Email Detail
Show an email
GET /hyperkitty/api/list/[email protected]/email/HGBDREMVRUK2SFYWZMAFPPQA62JIRZPF/
{ "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/HGBDREMVRUK2SFYWZMAFPPQA62JIRZPF/", "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/", "message_id": "[email protected]", "message_id_hash": "HGBDREMVRUK2SFYWZMAFPPQA62JIRZPF", "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/HGBDREMVRUK2SFYWZMAFPPQA62JIRZPF/", "sender": { "address": "wa4cwi (a) bellsouth.net", "mailman_id": "4aa6f1e3f4cd4bf4b1492e47285ca527", "emails": "https://mailman.amsat.org/hyperkitty/api/sender/4aa6f1e3f4cd4bf4b1492e47285ca527/emails/" }, "sender_name": "Jim McCullers", "subject": "[pacsat-dev] Re: Progress", "date": "2023-12-29T15:49:12Z", "parent": null, "children": [], "votes": { "likes": 0, "dislikes": 0, "status": "neutral" }, "content": "\n\nCongrats Bob. Good progress.\nI'm back in Birmingham.\n\nAttached is the Blinky source code which includes the last HCG I did for the\nboard.\nI'm certain that many changes will be required but it's a start.\n\nNot certain if Blinky, at least at the current level, is anything we want on\nthe github repository.\nDiscussion item for next week's meeting.\n\n73,\n\nJim McCullers\nWA4CWI\n\nAll,\n\nI have worked on the board a few hours over the past few days.\n\nI got the JTAG interface put together and set this up for testing with the\nPC and a XDS110. When I connected them together and powered things up I\ninitially saw the LEDs on the PCB come on which is what I expect.\nUnfortunately when I started trying to communicate with using the JTAG I so\nthe LEDs go off and immediatly I checked the 3.3V supply and found it was\nbouncing up to about 4 volts. Not good. So I powered down and after some\nthought I decided the 3.3 voltage regulator was not stable enough to support\nout board. It's working in a feed back mode trying to hold the 3.3V while\nadjusting Pulse Width Modulation of the LC circuit. \n\nI tested the board with an external 3.3V supply and noticed the current draw\nhad increased to about 240 mA. Concerning.\n\nI have removed the MAX regulator and put a LDO fixed 3.3V regulator on\nhanging in the air. #.3V supply now seems solid.\n\nI got everything reconnected to JTAG and started again trying to test. When\nI tried Test Connection I was seeing a message about missing a file which I\nlater realized was the HalCoGen file defining the board info. I then tried\nthe one from the PAcSat project that I had but this was not working either.\nSo I used the setup system to create a basic interface with a 4 wire JTAG.\nThe I select Test Connection and this time it seems to be working. Still\nmore work needed to learn what it is telling be but the two successes at the\nbottom of the listing below are encouraging.\n\nIn this mode the supply current is down to 190 mA feeding into the 5V supply\nwhich feeds everything on the board. May be believable.\n\nNow time to create a proper HalCoGen file.\n\n\nBob N5BRG\n\n\n[Start: Texas Instruments XDS110 USB Debug Probe]\n\nExecute the command:\n\n%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity\n\n[Result]\n\n\n-----[Print the board config\npathname(s)]------------------------------------\n\n/home/bob/.ti/ccs1250/0/0/BrdDat/testBoard.dat\n\n-----[Print the reset-command software\nlog-file]-----------------------------\n\nThis utility has selected a 100/110/510 class product.\nThis utility will load the adapter 'libjioxds110.so'.\nThe library build date was 'Sep 6 2023'.\nThe library build time was '09:54:42'.\nThe library package version is '9.13.0.00201'.\nThe library component version is '35.35.0.0'.\nThe controller does not use a programmable FPGA.\nThe controller has a version number of '5' (0x00000005).\nThe controller has an insertion length of '0' (0x00000000).\nThis utility will attempt to reset the controller.\nThis utility has successfully reset the controller.\nNote: This is a key indicator\n\n-----[Print the reset-command hardware\nlog-file]-----------------------------\n\nThe scan-path will be reset by toggling the JTAG TRST signal.\nThe controller is the XDS110 with USB interface.\nThe link from controller to target is direct (without cable).\nThe software is configured for XDS110 features.\nThe controller cannot monitor the value on the EMU[0] pin.\nNote: We are not using some of these signals so this is OK. Bob\nThe controller cannot monitor the value on the EMU[1] pin.\nThe controller cannot control the timing on output pins.\nThe controller cannot control the timing on input pins.\nThe scan-path link-delay has been set to exactly '0' (0x0000).\n\n-----[Perform the Integrity scan-test on the JTAG\nIR]------------------------\n\nThis test will use blocks of 64 32-bit words.\nThis test will be applied just once.\n\nDo a test using 0xFFFFFFFF.\nScan tests: 1, skipped: 0, failed: 0\nDo a test using 0x00000000.\nScan tests: 2, skipped: 0, failed: 0\nDo a test using 0xFE03E0E2.\nScan tests: 3, skipped: 0, failed: 0\nDo a test using 0x01FC1F1D.\nScan tests: 4, skipped: 0, failed: 0\nDo a test using 0x5533CCAA.\nScan tests: 5, skipped: 0, failed: 0\nDo a test using 0xAACC3355.\nScan tests: 6, skipped: 0, failed: 0\nAll of the values were scanned correctly.\nNote: Good news\n\nThe JTAG IR Integrity scan-test has succeeded.\n\n-----[Perform the Integrity scan-test on the JTAG\nDR]------------------------\n\nThis test will use blocks of 64 32-bit words.\nThis test will be applied just once.\n\nDo a test using 0xFFFFFFFF.\nScan tests: 1, skipped: 0, failed: 0\nDo a test using 0x00000000.\nScan tests: 2, skipped: 0, failed: 0\nDo a test using 0xFE03E0E2.\nScan tests: 3, skipped: 0, failed: 0\nDo a test using 0x01FC1F1D.\nScan tests: 4, skipped: 0, failed: 0\nDo a test using 0x5533CCAA.\nScan tests: 5, skipped: 0, failed: 0\nDo a test using 0xAACC3355.\nScan tests: 6, skipped: 0, failed: 0\nAll of the values were scanned correctly.\nNote: Good news\n\nThe JTAG DR Integrity scan-test has succeeded.\n\n-----[An error has occurred and this utility has\naborted]--------------------\n\nThis error is generated by TI's USCIF driver or utilities.\n\nThe value is '-382' (0xfffffe82).\nThe title is 'SC_ERR_LIST_SUBPATH_DELETE'.\n\nThe explanation is:\nAn error occurred when deleting a sub-path from the sub-path select list.\nThe sub-path may already be off the list.\nThus it cannot be deleted from that list.\n\n[End: Texas Instruments XDS110 USB Debug Probe]\n\n[Start: Texas Instruments XDS110 USB Debug Probe_0]\n\nExecute the command:\n\n%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity\n\n[Result]\n\n\n-----[Print the board config\npathname(s)]------------------------------------\n\n/home/bob/.ti/ccs1250/0/0/BrdDat/testBoard.dat\n\n-----[Print the reset-command software\nlog-file]-----------------------------\n\nThis utility has selected a 100/110/510 class product.\nThis utility will load the adapter 'libjioxds110.so'.\nThe library build date was 'Sep 6 2023'.\nThe library build time was '09:54:42'.\nThe library package version is '9.13.0.00201'.\nThe library component version is '35.35.0.0'.\nThe controller does not use a programmable FPGA.\nThe controller has a version number of '5' (0x00000005).\nThe controller has an insertion length of '0' (0x00000000).\nThis utility will attempt to reset the controller.\nThis utility has successfully reset the controller.\n\n-----[Print the reset-command hardware\nlog-file]-----------------------------\n\nThe scan-path will be reset by toggling the JTAG TRST signal.\nThe controller is the XDS110 with USB interface.\nThe link from controller to target is direct (without cable).\nThe software is configured for XDS110 features.\nThe controller cannot monitor the value on the EMU[0] pin.\nThe controller cannot monitor the value on the EMU[1] pin.\nThe controller cannot control the timing on output pins.\nThe controller cannot control the timing on input pins.\nThe scan-path link-delay has been set to exactly '0' (0x0000).\n\n-----[Perform the Integrity scan-test on the JTAG\nIR]------------------------\n\nThis test will use blocks of 64 32-bit words.\nThis test will be applied just once.\n\nDo a test using 0xFFFFFFFF.\nScan tests: 1, skipped: 0, failed: 0\nDo a test using 0x00000000.\nScan tests: 2, skipped: 0, failed: 0\nDo a test using 0xFE03E0E2.\nScan tests: 3, skipped: 0, failed: 0\nDo a test using 0x01FC1F1D.\nScan tests: 4, skipped: 0, failed: 0\nDo a test using 0x5533CCAA.\nScan tests: 5, skipped: 0, failed: 0\nDo a test using 0xAACC3355.\nScan tests: 6, skipped: 0, failed: 0\nAll of the values were scanned correctly.\n\nThe JTAG IR Integrity scan-test has succeeded.\n\n-----[Perform the Integrity scan-test on the JTAG\nDR]------------------------\n\nThis test will use blocks of 64 32-bit words.\nThis test will be applied just once.\n\nDo a test using 0xFFFFFFFF.\nScan tests: 1, skipped: 0, failed: 0\nDo a test using 0x00000000.\nScan tests: 2, skipped: 0, failed: 0\nDo a test using 0xFE03E0E2.\nScan tests: 3, skipped: 0, failed: 0\nDo a test using 0x01FC1F1D.\nScan tests: 4, skipped: 0, failed: 0\nDo a test using 0x5533CCAA.\nScan tests: 5, skipped: 0, failed: 0\nDo a test using 0xAACC3355.\nScan tests: 6, skipped: 0, failed: 0\nAll of the values were scanned correctly.\n\nThe JTAG DR Integrity scan-test has succeeded.\n\n[End: Texas Instruments XDS110 USB Debug Probe_0]\n\n\n-----------------------------------------------------------\n\npacsat-dev mailing list -- [email protected] View archives of this\nmailing list at\nhttps://mailman.amsat.org/hyperkitty/list/[email protected]\nTo unsubscribe send an email to [email protected] Manage all of\nyour AMSAT-NA mailing list preferences at https://mailman.amsat.org\n", "attachments": [ { "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/HGBDREMVRUK2SFYWZMAFPPQA62JIRZPF/", "counter": 2, "name": "Blinky.zip", "content_type": "application/x-zip-compressed", "encoding": null, "size": 1467824, "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/HGBDREMVRUK2SFYWZMAFPPQA62JIRZPF/attachment/2/Blinky.zip" } ] }