I received the two Devpack programming boards from Burns. Replaced connectors on both boards and I have tested them on the Quad board and they both worked fine.
Returning one of these to Burns today.
Bob
On Jan 5, 2024, at 11:21 AM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev@amsat.orgmailto:pacsat-dev@amsat.org> wrote:
I included a little extra. The connectors that I had ordered just arrived (hot off the plane from Singapore) and I realized that Newark Electroncis had apparently switched the part number around on me, and they were surface mount! Not useful for me in this case, but if they are useful for anything you build, I sent you a few. 73,
Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software
On Fri, Jan 5, 2024 at 11:28 AM Bob Stricklin via pacsat-dev <pacsat-dev@amsat.orgmailto:pacsat-dev@amsat.org> wrote: Thank you sir.
Bob
On Jan 5, 2024, at 10:09 AM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev@amsat.orgmailto:pacsat-dev@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@fisher.ccmailto:wb1fj@fisher.cc> 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@amsat.orgmailto:pacsat-dev@amsat.org View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave@amsat.orgmailto:pacsat-dev-leave@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.orghttps://mailman.amsat.org/
-----------------------------------------------------------
pacsat-dev mailing list -- pacsat-dev@amsat.orgmailto:pacsat-dev@amsat.org View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave@amsat.orgmailto:pacsat-dev-leave@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.orghttps://mailman.amsat.org/
-----------------------------------------------------------
pacsat-dev mailing list -- pacsat-dev@amsat.orgmailto:pacsat-dev@amsat.org View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave@amsat.orgmailto:pacsat-dev-leave@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
participants (1)
-
Bob Stricklin