I'm an amateur AVR user considering upgrading my robotics core module to an
ARM7, and I'm looking at this:
http://www.thaieasyelec.net/index.php/arm/arm7-lpc2378-with-2-8-inch-qvga-tft-lcd-touch-screen/p_2.html
The board has 3 key peripherals I want (LCD, touchscreen, uSD). I will be
learning about ARM, the 2378, these peripherals, and CrossWorks 2 all at the
same time. Ugh. I never really needed JTAG with my AVRs, so I'll probably
be learning that as well.
If you have experience with this board, or you have advice for an ARM newb
diving into the 23xx, I'd really like to hear from you. One thing I have
noticed is the drop in datasheet quality (next to AVRs).
Thanks,
LPC2378 dev board with 2.8" TFT touchscreen
Started by ●October 8, 2009
Reply by ●October 8, 20092009-10-08
--- In l..., "zoidicus" wrote:
> If you have experience with this board, or you have advice for an ARM newb diving into the 23xx, I'd really like to hear from you. One thing I have noticed is the drop in datasheet quality (next to AVRs).
>
> Thanks,
>
Remember. NXP publishes the datasheet and the user manual as separate documents.
In either event, the documents are tightly worded without a lot of example code. They take careful reading.
Richard
> If you have experience with this board, or you have advice for an ARM newb diving into the 23xx, I'd really like to hear from you. One thing I have noticed is the drop in datasheet quality (next to AVRs).
>
> Thanks,
>
Remember. NXP publishes the datasheet and the user manual as separate documents.
In either event, the documents are tightly worded without a lot of example code. They take careful reading.
Richard
Reply by ●October 8, 20092009-10-08
> I'm an amateur AVR user considering upgrading my
robotics core module to an ARM7, and I'm looking at this:
> http://www.thaieasyelec.net/index.php/arm/arm7-lpc2378-with-2-8-inch-qvga-tft-lcd-touch-screen/p_2.html
> The board has 3 key peripherals I want (LCD, touchscreen, uSD). I will be learning about ARM, the 2378, these peripherals, and CrossWorks 2 all at the same time. Ugh. I never really needed JTAG with my AVRs, so I'll probably be learning that as well.
>
> If you have experience with this board, or you have advice for an ARM newb diving into the 23xx, I'd really like to hear from you. One thing I have noticed is the drop in datasheet quality (next to AVRs).
>
> Thanks,
>
You might want to look at the 2478 rather than the 2378. It has an LCD controller built in. The touch screen should be trivial to implement in code and I'm sure you'll find numerous examples on the web on how to do this with a couple ADC lines.
Kevin.
> http://www.thaieasyelec.net/index.php/arm/arm7-lpc2378-with-2-8-inch-qvga-tft-lcd-touch-screen/p_2.html
> The board has 3 key peripherals I want (LCD, touchscreen, uSD). I will be learning about ARM, the 2378, these peripherals, and CrossWorks 2 all at the same time. Ugh. I never really needed JTAG with my AVRs, so I'll probably be learning that as well.
>
> If you have experience with this board, or you have advice for an ARM newb diving into the 23xx, I'd really like to hear from you. One thing I have noticed is the drop in datasheet quality (next to AVRs).
>
> Thanks,
>
You might want to look at the 2478 rather than the 2378. It has an LCD controller built in. The touch screen should be trivial to implement in code and I'm sure you'll find numerous examples on the web on how to do this with a couple ADC lines.
Kevin.
Reply by ●October 8, 20092009-10-08
Definitely, if you need TFT display, use the LPC2478, it does drive the
display by hardware, not software as would be needed on lpc23xx.
Debugging is a headache without a good "working-out-of-the-box" jtag,
usually they are expansives.
Cya
2009/10/8 kevin_townsend2
> > I'm an amateur AVR user considering upgrading my robotics core module to
> an ARM7, and I'm looking at this:
> >
> http://www.thaieasyelec.net/index.php/arm/arm7-lpc2378-with-2-8-inch-qvga-tft-lcd-touch-screen/p_2.html
> > The board has 3 key peripherals I want (LCD, touchscreen, uSD). I will be
> learning about ARM, the 2378, these peripherals, and CrossWorks 2 all at the
> same time. Ugh. I never really needed JTAG with my AVRs, so I'll probably be
> learning that as well.
> >
> > If you have experience with this board, or you have advice for an ARM
> newb diving into the 23xx, I'd really like to hear from you. One thing I
> have noticed is the drop in datasheet quality (next to AVRs).
> >
> > Thanks,
> > You might want to look at the 2478 rather than the 2378. It has an LCD
> controller built in. The touch screen should be trivial to implement in code
> and I'm sure you'll find numerous examples on the web on how to do this with
> a couple ADC lines.
>
> Kevin.
>
>
>
display by hardware, not software as would be needed on lpc23xx.
Debugging is a headache without a good "working-out-of-the-box" jtag,
usually they are expansives.
Cya
2009/10/8 kevin_townsend2
> > I'm an amateur AVR user considering upgrading my robotics core module to
> an ARM7, and I'm looking at this:
> >
> http://www.thaieasyelec.net/index.php/arm/arm7-lpc2378-with-2-8-inch-qvga-tft-lcd-touch-screen/p_2.html
> > The board has 3 key peripherals I want (LCD, touchscreen, uSD). I will be
> learning about ARM, the 2378, these peripherals, and CrossWorks 2 all at the
> same time. Ugh. I never really needed JTAG with my AVRs, so I'll probably be
> learning that as well.
> >
> > If you have experience with this board, or you have advice for an ARM
> newb diving into the 23xx, I'd really like to hear from you. One thing I
> have noticed is the drop in datasheet quality (next to AVRs).
> >
> > Thanks,
> > You might want to look at the 2478 rather than the 2378. It has an LCD
> controller built in. The touch screen should be trivial to implement in code
> and I'm sure you'll find numerous examples on the web on how to do this with
> a couple ADC lines.
>
> Kevin.
>
>
>
Reply by ●October 8, 20092009-10-08
The board that is pointed out comes with an LCD that includes
an intelligent controller with its own memory. I have one of these
it works great for what it is. The LPC parts are very powerful with
tons of features.. takes a while to master all the registers.. I was
using it for a while, then got side tracked on another project..
As for JTag I was using a wiggler cable for a while then upgraded
to the Segger JTag.. The wiggler was good enough to get me started
but the newer Segger part with Flash BP debugging really makes a
difference.
-John Gentilin
On 10/8/09 6:07 PM, Felipe de A N L wrote:
>
> Definitely, if you need TFT display, use the LPC2478, it does drive the
> display by hardware, not software as would be needed on lpc23xx.
>
> Debugging is a headache without a good "working-out-of-the-box" jtag,
> usually they are expansives.
>
> Cya
>
> 2009/10/8 kevin_townsend2 > > >
> >
> > > I'm an amateur AVR user considering upgrading my robotics core
> module to
> > an ARM7, and I'm looking at this:
> > >
> >
> http://www.thaieasyelec.net/index.php/arm/arm7-lpc2378-with-2-8-inch-qvga-tft-lcd-touch-screen/p_2.html
>
> > > The board has 3 key peripherals I want (LCD, touchscreen, uSD). I
> will be
> > learning about ARM, the 2378, these peripherals, and CrossWorks 2
> all at the
> > same time. Ugh. I never really needed JTAG with my AVRs, so I'll
> probably be
> > learning that as well.
> > >
> > > If you have experience with this board, or you have advice for an ARM
> > newb diving into the 23xx, I'd really like to hear from you. One thing I
> > have noticed is the drop in datasheet quality (next to AVRs).
> > >
> > > Thanks,
> > >
> >
> > You might want to look at the 2478 rather than the 2378. It has an LCD
> > controller built in. The touch screen should be trivial to implement
> in code
> > and I'm sure you'll find numerous examples on the web on how to do
> this with
> > a couple ADC lines.
> >
> > Kevin.
> >
> >
> >
an intelligent controller with its own memory. I have one of these
it works great for what it is. The LPC parts are very powerful with
tons of features.. takes a while to master all the registers.. I was
using it for a while, then got side tracked on another project..
As for JTag I was using a wiggler cable for a while then upgraded
to the Segger JTag.. The wiggler was good enough to get me started
but the newer Segger part with Flash BP debugging really makes a
difference.
-John Gentilin
On 10/8/09 6:07 PM, Felipe de A N L wrote:
>
> Definitely, if you need TFT display, use the LPC2478, it does drive the
> display by hardware, not software as would be needed on lpc23xx.
>
> Debugging is a headache without a good "working-out-of-the-box" jtag,
> usually they are expansives.
>
> Cya
>
> 2009/10/8 kevin_townsend2 > > >
> >
> > > I'm an amateur AVR user considering upgrading my robotics core
> module to
> > an ARM7, and I'm looking at this:
> > >
> >
> http://www.thaieasyelec.net/index.php/arm/arm7-lpc2378-with-2-8-inch-qvga-tft-lcd-touch-screen/p_2.html
>
> > > The board has 3 key peripherals I want (LCD, touchscreen, uSD). I
> will be
> > learning about ARM, the 2378, these peripherals, and CrossWorks 2
> all at the
> > same time. Ugh. I never really needed JTAG with my AVRs, so I'll
> probably be
> > learning that as well.
> > >
> > > If you have experience with this board, or you have advice for an ARM
> > newb diving into the 23xx, I'd really like to hear from you. One thing I
> > have noticed is the drop in datasheet quality (next to AVRs).
> > >
> > > Thanks,
> > >
> >
> > You might want to look at the 2478 rather than the 2378. It has an LCD
> > controller built in. The touch screen should be trivial to implement
> in code
> > and I'm sure you'll find numerous examples on the web on how to do
> this with
> > a couple ADC lines.
> >
> > Kevin.
> >
> >
> >
Reply by ●October 8, 20092009-10-08
> Definitely, if you need TFT display, use the LPC2478,
it does drive the
> display by hardware, not software as would be needed on lpc23xx.
>
> Debugging is a headache without a good "working-out-of-the-box" jtag,
> usually they are expansives.
>
> Cya
If you're going to use Crossworks (it's worth the money for debugging IMHO), the Olimex ARM-USB-TINY is probably the cheapest JTAG device you'll find (around $60 I think?) and it works 'out-of-box' with Crossworks. You'll probably need to increase the "JTAG Clock Divider" setting in Crossworks to get it to connect (try something like 4 or 8 to get started), but it should be pretty dependable. You can't go wrong with Crossworks + the Olimex JTAG in terms of bang for the buck, anyway (assuming you're paying 'hobbyist' pricing on CW).
It's just a shame there aren't a few more options for inexpensive 2478-based boards, though. It's a great chip. I have the Olimex 2478 STK and the Embedded Artists 2478 boards (the EA board is easier to prototype with) but they're pricey if you're just getting started. I'd love to see a decent < $100 2478 board with just the LCD pins broken out, for example.
Those are my (less than informed) suggestions, anyway.
> display by hardware, not software as would be needed on lpc23xx.
>
> Debugging is a headache without a good "working-out-of-the-box" jtag,
> usually they are expansives.
>
> Cya
If you're going to use Crossworks (it's worth the money for debugging IMHO), the Olimex ARM-USB-TINY is probably the cheapest JTAG device you'll find (around $60 I think?) and it works 'out-of-box' with Crossworks. You'll probably need to increase the "JTAG Clock Divider" setting in Crossworks to get it to connect (try something like 4 or 8 to get started), but it should be pretty dependable. You can't go wrong with Crossworks + the Olimex JTAG in terms of bang for the buck, anyway (assuming you're paying 'hobbyist' pricing on CW).
It's just a shame there aren't a few more options for inexpensive 2478-based boards, though. It's a great chip. I have the Olimex 2478 STK and the Embedded Artists 2478 boards (the EA board is easier to prototype with) but they're pricey if you're just getting started. I'd love to see a decent < $100 2478 board with just the LCD pins broken out, for example.
Those are my (less than informed) suggestions, anyway.
Reply by ●October 8, 20092009-10-08
--- In l..., John Gentilin wrote:
>
> The board that is pointed out comes with an LCD that includes
> an intelligent controller with its own memory.
... and it is supplied with software needed to drive the display and touchscreen. It's critical to get the driver code that matches the display as ThaiEasyElec have used several different versions of display controllers to date.
We have only used the display so far. We adapted our existing graphics library and demonstration code written using Armaide / Oberon-07 to drive it. The results can be seen on ThaiEasyElec's blog:
http://bluescreen-etee009.blogspot.com/
It wasn't particularly difficult. However, from our experience, any newbie to ARM who wants to program in C should rely on ThaiEasyElec's code and better spend their time productively writing applications for it.
> As for JTag I was using a wiggler cable for a while then upgraded
> to the Segger JTag.. The wiggler was good enough to get me started
> but the newer Segger part with Flash BP debugging really makes a
> difference.
>
We didn't have a need for any JTAG facilities or BP debugging. We just connected the board to an existing inexpensive RS232 / TTL adapter. We used FlashMagic on Windows to upload code to it and display debugging messages on a PC.
--
Chris Burrows
CFB Software
Armaide v2.1: LPC2xxx Oberon-07 Development System
http://www.cfbsoftware.com/armaide
>
> The board that is pointed out comes with an LCD that includes
> an intelligent controller with its own memory.
... and it is supplied with software needed to drive the display and touchscreen. It's critical to get the driver code that matches the display as ThaiEasyElec have used several different versions of display controllers to date.
We have only used the display so far. We adapted our existing graphics library and demonstration code written using Armaide / Oberon-07 to drive it. The results can be seen on ThaiEasyElec's blog:
http://bluescreen-etee009.blogspot.com/
It wasn't particularly difficult. However, from our experience, any newbie to ARM who wants to program in C should rely on ThaiEasyElec's code and better spend their time productively writing applications for it.
> As for JTag I was using a wiggler cable for a while then upgraded
> to the Segger JTag.. The wiggler was good enough to get me started
> but the newer Segger part with Flash BP debugging really makes a
> difference.
>
We didn't have a need for any JTAG facilities or BP debugging. We just connected the board to an existing inexpensive RS232 / TTL adapter. We used FlashMagic on Windows to upload code to it and display debugging messages on a PC.
--
Chris Burrows
CFB Software
Armaide v2.1: LPC2xxx Oberon-07 Development System
http://www.cfbsoftware.com/armaide
Reply by ●October 9, 20092009-10-09
This is all great feedback.
I'm glad to see the that board contains all the necessary LCD drive hardware external to the chip. On the other hand, for another $15 the same company offers a 2478 dev board with a larger display, and 64MB external SDRAM. However, I would have to find a way to mount the LCD, and I'm not sure if there's enough GPIO pins. Ultimately I will be interfacing a lot of robotics devices, including a small CMOS camera. Takes lots of pins to do that, and--unlike most interfaces--the camera isn't something I can farm out to an AVR.
As for JTAG devices, are the wigglers any less functional than the USB-TINY? I thought it was just slower, and required a parallel port.
FYI, I intend to use CW on Windows 7 (if it matters).
I'm glad to see the that board contains all the necessary LCD drive hardware external to the chip. On the other hand, for another $15 the same company offers a 2478 dev board with a larger display, and 64MB external SDRAM. However, I would have to find a way to mount the LCD, and I'm not sure if there's enough GPIO pins. Ultimately I will be interfacing a lot of robotics devices, including a small CMOS camera. Takes lots of pins to do that, and--unlike most interfaces--the camera isn't something I can farm out to an AVR.
As for JTAG devices, are the wigglers any less functional than the USB-TINY? I thought it was just slower, and required a parallel port.
FYI, I intend to use CW on Windows 7 (if it matters).
