I recently purchased this board from Sparkfun. I think the board is supplied by ThaiEasyElec.com guys over in Bangkok. The board has LPC2378, 2.8" color LCD, and a touch screen with a JTAG interface.
The examples that came with the board are for Keil compiler, also listed on SparkFun website. I can’t afford to pay for the compiler and I tried the evaluation version but they don’t compile due to code size limitation in the compiler.
I also purchased the OpenOCD ARM-USB-OCD from Olimex via Sparkfun. That came with Eclipse based ARm-GCC tools. I am trying to port the Keil C code and examples to ARM GCC tools.
I have experience in programming PIC, Atmel microcontrollers. This is my first experience with ARM based microcontrollers.
Well … this sucks. I’m not able to get the the olimex arm-usb-ocd device working with Eclipse either. In the Olimex how-to textfile supplied on the cd it states:
olimex how-to:
8. Start the debugger from “Run->Open Debug Dialg->Embedded Debug(Cygwin)->”, “Debug”
There is no such option in the Eclipse supplied with the Olimex ocd
When I try to run the demo progam og debug it or whatever I get:
eclipse:
An internal error occurred during: “Launching main.out”.
java.lang.NullPointerException
I getting pretty frustrated. How hard can it be to supply tools with correct documentation ??
BTW, I think the openocd part is working, the console output is:
eclipse console output:
Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
I have Eclipse working… Had to use the Zylin plugin and fired up the debugger from there.
Problem I am having is that all the mid to high level code is very difficult to read… The low level LCD and Touch Screen libs are ok, but anything in the App level is the worst…
Were you able to get FlashMagic to work… I was not, I have to load code through the JTag port…
I now got flashmagic working. Just used an FTDI usb to serial converter. Connected to console port, FTDI RX to Console TX and FTDI TX to Console RX + both GND lines. Shorted the programming jumper and pressed reset. Then the bluescreen boots with a blank display and I was able to make Flash Magic work just fine.
Still haven’t got JTAG working, but I haven’t had much time to study the problem either.
I now got flashmagic working. Just used an FTDI usb to serial converter. Connected to console port, FTDI RX to Console TX and FTDI TX to Console RX + both GND lines.
We also used FlashMagic in a similar way when developing a vector graphics processing program for the BlueScreen. JTAG facilities weren't needed at all. A video of the resulting program is here:
The first two images are processed in real time, the second two have built-in delays to show the drawing as it proceeds.
All the code is written in Oberon-07 using the Armaide development system. The total executable size (including display drivers) is 17 KB. The AutoCAD Slide image data file sizes are 5 KB for the Space Shuttle and 28 KB for St Pauls. They are appended to the executable using the ‘resource management’ feature of Armaide v2.1.
When you upload it, the executable replaces the first 17 KB + 33 KB of code you have in Flash ROM, so make sure, if you need to, that you can reload any of the ThaiEasyElec code that might already occupy that address space.
Also, the low-level driver code assumes that the BlueScreen is using the ILI9325 QVGA driver chip which is the one used on our board. The code supplied by ThaiEasyElec also supports the ILI9320 chip. Maybe that was used on earlier versions of the board? We have written a simple program which identifies the chip used so if the program doesn’t work that would be the first thing to try.
I might have to look into that development ide of yours :!:
