Does anyone know where I can find a bootloader example which uses ONLY the USB port on the LPC-214X as the means to download new code to flash?
I’ve scoured the web for the same thing for a few months now and come up with nothing. If anybody’s written one, they apparently aren’t making it open source.
Resource about ARMs is rare today although it is widely used.
I don’t know all the specific details, but here’s an USB bootloader used in model airplanes, using the lpcusb stack:
I need some help. I have an embedded artists LPC2148 quickstart board and I’m using the lpcusb library to communicate with it. The aim is to communicate with the board through USB (VCOM application) and to be able to program the firmware through a bootloader.
I’ve tried paparazzi’s bootloader and i’ve programmed a simple led on application. It works perfectly. On the other hand, when i program through ISP the VCOM application it also works perfectly. The problem comes when i try to program through the bootloader the VCOM application.
I don’t know where the error can be, because I link my application to 0x4000 address (library LPC2140-ROM-bl.ld) and the bootpin in crt.S is not P0.23. I’ve followed the instructions in http://paparazzi.enac.fr/wiki/index.php … SBDownload
The VCOM application works, but it gets stuck. That’s what I get through the serial port:
Registered handler for device status
Registered handler for EP 0x0
Registered handler for EP 0x80
Registered handler for EP 0x81
Registered handler for EP 0x82
Registered handler for EP 0x5
Registered handler for frame
Registered handler for device status
S6D100
There is another source for LPC214x USB bootloader available at:
http://www.tnkernel.com/usb_fw_upgrader.html
The USB Firmware Upgrader is a standalone program for the Philips LPC214x microcontroller,
which allows to download the firmware (an application program) to the microcontroller’s flash using an USB.
This is very useable for the field/customer future firmware upgrades.
I know,
but I’m trying not to use IOUSB driver, because it stops working 4 hours later.
I don’t know what’s going on. From the logging I can see that the device receives at least an USB reset, setup request 6 and a request for the device descriptor. Next thing I would expect from a windows host is another bus reset and another device descriptor request.