Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/5ANWKDTPNNFJSMC2QSJXMIYIIVUCNBID/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "5ANWKDTPNNFJSMC2QSJXMIYIIVUCNBID",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/5ANWKDTPNNFJSMC2QSJXMIYIIVUCNBID/?format=api",
    "sender": {
        "address": "bstrick (a) N5BRG.COM",
        "mailman_id": "953542c988dd4c549175bb02a8a6a1ed",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/953542c988dd4c549175bb02a8a6a1ed/emails/?format=api"
    },
    "sender_name": "Bob Stricklin",
    "subject": "[pacsat-dev] Re: Info about debug device",
    "date": "2024-01-05T16:28:01Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Thank you sir.\r\n\r\nBob\r\n\r\nOn Jan 5, 2024, at 10:09 AM, Burns Fisher (AMSAT) via pacsat-dev <[email protected]> wrote:\r\n\r\n\r\nBTW, 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 :-)\r\n\r\nI don't care which one you return to be with the connector replace, btw.\r\n\r\nGood luck!\r\n\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n\r\nOn Fri, Jan 5, 2024 at 10:59 AM Burns Fisher (AMSAT) <[email protected]<mailto:[email protected]>> wrote:\r\nBob, et al:\r\n\r\nFWIW, the official name of the little boards I'm send is TI Simplelink SensorTag Devpack.\r\n\r\nI'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.\r\n\r\nI 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:\r\n\r\n./ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -e\r\n\r\nUSB Device Firmware Upgrade Utility\r\nCopyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.\r\n\r\nScanning USB buses for supported XDS110 devices...\r\n<<<< Device 0 >>>>\r\nVID: 0x0451    PID: 0xbef3\r\nDevice Name:   XDS110 with CMSIS-DAP\r\nVersion:       2.2.5.1\r\nManufacturer:  Texas Instruments\r\nSerial Num:    L787\r\nMode:          Runtime\r\nConfiguration: Standard\r\nFound 1 device.\r\n\r\nNotice 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:\r\n\r\n\r\nbfisher@skylab:~$ ./ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -m\r\nUSB Device Firmware Upgrade Utility\r\nCopyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.\r\nScanning USB buses for supported XDS110 devices...\r\n<<<< Device 0 >>>>\r\nVID: 0x0451    PID: 0xbef3\r\nDevice Name:   XDS110 with CMSIS-DAP\r\nVersion:       2.2.5.1\r\nManufacturer:  Texas Instruments\r\nSerial Num:    L787\r\nMode:          Runtime\r\nConfiguration: Standard\r\nSwitching device into DFU mode.\r\n\r\nbfisher@skylab:~$ ./ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -s L3144444 -r\r\nUSB Device Firmware Upgrade Utility\r\nCopyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.\r\nScanning USB buses for supported XDS110 devices...\r\nSetting serial number to \"L3144444\"...\r\n\r\nAnd 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.\r\n\r\nI'll update the serial and firmware on the second one I send you as well.\r\n\r\n\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/5ANWKDTPNNFJSMC2QSJXMIYIIVUCNBID/?format=api",
            "counter": 2,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "utf-8",
            "size": 8107,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/5ANWKDTPNNFJSMC2QSJXMIYIIVUCNBID/attachment/2/attachment.html"
        }
    ]
}