using openocd

Neng-Yu Tu (Tony Tu) tony at
Tue Sep 2 06:58:43 CEST 2008

Hash: SHA1

Hi Lynn-

Lynn Nguyen 提到:
> Why would I want to do that to the debug board?
> . If the usb id is
> 0403:6010 then its wrong isn't it?

Yes, 0403:6010 is wrong if you get the debug v3 comes with these IDs.
But use the default ID advantage is you could get your system recognized
debug board as ttyUSB0 and ttyUSB1 immediately, instead of showing 1-1,
2-1, 2-1.1 in the ubuntu /dev (USB hub/FTDI channel 1/FTDI channel 2).
In your case, I suggest you reset debug board eeporm and direct use it
again or re-program it.

In some cases (very rare) that re-program or reset the FTDI content
could let debug board back to normal.

Other possible is FPC not correct connected, but should have at least
UART or JTAG worked.


- --
Neng-Yu Tu (Tony Tu)
Openmoko, Inc.

Some questions could be answered by reference following link:

Wiki -
Download -

Freerunner Introduction -

> Also I don't understand this section of the wiki page:
>           Did you turn it on ?
>     An easily made but devastating mistake is to forget to actually
>     activate the CPU. Just connecting power is not enough ! Press and
>     hold the power button until the boot loader does its count-down, or,
>     in case there is no runnable boot loader, the CPU keeps itself busy.
> is the 'it' this part referring to the openmoko? I mean, isn't the whole
> point of a bricked openmoko the fact that it can't turn on? How am I
> supposed to activate the CPU if it won't turn on at all? I know the
> battery is fully charged because I checked the voltage.
> this is the openocd.cfg i am using:
>     telnet port 4444
>     gdb_port 3333
>     # interface
>     interface ft2232
>     jtag_speed 8
>     ft2232_device_desc "Debug Board for Neo1973"
>     ft2232_layout "jtagkey"
>     ft2232_vid_pid 0x1457 0x5118
>     reset_config trst_and_srst
>     jtag_device 4 0x1 0xf 0xe
>     daemon_startup attach
>     target arm920t little reset_run 0 arm920t
>     working_area 0 0x200000 0x4000 backup
>     run_and_halt_time 0 5000
> How do I check my debug board's uart console? I can't remember how to do
> it but I'm pretty sure I was able to screen onto it once.
> Actually maybe it is something with my debug board, I looked in the logs
> and saw this:
>     [  459.596147] usb 3-1.3: new full speed USB device using uhci_hcd
>     and address 27
>     [  459.744465] usb 3-1.3: device not accepting address 27, error -71
> Do you know what to make of this error? Google search finds nothing =/.

Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla -


More information about the community mailing list