Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
11 years, 1 month ago.
Can' get mbed interface on LPC800 MAX
Hello, I recently get my LPC800 MAX board (http://www.lpcware.com/lpc800-max) When i connect my board to computer, the default program (rgb led blinks red-green-blue-red-green-blue-r...) starts but computer does not see flash drive. When i connect while reset button is pressed, the removable disk labeled "CRP DISABLD (G:)" appears and there is a file "firmware.bin" in the memory. I can delete this file and copy another file there but when i press reset, the program remains same and when i disconnect and reconnect the board, firmware.bin is still there. I installed some firmwares but may be a mistake.
(sorry for language mistakes)
edit: I is most probably caused from Windows XP because another computer with Windows 7 works well. What is wrong with my computer?
Question relating to:
4 Answers
11 years, 1 month ago.
The firmware.bin that you see is probably the code on the mbed interface chip, not the code on the target lpc812. You may have damaged that code when overwriting it. I would try to reinstall it from the mbed hdk pages.
Actually, you may right. But i came across this page:https://mbed.org/handbook/Firmware-LPC800-MAX after publishing my question, followed he instructions but nothing changed.
posted by 08 Oct 201311 years, 1 month ago.
In seeestudio arch, reset is a very short press, like 100ms and to set it to usb disk you have to press like 1-2 seconds. Firmware.bin is restored automatically and i need to delete it each time when installing my own software.
My software runs fine altough i cant get Serial.printf data to my Vista because of the lack of support by mbed comm driver.
Also i noticed that fopen hangs the device and mbed documentation gives seally reason for that (in chip flash). With in chip flash the average end customer does not flash the device so permanent data written to flash from the software should be possible.
i have a 4 digit led display as output and it has helped me going on. I just ordered a 2.2'' tft to get better display for development and for the end user.
11 years, 1 month ago.
this is the file i used to 'un-brick' it
/media/uploads/ceri/firmware__lpc_max-save.bin
Hope this helps,
BTW, where is the new software ??
Cheers
Ceri
11 years, 1 month ago.
Hi. I have problem with bricked LPC800-max too. Probably it's problem with Linux driver.
After connecting device, dmesg display something like that:
dmesg log
[18013.090711] usb 2-1.2: new full-speed USB device number 32 using ehci-pci [18013.178633] usb 2-1.2: New USB device found, idVendor=1fc9, idProduct=000f [18013.178643] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [18013.178649] usb 2-1.2: Product: LPC1XXX IFLASH [18013.178653] usb 2-1.2: Manufacturer: NXP [18013.178657] usb 2-1.2: SerialNumber: ISP [18013.179461] scsi32 : usb-storage 2-1.2:1.0 [18014.181362] scsi 32:0:0:0: Direct-Access NXP LPC1XXX IFLASH 1.0 PQ: 0 ANSI: 0 CCS [18014.181803] sd 32:0:0:0: Attached scsi generic sg2 type 0 [18014.182548] sd 32:0:0:0: [sdc] 132 512-byte logical blocks: (67.5 kB/66.0 KiB) [18014.184323] sd 32:0:0:0: [sdc] Write Protect is off [18014.184335] sd 32:0:0:0: [sdc] Mode Sense: 03 00 00 00 [18014.185412] sd 32:0:0:0: [sdc] No Caching mode page present [18014.185422] sd 32:0:0:0: [sdc] Assuming drive cache: write through [18014.189810] sd 32:0:0:0: [sdc] No Caching mode page present [18014.189819] sd 32:0:0:0: [sdc] Assuming drive cache: write through [18014.198532] sdc: [18014.202999] sd 32:0:0:0: [sdc] No Caching mode page present [18014.203008] sd 32:0:0:0: [sdc] Assuming drive cache: write through [18014.203014] sd 32:0:0:0: [sdc] Attached SCSI removable disk
And after saving new frimware or old one firmware, new firmware readed from flash was broken (after deataching and attaching device again - many first bytes have value 0xff). After writing firmware on Windows machine, board was back to live.
I think I read that there's a known problem with flashing the 11U24 from Linux because the chip is only pretending to be a MSD and it depends on the sectors being written in sequence. The solution was to overwrite the file instead of delete-then-copy. The AN doesn't say how but I'd try using "dd". In Windows you must use "Delete-then-copy". See http://www.lpcware.com/content/nxpfile/an11305-usb-system-programming-lpc11u3xlpc11u2x
posted by 11 Oct 2013