Support for the MCB2388 Evaluation Board. More...
Support for the MCB2388 Evaluation Board.
|16KiB USB RAM|
|16KiB Ethernet RAM|
|2KiB Backup RAM|
|Frequency||up to 72 MHz|
|ADCs||1x 10-bit (8 channels)|
|DACs||1x 10-bit (1 channel)|
|Vcc||3.0V - 3.63V|
|Board Manual||Board Manual|
1 User button, 8 LED, 1 potentiometer, 1 speaker:
|DMA||partly||only for MCI|
|MCI||yes||Media Card (SD/MMC) Interface|
The MCB2388 is programmed via an ISP bootloader over UART. For this you have to connect an USB-RS232 converter to the COM0 port.
Make sure to have the ISP Jumper set.
Connect the MCB2388 to your PC using the serial port and run from within the folder of your application to flash:
BOARD=mcb2388 make flash
You'll notice that during the first invocation takes a bit longer, as the tool
lpc2k_pgm used to flash the MCB2388 is also compiled.
You can connect to the shell by running:
BOARD=mcb2388 make term
By default the RST line is connected to the RTS/CTS line of COM0. This will pull the MCU into reset when connecting a terminal. Use
pyterm -tg to toggle the pins and complete the reset.
If you want to connect a terminal application that does not support this, remove the RST jumper from the board. You will not be able to flash the board using
lpc2k_pgm if the RST jumper is disconnected.
The development kit comes with a ULINK-ME Debug Unit that supports the CMSIS-DAP protocol. Connect it with the JTAG port on the board, the debugging should work by typing
BOARD=mcb2388 make debug
Theoretically you should be able to flash also via JTAG. Unfortunately OpenOCD support for this chip family seems to be pretty buggy. I was unable to flash the board using the ULINK-ME adapter and OpenOCD. (2019)
The board might get stuck when using OpenOCD, you have to power-cycle it to being able to use ISP programming again.
|Board specific configuration of direct mapped ADC. |
|Basic definitions for the MCB2388 board. |
|Board specific configuration of direct mapped GPIOs. |
|MCB2388 peripheral configuration. |