Ticket #1567 (closed defect: worksforme)
cannot re-flash the debug board
| Reported by: | asappia | Owned by: | hardware |
|---|---|---|---|
| Priority: | highest | Milestone: | |
| Component: | hardware | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | PatchReviewResult: | ||
| Reproducible: |
Description
Hi all,
Yesterday evening I finally had time to check my FreeRunner? and its Debug Board.
First of all I opened the Freerunner and made all the requested connection between the openmoko and the debug board (the cable and the USB connector), next I connected the debug board to my PC.
Reading http://wiki.openmoko.org/wiki/Debug_board
I see that my USB ID 0403:6010 request I need to reflash the debug board.
So I started my tries with linux.
Downloaded libftdi -> applied patch from http://people.openmoko.org/werner/libftdi-c56-strings-dirty-hack.patch
Hunk 1 failed ... done manual patching
Hunk 2 Succeed with Fuzz 1
Rechecked ftdi.c, it seems ok.
Compiled and installed OK
Downloaded ftdi_eeprom -> applied patch from http://people.openmoko.org/laforge/misc/debug_board_v2/ftdi_eeprom/ftdi_eeprom-0.2-moko.patch
Succeed
Downloaded
- http://people.openmoko.org/laforge/misc/debug_board_v2/ftdi_eeprom/neo1973_debug_board_v2.ftdi
- http://people.openmoko.org/laforge/misc/debug_board_v2/ftdi_eeprom/neo1973_debug_board_v2.eeprom
Now let's try to patch
# ftdi_eeprom --flash-eeprom ftdi_eeprom/neo1973_debug_board_v2.ftdi
Error: No device with vendor id 1457:5118
Ok let's see
tried to substitute vendor id and product id inside the .ftdi, but
Cannot Flash
Let's try with Windows
Downloaded MProg3.0
Downloaded http://people.openmoko.org/laforge/misc/debug_board_v2/mprog_template/neo1973_debugboard_v2.ept
Started MProg3.0
Applied "Scan for Available Devices"
Results:
Number Of Blank Devices = 0
Number Of Programmed Devices = 0
Simply I see the device connected, but I'm unable to apply the correct firmware.

Just a quick comment: the debug board will also work if you don't have
the correct numbers in the EEPROM: ttyUSB doesn't care about them anyway,
openocd.cfg should have a list of valid numbers, and dfu-util only needs
the vendor/product ID if there's more than one DFU-capable device.