Re: using openocd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lynn Nguyen wrote: So um, how do you reset the eeprom? I'm sorry, I don't have much experience in this error. Also, I was thinking that ft2232 was not enabled for my openocd build and when I tried to build openocd from the source code with ft2232 enabled, I kept getting random errors. So, I just used apt-get install openocd instead. I figured most people just used apt-get install and so that should be alright right? i used apt-get install openocd , it's alright Lynn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBSL6XBRFuNemPXNFjAQKQ+Af9GXk5EOdxX/lzzkfhuerfXyHEk6VEKqe0 Mo0jmyTT7E+Zmq6KxV/1/84w/so80DFCnaJIhyAQaVMdGGs5TMIKfCleKY334loB bSrZKJqESG+RlrbmkpAYERJAnMW/ntOlx6QgKyoGkv7fWzqJD/bA598JNJ2Llb4T QKrOQKadPNNW8l3azjiM4adTyTul86NkOIwh/NH948yWH/yJJitn7j3wucLQwVPr rkbVkgDud28VFscm9uHzuC/6JQ8HrUhrWgFPm9t3dmsXFM0SpzV6rKX3npMAEZTq lyaqkjlxdGkFZhCBiUVo5FABXw6YCNLefcJfNEuVN6w1NSuWKlTtmA== =RSYJ -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
Tony, any idea what that error means? I searched a little and failed to find. Lynn Nguyen wrote: I get: [ 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 I don't have any USBs showing up in tty when I plug it in. Lynn On Mon, Sep 1, 2008 at 7:59 PM, Michael Shiloh [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Lynn Nguyen wrote: I tried the sequence but still the same errors. Should I have a /dev/ttyUSB1 when I plug in the debug board? because i dont... Lynn Did you check other devices? It may have shown up on a different tty. what does dmesg or tail -f /var/log/messages say as you plug in the USB cable? Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
So um, how do you reset the eeprom? I'm sorry, I don't have much experience in this error. Also, I was thinking that ft2232 was not enabled for my openocd build and when I tried to build openocd from the source code with ft2232 enabled, I kept getting random errors. So, I just used apt-get install openocd instead. I figured most people just used apt-get install and so that should be alright right? Lynn On Tue, Sep 2, 2008 at 11:47 AM, Kees Jongenburger [EMAIL PROTECTED] wrote: On Mon, Sep 1, 2008 at 6:33 AM, Lynn Nguyen [EMAIL PROTECTED] wrote: Hey All, I was wondering if anyone was using the Neo1973 (GTA01v4) with Debug board v3. I used the openocd.cfg available on the wiki and I get this problem: Info:openocd.c:82 main(): Open On-Chip Debugger (2006-08-01 12:00 CEST) Info:configuration.c:50 configuration_output_handler(): Command ft2232_device_desc not found Info:configuration.c:50 configuration_output_handler(): Command ft2232_layout not found Info:configuration.c:50 configuration_output_handler(): Command ft2232_vid_pid not found Error: jtag.c:1219 jtag_init(): No valid jtag interface found (ft2232) It seems like openocd is having some trouble with ft2232 because I don't see anything wrong with those commands. yes , perhaps libft2232 is not enabled in you openocd build? greetings ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
Why would I want to do that to the debug board? http://wiki.openmoko.org/wiki/Debug_Board_v3 . If the usb id is 0403:6010 then its wrong isn't it? Also I don't understand this section of the wiki page: http://wiki.openmoko.org/wiki/OpenOCD#Known_Bugs_and_Troubleshooting 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 gdb_port # 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 0x20 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 =/. Lynn On Mon, Sep 1, 2008 at 12:43 AM, Neng-Yu Tu (Tony Tu) [EMAIL PROTECTED]wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Lynn- Lynn Nguyen ??: Yeah it's loading the correct openocd.cfg file. I even added random commands to it and i saw those commands in the error messages. I even used -f to be sure. * Could you check the .cfg file is comes with, it should called openocd-debugv2.cfg : 1. ft2232_vid_pid 0x1457 0x5118 2. And adjust jtag_speed to higher number (4 or 8, default is 0) * And is your debug board UART (terminal console) is working? If still not working, you might could erase the EEPROM content in the debug board again, return the default USB ID 0403 6010. They see if the UART and openocd could work. Regards, - -- Neng-Yu Tu (Tony Tu) Openmoko, Inc. Support. Some questions could be answered by reference following link: Wiki - http://wiki.openmoko.org Download - http://downloads.openmoko.org Freerunner Introduction - http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner I was wondering if anyone was using the Neo1973 (GTA01v4) with Debug board v3. I used the openocd.cfg available on the wiki and I get this problem: Info:openocd.c:82 main(): Open On-Chip Debugger (2006-08-01 12:00 CEST) Info:configuration.c:50 configuration_output_handler(): Command ft2232_device_desc not found Info:configuration.c:50 configuration_output_handler(): Command ft2232_layout not found Info:configuration.c:50 configuration_output_handler(): Command ft2232_vid_pid not found Error: jtag.c:1219 jtag_init(): No valid jtag interface found (ft2232) It seems like openocd is having some trouble with ft2232 because I don't see anything wrong with those commands. Does your openocd load neo1973 specific config? like tmp/openocd -f tmp/openocd-debugv2.cfg Usually it is because your USB vid/pid setting is not correct in the config file(load the wrong config file) Hope this helps. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAki7nRcACgkQmV6sZhhBn2/jIACgjEh/KVZXXdhD4sLyZh17d9gA DG4AnAmOZwoBDKSqNn3mua2WQnvi9xCp =wz/W -END PGP SIGNATURE- ___ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
Lynn Nguyen wrote: 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. it does refer to the phone. Turn it on means setting the power-management unit (PMU) into Active mode so that voltage is applied to the CPU. This might happen automatically when you plug in the USB cable, but if not you can do it by pressing the power button. If the device is bricked you will not see anything happen when you turn it on, but internally the CPU will be ready to accept a JTAG connection. Try following the sequence described at http://wiki.openmoko.org/wiki/Debug_Board_v2#Hardware_connection (which AFAIK should be the same for a v3 debug board). this is the openocd.cfg i am using: Looks OK to me. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
I tried the sequence but still the same errors. Should I have a /dev/ttyUSB1 when I plug in the debug board? because i dont... Lynn On Mon, Sep 1, 2008 at 5:03 PM, Mike Montour [EMAIL PROTECTED] wrote: Lynn Nguyen wrote: 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. it does refer to the phone. Turn it on means setting the power-management unit (PMU) into Active mode so that voltage is applied to the CPU. This might happen automatically when you plug in the USB cable, but if not you can do it by pressing the power button. If the device is bricked you will not see anything happen when you turn it on, but internally the CPU will be ready to accept a JTAG connection. Try following the sequence described at http://wiki.openmoko.org/wiki/Debug_Board_v2#Hardware_connection (which AFAIK should be the same for a v3 debug board). this is the openocd.cfg i am using: Looks OK to me. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
I get: [ 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 I don't have any USBs showing up in tty when I plug it in. Lynn On Mon, Sep 1, 2008 at 7:59 PM, Michael Shiloh [EMAIL PROTECTED] wrote: Lynn Nguyen wrote: I tried the sequence but still the same errors. Should I have a /dev/ttyUSB1 when I plug in the debug board? because i dont... Lynn Did you check other devices? It may have shown up on a different tty. what does dmesg or tail -f /var/log/messages say as you plug in the USB cable? Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
Lynn Nguyen wrote: I tried the sequence but still the same errors. Should I have a /dev/ttyUSB1 when I plug in the debug board? because i dont... You should, as long as you have the ftdi_sio module loaded with the right vendor/product IDs for the debug board (0x1457/0x1458). Here's what I see when I plug in my debug board v2: usb 1-2: new full speed USB device using uhci_hcd and address 5 usb 1-2: new device found, idVendor=0451, idProduct=2046 usb 1-2: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 1-2: configuration #1 chosen from 1 choice hub 1-2:1.0: USB hub found hub 1-2:1.0: 4 ports detected usb 1-2.1: new full speed USB device using uhci_hcd and address 6 usb 1-2.1: new device found, idVendor=1457, idProduct=5118 usb 1-2.1: new device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-2.1: Product: Debug Board for Neo1973 usb 1-2.1: Manufacturer: OpenMoko usb 1-2.1: configuration #1 chosen from 1 choice ftdi_sio 1-2.1:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT2232C usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB0 ftdi_sio 1-2.1:1.1: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT2232C usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB1 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Using openocd
Hi all, I was wondering, has anyone had any luck connecting their debug board (v3) to a neo1973? I followed all the instructions here: http://wiki.openmoko.org/wiki/Debug_Board_v3 (for linux) but I keep getting 'no valid jtag interface found'. But that doesn't make any sense because I can see the debug board from my laptop when i do 'lsusb'. Any ideas? Thanks! Lynn ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Using openocd
Hi Lynn- Hi all, I was wondering, has anyone had any luck connecting their debug board (v3) to a neo1973? I followed all the instructions here: http://wiki.openmoko.org/wiki/Debug_Board_v3 (for linux) but I keep getting 'no valid jtag interface found'. But that doesn't make any sense because I can see the debug board from my laptop when i do 'lsusb'. Any ideas? Thanks! Lynn Does your openocd using correct setting file? v3 board could connect to neo1973, because it basically compatible old boards. -- Tony Tu (Neng-Yu Tu) Openmoko, Inc. Support. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
