Following your Porting Guide (btw, I check every day for updates ), we tried to port MF to a couple of our ARM boards.
The first one is a LPC2148 based ARM-KIT board by MCU123.com.
We first used GCC building environment: we managed to build both “Solutions/PCM023” projects (targeted to LPC22xx microcontrollers) and “Solutions/EA_LPC2478” projects.
After that, we tried to flash TinyBooterDecompressor.bin with a JTAG debugger/programmer (Segger J-Link 8, using J-Flash tool); we erased chip, then we programmed bin file (btw, J-Flash asked whether to correct the wrong checksum of .bin file: should we allow the tool to correct it?) and restarted device.
Then, we connected a PC to COM1 board port (using TeraTerm, at 9600bps), launched MFDeploy, choosed to connect via Serial Port, selected the right COM port on PC (COM2, on our case), clicked to “Ping” and…we get a sad “Pinging… Error: No response from device”; even after having connected (F5 on MFDeploy), we got “Connecting to COM2…Connected
Then, we tried to use FlashMagic, after having erased once again whole chip (via J-Flash JTAG tool) and tried to activate “autobaud” feature of LPC microcontrollers. But we didn’t succeeded: we never got “Synchronized” feedback one entered “?” character. Of course, FlashMagic didn’t work for same reason.
Then we tried to redo everything from start using MDK 4.1 (which embeds RealView 4.1 compiler) for same PCM023 solution. Building went fine, but once again flashing TinyBooterDecompressor.bin didn’t give us any positive feedback. To build we used MDK_3.80a “setenv” batch file.
Then we tried to redo everything from start building EA_LPC2478 solution. With GCC all went fine, but after flashing nothing changed (MFDeploy gave us “No response from device” at ping request). With MDK/RV, this time, we didn’t managed to build solution, since we got these 5 errors:
“c:\MicroFrameworkPK_v4_1\Solutions\EA_LPC2478\dotnetmf.proj” (build target) (1
“c:\MicroFrameworkPK_v4_1\Solutions\EA_LPC2478\TinyCLR\TinyCLR.proj” (Build tar
get) (88) ->
(BuildAXF target) ->
EXEC : error : L6220E: Load region LR_IFLASH size (772756 bytes) exceeds limi
t (380928 bytes). [c:\MicroFrameworkPK_v4_1\Solutions\EA_LPC2478\TinyCLR\TinyCL
EXEC : error : L6220E: Execution region ER_IFLASH size (772756 bytes) exceeds
limit (380928 bytes). [c:\MicroFrameworkPK_v4_1\Solutions\EA_LPC2478\TinyCLR\T
EXEC : error : L6220E: Load region LR_DAT size (163644 bytes) exceeds limit (
131072 bytes). [c:\MicroFrameworkPK_v4_1\Solutions\EA_LPC2478\TinyCLR\TinyCLR.p
EXEC : error : L6220E: Execution region ER_DAT size (163644 bytes) exceeds li
mit (131072 bytes). [c:\MicroFrameworkPK_v4_1\Solutions\EA_LPC2478\TinyCLR\Tiny
Then we tried to redo everything from start using another board, an ET-2103 based on LPC2103 micro.
This time we succeeded in activating autobaud feature and flashing TinyBooterDecompressor (both via JTAG and via FlashMagic), but once again…no response from device using MFDeploy.
Could you please help us?
Thanks very much!
P.S. Since we aim to port MF to LPC2387, is EA_LPC2478 solution suitable for that? Does it support display/presentation features via parallel interface?