- pacsat-dev - mailman.amsat.org

Re: Info about debug device
by Bob Stricklin 05 Jan '24

05 Jan '24

Thank you sir. Bob On Jan 5, 2024, at 10:09 AM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org> wrote: BTW, I'm putting both in the same box but including all the instructions that came with it. Note that the instructions assume you are going to be using this with a thing called a SensorTag so you can ignore them :-) I don't care which one you return to be with the connector replace, btw. Good luck! 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software On Fri, Jan 5, 2024 at 10:59 AM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc<mailto:[email protected]>> wrote: Bob, et al: FWIW, the official name of the little boards I'm send is TI Simplelink SensorTag Devpack. I'm including a photo of the one that works. You can see when you look at a new one) that the replacement connector goes on the opposite side of the board from the existing 10-pin connector. The existing one is female with no key. The new one is male with shroud and key. The key is on the outside edge of the board, and the connector is on the opposite side of the board from the chip (on the same side as the larger connector. I tried to load code using it (despite not being connect to the RTIHU) and got the attached error message. I used the xdsdfu utility that the error talks about and discovered this: ./ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -e USB Device Firmware Upgrade Utility Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... <<<< Device 0 >>>> VID: 0x0451 PID: 0xbef3 Device Name: XDS110 with CMSIS-DAP Version: 2.2.5.1 Manufacturer: Texas Instruments Serial Num: L787 Mode: Runtime Configuration: Standard Found 1 device. Notice the serial number L787. One of my working ones has the serial number L3122222. So letter L and 7 digits. I am setting yours to L31444444 and L31555555. Like this: bfisher@skylab:~$ ./ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -m USB Device Firmware Upgrade Utility Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... <<<< Device 0 >>>> VID: 0x0451 PID: 0xbef3 Device Name: XDS110 with CMSIS-DAP Version: 2.2.5.1 Manufacturer: Texas Instruments Serial Num: L787 Mode: Runtime Configuration: Standard Switching device into DFU mode. bfisher@skylab:~$ ./ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -s L3144444 -r USB Device Firmware Upgrade Utility Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... Setting serial number to "L3144444"... And now the box asks me to select whether I want to use TIXDS110_Connection-S/N:L31444444. I said yes, and it said to update the firmware from 2.2.5.1 to 3.0.0.15 (and there was an update button). This works ok, and now since I am not connected to the RTIHU, it is correctly claiming that it can't connect to the target. I'll update the serial and firmware on the second one I send you as well. 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Info about debug device
by Burns Fisher (AMSAT) 05 Jan '24

05 Jan '24

Bob, et al: FWIW, the official name of the little boards I'm send is TI Simplelink SensorTag Devpack. I'm including a photo of the one that works. You can see when you look at a new one) that the replacement connector goes on the opposite side of the board from the existing 10-pin connector. The existing one is female with no key. The new one is male with shroud and key. The key is on the outside edge of the board, and the connector is on the opposite side of the board from the chip (on the same side as the larger connector. I tried to load code using it (despite not being connect to the RTIHU) and got the attached error message. I used the xdsdfu utility that the error talks about and discovered this: ./ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -e USB Device Firmware Upgrade Utility Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... <<<< Device 0 >>>> VID: 0x0451 PID: 0xbef3 Device Name: XDS110 with CMSIS-DAP Version: 2.2.5.1 Manufacturer: Texas Instruments Serial Num: L787 Mode: Runtime Configuration: Standard Found 1 device. Notice the serial number L787. One of my working ones has the serial number L3122222. So letter L and 7 digits. I am setting yours to L31444444 and L31555555. Like this: bfisher@skylab:~$ ./ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -m USB Device Firmware Upgrade Utility Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... <<<< Device 0 >>>> VID: 0x0451 PID: 0xbef3 Device Name: XDS110 with CMSIS-DAP Version: 2.2.5.1 Manufacturer: Texas Instruments Serial Num: L787 Mode: Runtime Configuration: Standard Switching device into DFU mode. bfisher@skylab:~$ ./ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -s L3144444 -r USB Device Firmware Upgrade Utility Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... Setting serial number to "L3144444"... And now the box asks me to select whether I want to use TIXDS110_Connection-S/N:L31444444. I said yes, and it said to update the firmware from 2.2.5.1 to 3.0.0.15 (and there was an update button). This works ok, and now since I am not connected to the RTIHU, it is correctly claiming that it can't connect to the target. I'll update the serial and firmware on the second one I send you as well. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 1

Messages from Test Device and Errors for a test code load.
by Bob Stricklin 05 Jan '24

05 Jan '24

Test Device shows some error but it may be the results are fine since it says succeeded. The error info may be related to a config issue in HalCoGen or the ID number Burns was telling us about. May also be the JTAG is not correct yet. Bob

1 0

Reset pull up
by Bob Stricklin 05 Jan '24

05 Jan '24

When I put nTRST pull-up back on board the Test Device passes but still not letting me load code. I will put error info later. Bob

1 0

Re: Launchpad schematics
by Corey Minyard 05 Jan '24

05 Jan '24

On Thu, Jan 4, 2024 at 8:00 PM Corey Minyard via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Schematics are here: > > https://www.ti.com/lit/df/sprr401/sprr401.pdf?ts=1704419116024 > > Oddly enough, I don't see a pull up or down on the TRSTN pin. The > rest of the pins have unpopulated pullups, I assume you would need > them if you removed the zero-ohm resistors on the XDS100. I read a little more, and I figured out what is happening with the TRSTN pin on the Launchpad. The XDS100 checks pin J12-8 from the external JTAG connector, the JTAG_SEL pin. If it detects that an external JTAG device is present, it will tristate all the JTAG lines. If it doesn't detect the external JTAG, it will drive the TRSTN line itself. > > -corey > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Launchpad schematics
by Corey Minyard 05 Jan '24

05 Jan '24

Schematics are here: https://www.ti.com/lit/df/sprr401/sprr401.pdf?ts=1704419116024 Oddly enough, I don't see a pull up or down on the TRSTN pin. The rest of the pins have unpopulated pullups, I assume you would need them if you removed the zero-ohm resistors on the XDS100. -corey

1 0

JTAG Asorted backup Info
by Bob Stricklin 04 Jan '24

04 Jan '24

Asorted info used to debug JTAG interface. Bob

1 0

Pacsat dev mtg 1/4/2024
by Bill 04 Jan '24

04 Jan '24

Pacsat dev mtg 1/4/2024 Thu, Jan 4, 2024 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/420461461 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (224) 501-3412 - One-touch: tel:+12245013412,,420461461# Access Code: 420-461-461 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 420 461 461 Or dial directly: 420461461(a)67.217.95.2 or 67.217.95.2##420461461 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Fwd: JTAG
by Bob Stricklin 04 Jan '24

04 Jan '24

All, As reported I had an issue with the five volt supply failing and the TMS570. I have raved these chips, purchased new voltage reg from mouser and have all these back on the PCB and functioning. Still not seeing proper JTAG function. I am working on this now. I have posted information to the GitHub on a revised JTAG interface schematic and PCB layout. Below attached a couple of photos showing what is supposed to be the same connection for JTAG. This is not working yet though and needs more study. I will post additional info on backup used to develop JTAG interface later. With the CPU back on the PCB the current pull is about 60 mA and power supply are holding properly. Bob Begin forwarded message: From: Bob Stricklin <bstricklin51(a)icloud.com<mailto:[email protected]>> Subject: JTAG Date: January 4, 2024 at 2:22:18 PM CST To: Bob Stricklin <bstrick(a)n5brg.com<mailto:[email protected]>> [cid:[email protected]] [cid:[email protected]] [cid:[email protected]]

1 0

Progress On board
by Bob Stricklin 01 Jan '24

01 Jan '24

I tested Jim's code and saw issues. I tested additional code that I put together and also saw issues. I also built a package that I called Do Nothing which did not use anything but a loop running in flash and this would not load. I became convinced the problem was the JTAG interface was not working properly even though the TEST DEVICE in CCS indicated this did work. I think the TEST DEVICE routine was running some sort of a scan chain routine and when you load a program more is involved. I was seeing errors indicating the TSL570 could not be reset. I did not bring out the reset line on the JTAG connector because it is not a normal signal. TI does show having this connection available in one of their suggested interface diagrams. Due to the issues I started working on the PCBs I built to use them as the interface. I did not study the TI diagram well before making the PCB so it needed a lot of cut and jumpers and resistors added. It took me more than a half day to work through this. This morning I got back to testing with the newly built JTAG interface board. Things still were not working so I started to look for other issues. At this point I lost my 3.3V supply voltage. Then I found there was a short on the regulated 5V output. This all took serval hours to get through. So tonight I removed all the offending chips and since the TMS570 was getting hot I removed it as well. I will have to order more of the 5V regulators because the one I removed is not usable. It will be Wednesday before I can get these from Mouser. My thought is to put back what I can minus the TMS570. Then check the voltages and possibly the signals on the JTAG pins coming from the XDS110 through my JTAG interface board and finally to the CPU pads. When I see I have voltages from regulators back the way they are supposed to be I will solder on the TMS570 and then start trying to test the JTAG interface and code again. Sorry it is going slow here. Bob

1 0