> -----Original Message-----
> From: l...
> [mailto:l...]On Behalf
> Of Forum Junky
> Sent: Saturday, January 27, 2007 8:34 PM
> To: l...
> Subject: RE: [lpc2000] Re: USB Bootloader - MCB2140 - LPC2148
> Mike, I downloaded the "firmware uploader" directly from
> TNKernel. From there, I compiled both "usb_fwu" and "usb_app"
> using IAR full evaluation software without modifying any of
> the firmwares. Both were compiled successfully. As mentioned
> from previous post, the "usb_fwu" was downloaded using ISP
> and later "usb_app" was downloaded via USB using TNKernel
> firmware loader program. When I tried to re-download
> "usb_app" to test if "usb_fwu" still present, it's giving
> "download failure error". I also tried to replug the USB
> cable, but to no avail the same error popup.
>
> Sonny
>

You may not realize it, but since the usb_fw driver that you
installed on your PC is a trial version, it times out in
4 hours, and stops working giving that error. Reboot your
PC, and try it agian. Unfortunately, the diver is very
expensive if you want to purchase it...

If this doesn't work, try reloading usb_fw on your board,
just to be sure. I've not had any problems with usb_fw
being corrupted.

Mike

An Engineer's Guide to the LPC2100 Series

Mike, I downloaded the "firmware uploader" directly from TNKernel. From there, I compiled both "usb_fwu" and "usb_app" using IAR full evaluation software without modifying any of the firmwares. Both were compiled successfully. As mentioned from previous post, the "usb_fwu" was downloaded using ISP and later "usb_app" was downloaded via USB using TNKernel firmware loader program. When I tried to re-download "usb_app" to test if "usb_fwu" still present, it's giving "download failure error". I also tried to replug the USB cable, but to no avail the same error popup.

Sonny

Michael Anton wrote:

> -----Original Message-----
> From: l...
> [mailto:l...]On Behalf
> Of Forum Junky
> Sent: Friday, January 26, 2007 8:21 PM
> To: l...
> Subject: RE: [lpc2000] Re: USB Bootloader - MCB2140 - LPC2148
> Mike, When you load "usb_fw" using ISP followed by "usb_app"
> via USB and TNKernel, did the "usb_fw" got overwritten? I had
> this problem, so I thought I need to ask.
>
> Sonny
>

No, since the firmware I load is located above usb_fw, it does
not get overwritten. You must locate your firmware to be loaded
via USB at 0x2000. Make sure your startup code for your firmware
does not include the reset and interrupt vectors, or these will
stomp on usb_fw. Check your map file to make sure you have
everything set to the correct addresses (the actual addresses
to be used would normally be set in the linker control file).

Mike

---------------------------------
Never Miss an Email
Stay connected with Yahoo! Mail on your mobile. Get started!

> -----Original Message-----
> From: l...
> [mailto:l...]On Behalf
> Of sashi ono
> Sent: Friday, January 26, 2007 10:05 PM
> To: l...
> Subject: [lpc2000] Re: USB Bootloader - MCB2140 - LPC2148
> --- In l..., "Michael Anton" wrote:
> >
> >
> >
> > > -----Original Message-----
> > > From: l...
> > > [mailto:l...]On Behalf
> > > Of Chris Graham
> > > Sent: Friday, January 19, 2007 8:32 AM
> > > To: l...
> > > Subject: RE: [lpc2000] USB Bootloader - MCB2140 - LPC2148
> > >
> > >
> > > I also need a LPC214x USB bootloader and was considering
> > > using the TNKernel
> > > "Firmware Upgrader". What problems did you find with it?
> > >
> > > If anyone has the code for a good failsafe bootloader I'd be
> > > willing to pay
> > > for it.
> > >
> > > - Chris
> > >
> > >
> >
> >
> > I have the USB bootloader based on the TNKernel working fine.
> > It looks like it should just work as is, but there were a
> > few things I changed to support my hardware.
> >
> > Mike
> > what were those changes? Any chance of posting a working hex file?
>

The changes are not necessary to make it work. I just didn't like
the way that the application ROM header was done, so I changed it.
Also, there were some hardware specific issues that needed to be
addressed for my target board. A hex file of my version wouldn't
help you much, unless I spent a lot of time documenting the changes.

Have you been able to get the usb_fw running, and recognized by the
driver? If you have, and you can't get your application to load
correctly, then there is something wrong with it. You must get the
ROM header to be located correctly or it will not work.

What specifically are you having trouble with? What doesn't work?

Mike

--- In l..., "Michael Anton" wrote:
>
> > -----Original Message-----
> > From: l...
> > [mailto:l...]On Behalf
> > Of Chris Graham
> > Sent: Friday, January 19, 2007 8:32 AM
> > To: l...
> > Subject: RE: [lpc2000] USB Bootloader - MCB2140 - LPC2148
> >
> >
> > I also need a LPC214x USB bootloader and was considering
> > using the TNKernel
> > "Firmware Upgrader". What problems did you find with it?
> >
> > If anyone has the code for a good failsafe bootloader I'd be
> > willing to pay
> > for it.
> >
> > - Chris
> >
> >
> I have the USB bootloader based on the TNKernel working fine.
> It looks like it should just work as is, but there were a
> few things I changed to support my hardware.
>
> Mike
>

what were those changes? Any chance of posting a working hex file?

