Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
On Mon, Dec 28, 2009 at 2:45 AM, David Brownell davi...@pacbell.net wrote: On Monday 21 December 2009, Yegor Yefremov wrote: My board rev: LMWLV-B Could you forward the USB IDs and device string of your board? I notice that tcl/interface/luminary-lm3s811.cfg doesn't include the USB IDs, so it's at least partially broken. Also its device string doesn't match the other eval boards; that's suspicious, though not necessarily wrong. Plus ... that config file isn't actually *used* anywhere in the tree! I propose fixing that so that it's specific to the old rev B boards (won't ever support SWO), and let everyone else use an updated luminary.cfg (using icdi layout, which can switch port B between SWO and UART). On Linux the /proc/bus/usb/devices file has a section with that data. (Some systems put it in /dev/.../usb/devices instead.) On Windows I suppose it's somewhere in the device properties. Do you mean this one got via lsusb? Bus 001 Device 002: ID 0403:bcd9 Future Technology Devices International, Ltd This is lsusb -v one: Bus 001 Device 002: ID 0403:bcd9 Future Technology Devices International, Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0403 Future Technology Devices International, Ltd idProduct 0xbcd9 bcdDevice5.00 iManufacturer 1 LMI iProduct2 Stellaris Evaluation Board iSerial 3 LM01 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 2 Stellaris Evaluation Board Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 2 Stellaris Evaluation Board Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Status: 0x (Bus Powered) Yegor ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
On Monday 28 December 2009, Yegor Yefremov wrote: On Mon, Dec 28, 2009 at 2:45 AM, David Brownell davi...@pacbell.net wrote: On Monday 21 December 2009, Yegor Yefremov wrote: My board rev: LMWLV-B Could you forward the USB IDs and device string of your board? I notice that tcl/interface/luminary-lm3s811.cfg doesn't include the USB IDs, so it's at least partially broken. Also its device string doesn't match the other eval boards; that's suspicious, though not necessarily wrong. Plus ... that config file isn't actually *used* anywhere in the tree! I propose fixing that so that it's specific to the old rev B boards (won't ever support SWO), and let everyone else use an updated luminary.cfg (using icdi layout, which can switch port B between SWO and UART). Do you mean this one got via lsusb? If that Rev B board is the only Stellaris eval board you have on that machine, yes that's the exact info I needed: idVendor 0x0403 Future Technology Devices International, Ltd idProduct 0xbcd9 Same USB IDs as other eval boards. bcdDevice5.00 iManufacturer 1 LMI iProduct2 Stellaris Evaluation Board ... and same device string, too. As I suspected. Thanks, I'll send a patch updating things. - Dave ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
On Monday 21 December 2009, Yegor Yefremov wrote: On Fri, Dec 18, 2009 at 3:58 PM, Charles Vaughn cvau...@gmail.com wrote: What revision is your board? The title is a bit out of sync with the issue, as in June it appears TI multiplexed SWO and JTAG. My board rev is LMWLV-C. My board rev: LMWLV-B (So $SUBJECT is misleading -- board revision is the issue, not chip revision.) Charles, what was your final resolution for this? ISTR you found that using ft2232_layout luminary_icdi instead of ft2232_layout evb_lm3s811 made it work. In which case we will be wanting the 0.4 release to go out with some fix, maybe just a new rev C board config. We'll want to know the difference between the layouts when we (eventually) do something with with SWV trace data collection ... if I understand things correctly. - Dave ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
Yegor, On Monday 21 December 2009, Yegor Yefremov wrote: My board rev: LMWLV-B Could you forward the USB IDs and device string of your board? I notice that tcl/interface/luminary-lm3s811.cfg doesn't include the USB IDs, so it's at least partially broken. Also its device string doesn't match the other eval boards; that's suspicious, though not necessarily wrong. Plus ... that config file isn't actually *used* anywhere in the tree! I propose fixing that so that it's specific to the old rev B boards (won't ever support SWO), and let everyone else use an updated luminary.cfg (using icdi layout, which can switch port B between SWO and UART). On Linux the /proc/bus/usb/devices file has a section with that data. (Some systems put it in /dev/.../usb/devices instead.) On Windows I suppose it's somewhere in the device properties. - Dave ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
On Fri, Dec 18, 2009 at 3:58 PM, Charles Vaughn cvau...@gmail.com wrote: What revision is your board? The title is a bit out of sync with the issue, as in June it appears TI multiplexed SWO and JTAG. My board rev is LMWLV-C. My board rev: LMWLV-B Yegor ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
On Thu, Dec 17, 2009 at 7:52 PM, Charles Vaughn cvau...@gmail.com wrote: I've recently purchased an LM3S811 evaluation board. I've tried to connect to it with OpenOCD, but I've met very little success even initiating a connection. When I use the version of OpenOCD available from Ubuntu repositories (r2403), I get the following error: m...@mint /usr/share/openocd/scripts $ sudo openocd -f interface/luminary.cfg -f target/lm3s811.cfg Open On-Chip Debugger 0.2.0-in-development (2009-06-30-01:11) svn:r2403 BUGS? Read /usr/share/doc/openocd/BUGS $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ 500 kHz jtag_nsrst_delay: 100 jtag_ntrst_delay: 100 Error: JTAG communication failure: check connection, JTAG interface, target power etc. Error: trying to validate configured JTAG chain anyway... Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x3F. tap=lm3s811.cpu pos=0 expected 0x1 got 3 Warn : Could not validate JTAG chain, continuing anyway... Warn : Invalid ACK in SWJDP transaction Warn : Invalid ACK in SWJDP transaction Warn : Invalid ACK in SWJDP transaction Warn : Invalid ACK in SWJDP transaction Warn : Block read error address 0xe000ed00, count 0x1 Warn : Invalid ACK in SWJDP transaction When I use version 0.3.1 or check out the latest with GIT, I get this error message: Error: 409 14198 core.c:905 jtag_examine_chain_check(): JTAG scan chain interrogation failed: all ones I've tried the following scripts: board/ek-lm3s811.cfg interface/luminary.cfg target/lm3s811.cfg interface/luminary.cfg target/stellaris.cfg The only difference is when using the board/ek-lm3s811.cfg the board does visibly reset. I've changed the jtag_khz to 100 and 1, nrst delay to 1, all with no change in result. My best guess is that there is some difference in the C2 revision of the chips that's causing this, though reviewing the datasheet, I see no difference other than device ID. This is a christmas present for a friend, so I'd appreciate any help... I've just pulled the latest changes from OpenOCD git repo and tried to connect to my LM3S811 board with openocd.cfg containing: source [ find interface/luminary.cfg ] source [ find target/stellaris.cfg ] This is output from flash info 0: TI/LMI Stellaris information: Chip is class 0 (Sandstorm) LM3S811 rev C2 did1: 0x0032002d, arch: 0x32002d, eproc: ARMv7M, ramsize: 8k, flashsize: 64k master clock: 6000kHz, rcc is 0x0, rcc2 is 0x0 pagesize: 1024, pages: 64, lockbits: 32, pages per lockbit: 2 Regards, Yegor ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
What revision is your board? The title is a bit out of sync with the issue, as in June it appears TI multiplexed SWO and JTAG. My board rev is LMWLV-C. On Fri, Dec 18, 2009 at 3:13 AM, Yegor Yefremov yegorsli...@googlemail.comwrote: On Thu, Dec 17, 2009 at 7:52 PM, Charles Vaughn cvau...@gmail.com wrote: I've recently purchased an LM3S811 evaluation board. I've tried to connect to it with OpenOCD, but I've met very little success even initiating a connection. When I use the version of OpenOCD available from Ubuntu repositories (r2403), I get the following error: m...@mint /usr/share/openocd/scripts $ sudo openocd -f interface/luminary.cfg -f target/lm3s811.cfg Open On-Chip Debugger 0.2.0-in-development (2009-06-30-01:11) svn:r2403 BUGS? Read /usr/share/doc/openocd/BUGS $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ 500 kHz jtag_nsrst_delay: 100 jtag_ntrst_delay: 100 Error: JTAG communication failure: check connection, JTAG interface, target power etc. Error: trying to validate configured JTAG chain anyway... Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x3F. tap=lm3s811.cpu pos=0 expected 0x1 got 3 Warn : Could not validate JTAG chain, continuing anyway... Warn : Invalid ACK in SWJDP transaction Warn : Invalid ACK in SWJDP transaction Warn : Invalid ACK in SWJDP transaction Warn : Invalid ACK in SWJDP transaction Warn : Block read error address 0xe000ed00, count 0x1 Warn : Invalid ACK in SWJDP transaction When I use version 0.3.1 or check out the latest with GIT, I get this error message: Error: 409 14198 core.c:905 jtag_examine_chain_check(): JTAG scan chain interrogation failed: all ones I've tried the following scripts: board/ek-lm3s811.cfg interface/luminary.cfg target/lm3s811.cfg interface/luminary.cfg target/stellaris.cfg The only difference is when using the board/ek-lm3s811.cfg the board does visibly reset. I've changed the jtag_khz to 100 and 1, nrst delay to 1, all with no change in result. My best guess is that there is some difference in the C2 revision of the chips that's causing this, though reviewing the datasheet, I see no difference other than device ID. This is a christmas present for a friend, so I'd appreciate any help... I've just pulled the latest changes from OpenOCD git repo and tried to connect to my LM3S811 board with openocd.cfg containing: source [ find interface/luminary.cfg ] source [ find target/stellaris.cfg ] This is output from flash info 0: TI/LMI Stellaris information: Chip is class 0 (Sandstorm) LM3S811 rev C2 did1: 0x0032002d, arch: 0x32002d, eproc: ARMv7M, ramsize: 8k, flashsize: 64k master clock: 6000kHz, rcc is 0x0, rcc2 is 0x0 pagesize: 1024, pages: 64, lockbits: 32, pages per lockbit: 2 Regards, Yegor ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
On Thursday 17 December 2009, Charles Vaughn wrote: Error: 409 14198 core.c:905 jtag_examine_chain_check(): JTAG scan chain interrogation failed: all ones I vaguely recall that some of the early Stellaris boards (like that one!) actually wired up TRST ... other chips don't seem to expose that signal, so it's not wired out of the JTAG adapters' CPLDs either. The all ones could indicate that the TAP is still being held in reset ... perhaps via TRST. I suggest you check your reset_config lines against board schematics, and maybe the code for that specific adapter. There are a bunch of Stellaris eval boards, with minor differences in JTAG wiring. I'm not sure which config is right for that board. I use interface/luminary.cfg on a different board and it's fine, so I'd expect once you sort out this config issue you'll have no problems. - Dave p.s. I also add reset_config srst_nogate to my board's default reset_config srst_only, but I don't recall that anything would care about that. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
Oh fun. I'll take a look. That hadn't occurred to me, but that would make the most sense. On Thu, Dec 17, 2009 at 12:42 PM, David Brownell davi...@pacbell.netwrote: On Thursday 17 December 2009, Charles Vaughn wrote: Error: 409 14198 core.c:905 jtag_examine_chain_check(): JTAG scan chain interrogation failed: all ones I vaguely recall that some of the early Stellaris boards (like that one!) actually wired up TRST ... other chips don't seem to expose that signal, so it's not wired out of the JTAG adapters' CPLDs either. The all ones could indicate that the TAP is still being held in reset ... perhaps via TRST. I suggest you check your reset_config lines against board schematics, and maybe the code for that specific adapter. There are a bunch of Stellaris eval boards, with minor differences in JTAG wiring. I'm not sure which config is right for that board. I use interface/luminary.cfg on a different board and it's fine, so I'd expect once you sort out this config issue you'll have no problems. - Dave p.s. I also add reset_config srst_nogate to my board's default reset_config srst_only, but I don't recall that anything would care about that. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
So I have the C revision of the board, which was released in June of this year. I confirmed TRST being pulled up, with no external control. The revision notes mention SWO support being added, which uses TDO and TMS. I've tried pulling the SWO_EN pin low, but that doesn't do anything, and it seems to operate fine for the windows flash utility. I'm also not able to see any activity other than the RST pin on a scope when running it. Any thoughts? On Thu, Dec 17, 2009 at 1:01 PM, Charles Vaughn cvau...@gmail.com wrote: Oh fun. I'll take a look. That hadn't occurred to me, but that would make the most sense. On Thu, Dec 17, 2009 at 12:42 PM, David Brownell davi...@pacbell.netwrote: On Thursday 17 December 2009, Charles Vaughn wrote: Error: 409 14198 core.c:905 jtag_examine_chain_check(): JTAG scan chain interrogation failed: all ones I vaguely recall that some of the early Stellaris boards (like that one!) actually wired up TRST ... other chips don't seem to expose that signal, so it's not wired out of the JTAG adapters' CPLDs either. The all ones could indicate that the TAP is still being held in reset ... perhaps via TRST. I suggest you check your reset_config lines against board schematics, and maybe the code for that specific adapter. There are a bunch of Stellaris eval boards, with minor differences in JTAG wiring. I'm not sure which config is right for that board. I use interface/luminary.cfg on a different board and it's fine, so I'd expect once you sort out this config issue you'll have no problems. - Dave p.s. I also add reset_config srst_nogate to my board's default reset_config srst_only, but I don't recall that anything would care about that. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
On Thursday 17 December 2009, Charles Vaughn wrote: revision notes mention SWO support being added, which uses TDO and TMS. Your problem signal is TDO (that's giving all ones output), so this looks like the right track... Looks to me like the way they added SWO support involved adding an additional control signal, which the previous revision didn't use. And thus, the previous OpenOCD driver didn't use... so one theory is that said signal is driven wrong, disabling JTAG. In the best of worlds, they used the same signal as various other boards, so you could just switch to the other interface config (which doesn't advertise itself as being for the '811 board). ISTR those go through CPLDs ... this one seems not to do that, I mis-remembered. Less optimally you'd have to tweak src/jtag/driver/ft2232.c to understand this as yet another variant. - Dave ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] All ones when connecting to LM3S811 Evaluation Board (Chip Revision C2)
So I've done a little more scope probing, and I can see a TCK out of the FT2232, but not on the TCK pin, so that backs that up. I'll take a closer look at the schematics and try to find out what drives that. On Thu, Dec 17, 2009 at 10:35 PM, David Brownell davi...@pacbell.netwrote: On Thursday 17 December 2009, Charles Vaughn wrote: revision notes mention SWO support being added, which uses TDO and TMS. Your problem signal is TDO (that's giving all ones output), so this looks like the right track... Looks to me like the way they added SWO support involved adding an additional control signal, which the previous revision didn't use. And thus, the previous OpenOCD driver didn't use... so one theory is that said signal is driven wrong, disabling JTAG. In the best of worlds, they used the same signal as various other boards, so you could just switch to the other interface config (which doesn't advertise itself as being for the '811 board). ISTR those go through CPLDs ... this one seems not to do that, I mis-remembered. Less optimally you'd have to tweak src/jtag/driver/ft2232.c to understand this as yet another variant. - Dave ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