> -----Original Message-----
> From: l...
> [mailto:l...]On Behalf
> Of Forum Junky
> Sent: Friday, January 26, 2007 8:21 PM
> To: l...
> Subject: RE: [lpc2000] Re: USB Bootloader - MCB2140 - LPC2148
> Mike, When you load "usb_fw" using ISP followed by "usb_app"
> via USB and TNKernel, did the "usb_fw" got overwritten? I had
> this problem, so I thought I need to ask.
>
> Sonny
>

No, since the firmware I load is located above usb_fw, it does
not get overwritten. You must locate your firmware to be loaded
via USB at 0x2000. Make sure your startup code for your firmware
does not include the reset and interrupt vectors, or these will
stomp on usb_fw. Check your map file to make sure you have
everything set to the correct addresses (the actual addresses
to be used would normally be set in the linker control file).

Mike

Mike, When you load "usb_fw" using ISP followed by "usb_app" via USB and TNKernel, did the "usb_fw" got overwritten? I had this problem, so I thought I need to ask.

Sonny

Michael Anton wrote:

> -----Original Message-----
> From: l...
> [mailto:l...]On Behalf
> Of forumjnky
> Sent: Monday, January 22, 2007 6:09 PM
> To: l...
> Subject: [lpc2000] Re: USB Bootloader - MCB2140 - LPC2148
> Mike,
> What compiler are you using? I'm using Keil uVision 3, but I'm
> getting "L6938E Invalid value for --ro-base" error. Any idea what
> went wrong. I followed the Linker settings from TNKernel usb_app
> project.
>
> Sonny

I'm using GCC. I have no idea what that error means, but given that
it starts with L, perhaps it is a linker error...

Of course, you could use GCC to build FWU, and then Keil for your
code.

Mike

---------------------------------
Now that's room service! Choose from over 150,000 hotels
in 45,000 destinations on Yahoo! Travel to find your fit.

> -----Original Message-----
> From: l...
> [mailto:l...]On Behalf
> Of forumjnky
> Sent: Monday, January 22, 2007 6:09 PM
> To: l...
> Subject: [lpc2000] Re: USB Bootloader - MCB2140 - LPC2148
> Mike,
> What compiler are you using? I'm using Keil uVision 3, but I'm
> getting "L6938E Invalid value for --ro-base" error. Any idea what
> went wrong. I followed the Linker settings from TNKernel usb_app
> project.
>
> Sonny

I'm using GCC. I have no idea what that error means, but given that
it starts with L, perhaps it is a linker error...

Of course, you could use GCC to build FWU, and then Keil for your
code.

Mike

Mike,
What compiler are you using? I'm using Keil uVision 3, but I'm
getting "L6938E Invalid value for --ro-base" error. Any idea what
went wrong. I followed the Linker settings from TNKernel usb_app
project.

Sonny
--- In l..., "Michael Anton" wrote:
>
> > -----Original Message-----
> > From: l...
> > [mailto:l...]On Behalf
> > Of forumjnky
> > Sent: Friday, January 19, 2007 6:03 PM
> > To: l...
> > Subject: [lpc2000] Re: USB Bootloader - MCB2140 - LPC2148
> >
> >
> > Mike, Have you actually tried downloading user firmware using FWU
and
> > TNKernel Firmware Downloader? Does your user firmware works after
> > downloading?
> >
> > --- In l..., "Michael Anton" wrote:
> > >
> > > Yes, I use this as my main method for programming now. It is nice,
> since it only takes 1.5 seconds to transfer my 50KB image.
>
> Mike
>

> -----Original Message-----
> From: l...
> [mailto:l...]On Behalf
> Of forumjnky
> Sent: Friday, January 19, 2007 6:03 PM
> To: l...
> Subject: [lpc2000] Re: USB Bootloader - MCB2140 - LPC2148
> Mike, Have you actually tried downloading user firmware using FWU and
> TNKernel Firmware Downloader? Does your user firmware works after
> downloading?
>
> --- In l..., "Michael Anton" wrote:
> >
> >

Yes, I use this as my main method for programming now. It is nice,
since it only takes 1.5 seconds to transfer my 50KB image.

Mike

Mike, Have you actually tried downloading user firmware using FWU and
TNKernel Firmware Downloader? Does your user firmware works after
downloading?

--- In l..., "Michael Anton" wrote:
>
> > -----Original Message-----
> > From: l...
> > [mailto:l...]On Behalf
> > Of Chris Graham
> > Sent: Friday, January 19, 2007 12:48 PM
> > To: l...
> > Subject: RE: [lpc2000] Re: USB Bootloader - MCB2140 - LPC2148
> >
> >
> > I haven't confimed that this solves your problem, but the
TNKernel USB
> > bootloader documentaton says that the bootloader itself
> > resides at 0x0000000
> > - 0x00001FFF. the downloaded firmware is loaded just
> > following a control
> > block that is at address 0x00002000 - 0x0000200F. Possibly
> > the blinky code
> > needs to be linked to start at 0x00002000 and include the
> > control block?
> > Also it says that the firmware's interrupts need to be
> > located in ram at
> > 0x40000000.
> >
> > However, I'm not an ARM expert. Can someone else confirm if
> > this makes
> > sense?
> >
> > - Chris
> > This is correct. You do need to insert a control block at the
> start of your code, and make sure the whole thing starts at
> address 0x00002000. This is all in the docs.
>
> Mike
>