December 2023 - pacsat-dev - mailman.amsat.org

Re: Progress
by Jim McCullers 29 Dec '23

29 Dec '23

Congrats Bob. Good progress. I'm back in Birmingham. Attached is the Blinky source code which includes the last HCG I did for the board. I'm certain that many changes will be required but it's a start. Not certain if Blinky, at least at the current level, is anything we want on the github repository. Discussion item for next week's meeting. 73, Jim McCullers WA4CWI All, I have worked on the board a few hours over the past few days. I got the JTAG interface put together and set this up for testing with the PC and a XDS110. When I connected them together and powered things up I initially saw the LEDs on the PCB come on which is what I expect. Unfortunately when I started trying to communicate with using the JTAG I so the LEDs go off and immediatly I checked the 3.3V supply and found it was bouncing up to about 4 volts. Not good. So I powered down and after some thought I decided the 3.3 voltage regulator was not stable enough to support out board. It's working in a feed back mode trying to hold the 3.3V while adjusting Pulse Width Modulation of the LC circuit. I tested the board with an external 3.3V supply and noticed the current draw had increased to about 240 mA. Concerning. I have removed the MAX regulator and put a LDO fixed 3.3V regulator on hanging in the air. #.3V supply now seems solid. I got everything reconnected to JTAG and started again trying to test. When I tried Test Connection I was seeing a message about missing a file which I later realized was the HalCoGen file defining the board info. I then tried the one from the PAcSat project that I had but this was not working either. So I used the setup system to create a basic interface with a 4 wire JTAG. The I select Test Connection and this time it seems to be working. Still more work needed to learn what it is telling be but the two successes at the bottom of the listing below are encouraging. In this mode the supply current is down to 190 mA feeding into the 5V supply which feeds everything on the board. May be believable. Now time to create a proper HalCoGen file. Bob N5BRG [Start: Texas Instruments XDS110 USB Debug Probe] Execute the command: %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity [Result] -----[Print the board config pathname(s)]------------------------------------ /home/bob/.ti/ccs1250/0/0/BrdDat/testBoard.dat -----[Print the reset-command software log-file]----------------------------- This utility has selected a 100/110/510 class product. This utility will load the adapter 'libjioxds110.so'. The library build date was 'Sep 6 2023'. The library build time was '09:54:42'. The library package version is '9.13.0.00201'. The library component version is '35.35.0.0'. The controller does not use a programmable FPGA. The controller has a version number of '5' (0x00000005). The controller has an insertion length of '0' (0x00000000). This utility will attempt to reset the controller. This utility has successfully reset the controller. Note: This is a key indicator -----[Print the reset-command hardware log-file]----------------------------- The scan-path will be reset by toggling the JTAG TRST signal. The controller is the XDS110 with USB interface. The link from controller to target is direct (without cable). The software is configured for XDS110 features. The controller cannot monitor the value on the EMU[0] pin. Note: We are not using some of these signals so this is OK. Bob The controller cannot monitor the value on the EMU[1] pin. The controller cannot control the timing on output pins. The controller cannot control the timing on input pins. The scan-path link-delay has been set to exactly '0' (0x0000). -----[Perform the Integrity scan-test on the JTAG IR]------------------------ This test will use blocks of 64 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 0 All of the values were scanned correctly. Note: Good news The JTAG IR Integrity scan-test has succeeded. -----[Perform the Integrity scan-test on the JTAG DR]------------------------ This test will use blocks of 64 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 0 All of the values were scanned correctly. Note: Good news The JTAG DR Integrity scan-test has succeeded. -----[An error has occurred and this utility has aborted]-------------------- This error is generated by TI's USCIF driver or utilities. The value is '-382' (0xfffffe82). The title is 'SC_ERR_LIST_SUBPATH_DELETE'. The explanation is: An error occurred when deleting a sub-path from the sub-path select list. The sub-path may already be off the list. Thus it cannot be deleted from that list. [End: Texas Instruments XDS110 USB Debug Probe] [Start: Texas Instruments XDS110 USB Debug Probe_0] Execute the command: %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity [Result] -----[Print the board config pathname(s)]------------------------------------ /home/bob/.ti/ccs1250/0/0/BrdDat/testBoard.dat -----[Print the reset-command software log-file]----------------------------- This utility has selected a 100/110/510 class product. This utility will load the adapter 'libjioxds110.so'. The library build date was 'Sep 6 2023'. The library build time was '09:54:42'. The library package version is '9.13.0.00201'. The library component version is '35.35.0.0'. The controller does not use a programmable FPGA. The controller has a version number of '5' (0x00000005). The controller has an insertion length of '0' (0x00000000). This utility will attempt to reset the controller. This utility has successfully reset the controller. -----[Print the reset-command hardware log-file]----------------------------- The scan-path will be reset by toggling the JTAG TRST signal. The controller is the XDS110 with USB interface. The link from controller to target is direct (without cable). The software is configured for XDS110 features. The controller cannot monitor the value on the EMU[0] pin. The controller cannot monitor the value on the EMU[1] pin. The controller cannot control the timing on output pins. The controller cannot control the timing on input pins. The scan-path link-delay has been set to exactly '0' (0x0000). -----[Perform the Integrity scan-test on the JTAG IR]------------------------ This test will use blocks of 64 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 0 All of the values were scanned correctly. The JTAG IR Integrity scan-test has succeeded. -----[Perform the Integrity scan-test on the JTAG DR]------------------------ This test will use blocks of 64 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 0 All of the values were scanned correctly. The JTAG DR Integrity scan-test has succeeded. [End: Texas Instruments XDS110 USB Debug Probe_0] ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Pacsat dev mtg 12/28/2023
by Bill 28 Dec '23

28 Dec '23

Pacsat dev mtg 12/28/2023 Thu, Dec 28, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/952684413 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (312) 757-3121 - One-touch: tel:+13127573121,,952684413# Access Code: 952-684-413 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 952 684 413 Or dial directly: 952684413(a)67.217.95.2 or 67.217.95.2##952684413 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Progress
by Burns Fisher (AMSAT) 27 Dec '23

27 Dec '23

Looking good. FWIW, when I load a processor on the RT-IHU, the current goes up by 50-100ma (at a bit over 5 volts). As soon as the program is loaded and starts, the current drops again. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Tue, Dec 26, 2023 at 9:02 PM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > All, > > I have worked on the board a few hours over the past few days. > > I got the JTAG interface put together and set this up for testing with the > PC and a XDS110. When I connected them together and powered things up I > initially saw the LEDs on the PCB come on which is what I expect. > Unfortunately when I started trying to communicate with using the JTAG I so > the LEDs go off and immediatly I checked the 3.3V supply and found it was > bouncing up to about 4 volts. Not good. So I powered down and after some > thought I decided the 3.3 voltage regulator was not stable enough to > support out board. It's working in a feed back mode trying to hold the 3.3V > while adjusting Pulse Width Modulation of the LC circuit. > > I tested the board with an external 3.3V supply and noticed the current > draw had increased to about 240 mA. Concerning. > > I have removed the MAX regulator and put a LDO fixed 3.3V regulator on > hanging in the air. #.3V supply now seems solid. > > I got everything reconnected to JTAG and started again trying to test. > When I tried Test Connection I was seeing a message about missing a file > which I later realized was the HalCoGen file defining the board info. I > then tried the one from the PAcSat project that I had but this was not > working either. So I used the setup system to create a basic interface with > a 4 wire JTAG. The I select Test Connection and this time it seems to be > working. Still more work needed to learn what it is telling be but the two > successes at the bottom of the listing below are encouraging. > > In this mode the supply current is down to 190 mA feeding into the 5V > supply which feeds everything on the board. May be believable. > > Now time to create a proper HalCoGen file. > > > Bob N5BRG > > > [Start: Texas Instruments XDS110 USB Debug Probe] > > Execute the command: > > %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity > > [Result] > > > -----[Print the board config > pathname(s)]------------------------------------ > > /home/bob/.ti/ccs1250/0/0/BrdDat/testBoard.dat > > -----[Print the reset-command software > log-file]----------------------------- > > This utility has selected a 100/110/510 class product. > This utility will load the adapter 'libjioxds110.so'. > The library build date was 'Sep 6 2023'. > The library build time was '09:54:42'. > The library package version is '9.13.0.00201'. > The library component version is '35.35.0.0'. > The controller does not use a programmable FPGA. > The controller has a version number of '5' (0x00000005). > The controller has an insertion length of '0' (0x00000000). > This utility will attempt to reset the controller. > This utility has successfully reset the controller. > Note: This is a key indicator > > -----[Print the reset-command hardware > log-file]----------------------------- > > The scan-path will be reset by toggling the JTAG TRST signal. > The controller is the XDS110 with USB interface. > The link from controller to target is direct (without cable). > The software is configured for XDS110 features. > The controller cannot monitor the value on the EMU[0] pin. > Note: We are not using some of these signals so this is OK. Bob > The controller cannot monitor the value on the EMU[1] pin. > The controller cannot control the timing on output pins. > The controller cannot control the timing on input pins. > The scan-path link-delay has been set to exactly '0' (0x0000). > > -----[Perform the Integrity scan-test on the JTAG > IR]------------------------ > > This test will use blocks of 64 32-bit words. > This test will be applied just once. > > Do a test using 0xFFFFFFFF. > Scan tests: 1, skipped: 0, failed: 0 > Do a test using 0x00000000. > Scan tests: 2, skipped: 0, failed: 0 > Do a test using 0xFE03E0E2. > Scan tests: 3, skipped: 0, failed: 0 > Do a test using 0x01FC1F1D. > Scan tests: 4, skipped: 0, failed: 0 > Do a test using 0x5533CCAA. > Scan tests: 5, skipped: 0, failed: 0 > Do a test using 0xAACC3355. > Scan tests: 6, skipped: 0, failed: 0 > All of the values were scanned correctly. > Note: Good news > > The JTAG IR Integrity scan-test has succeeded. > > -----[Perform the Integrity scan-test on the JTAG > DR]------------------------ > > This test will use blocks of 64 32-bit words. > This test will be applied just once. > > Do a test using 0xFFFFFFFF. > Scan tests: 1, skipped: 0, failed: 0 > Do a test using 0x00000000. > Scan tests: 2, skipped: 0, failed: 0 > Do a test using 0xFE03E0E2. > Scan tests: 3, skipped: 0, failed: 0 > Do a test using 0x01FC1F1D. > Scan tests: 4, skipped: 0, failed: 0 > Do a test using 0x5533CCAA. > Scan tests: 5, skipped: 0, failed: 0 > Do a test using 0xAACC3355. > Scan tests: 6, skipped: 0, failed: 0 > All of the values were scanned correctly. > Note: Good news > > The JTAG DR Integrity scan-test has succeeded. > > -----[An error has occurred and this utility has > aborted]-------------------- > > This error is generated by TI's USCIF driver or utilities. > > The value is '-382' (0xfffffe82). > The title is 'SC_ERR_LIST_SUBPATH_DELETE'. > > The explanation is: > An error occurred when deleting a sub-path from the sub-path select list. > The sub-path may already be off the list. > Thus it cannot be deleted from that list. > > [End: Texas Instruments XDS110 USB Debug Probe] > > [Start: Texas Instruments XDS110 USB Debug Probe_0] > > Execute the command: > > %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity > > [Result] > > > -----[Print the board config > pathname(s)]------------------------------------ > > /home/bob/.ti/ccs1250/0/0/BrdDat/testBoard.dat > > -----[Print the reset-command software > log-file]----------------------------- > > This utility has selected a 100/110/510 class product. > This utility will load the adapter 'libjioxds110.so'. > The library build date was 'Sep 6 2023'. > The library build time was '09:54:42'. > The library package version is '9.13.0.00201'. > The library component version is '35.35.0.0'. > The controller does not use a programmable FPGA. > The controller has a version number of '5' (0x00000005). > The controller has an insertion length of '0' (0x00000000). > This utility will attempt to reset the controller. > This utility has successfully reset the controller. > > -----[Print the reset-command hardware > log-file]----------------------------- > > The scan-path will be reset by toggling the JTAG TRST signal. > The controller is the XDS110 with USB interface. > The link from controller to target is direct (without cable). > The software is configured for XDS110 features. > The controller cannot monitor the value on the EMU[0] pin. > The controller cannot monitor the value on the EMU[1] pin. > The controller cannot control the timing on output pins. > The controller cannot control the timing on input pins. > The scan-path link-delay has been set to exactly '0' (0x0000). > > -----[Perform the Integrity scan-test on the JTAG > IR]------------------------ > > This test will use blocks of 64 32-bit words. > This test will be applied just once. > > Do a test using 0xFFFFFFFF. > Scan tests: 1, skipped: 0, failed: 0 > Do a test using 0x00000000. > Scan tests: 2, skipped: 0, failed: 0 > Do a test using 0xFE03E0E2. > Scan tests: 3, skipped: 0, failed: 0 > Do a test using 0x01FC1F1D. > Scan tests: 4, skipped: 0, failed: 0 > Do a test using 0x5533CCAA. > Scan tests: 5, skipped: 0, failed: 0 > Do a test using 0xAACC3355. > Scan tests: 6, skipped: 0, failed: 0 > All of the values were scanned correctly. > > The JTAG IR Integrity scan-test has succeeded. > > -----[Perform the Integrity scan-test on the JTAG > DR]------------------------ > > This test will use blocks of 64 32-bit words. > This test will be applied just once. > > Do a test using 0xFFFFFFFF. > Scan tests: 1, skipped: 0, failed: 0 > Do a test using 0x00000000. > Scan tests: 2, skipped: 0, failed: 0 > Do a test using 0xFE03E0E2. > Scan tests: 3, skipped: 0, failed: 0 > Do a test using 0x01FC1F1D. > Scan tests: 4, skipped: 0, failed: 0 > Do a test using 0x5533CCAA. > Scan tests: 5, skipped: 0, failed: 0 > Do a test using 0xAACC3355. > Scan tests: 6, skipped: 0, failed: 0 > All of the values were scanned correctly. > > The JTAG DR Integrity scan-test has succeeded. > > [End: Texas Instruments XDS110 USB Debug Probe_0] > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Progress
by Bob Stricklin 27 Dec '23

27 Dec '23

All, I have worked on the board a few hours over the past few days. I got the JTAG interface put together and set this up for testing with the PC and a XDS110. When I connected them together and powered things up I initially saw the LEDs on the PCB come on which is what I expect. Unfortunately when I started trying to communicate with using the JTAG I so the LEDs go off and immediatly I checked the 3.3V supply and found it was bouncing up to about 4 volts. Not good. So I powered down and after some thought I decided the 3.3 voltage regulator was not stable enough to support out board. It's working in a feed back mode trying to hold the 3.3V while adjusting Pulse Width Modulation of the LC circuit. I tested the board with an external 3.3V supply and noticed the current draw had increased to about 240 mA. Concerning. I have removed the MAX regulator and put a LDO fixed 3.3V regulator on hanging in the air. #.3V supply now seems solid. I got everything reconnected to JTAG and started again trying to test. When I tried Test Connection I was seeing a message about missing a file which I later realized was the HalCoGen file defining the board info. I then tried the one from the PAcSat project that I had but this was not working either. So I used the setup system to create a basic interface with a 4 wire JTAG. The I select Test Connection and this time it seems to be working. Still more work needed to learn what it is telling be but the two successes at the bottom of the listing below are encouraging. In this mode the supply current is down to 190 mA feeding into the 5V supply which feeds everything on the board. May be believable. Now time to create a proper HalCoGen file. Bob N5BRG [Start: Texas Instruments XDS110 USB Debug Probe] Execute the command: %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity [Result] -----[Print the board config pathname(s)]------------------------------------ /home/bob/.ti/ccs1250/0/0/BrdDat/testBoard.dat -----[Print the reset-command software log-file]----------------------------- This utility has selected a 100/110/510 class product. This utility will load the adapter 'libjioxds110.so'. The library build date was 'Sep 6 2023'. The library build time was '09:54:42'. The library package version is '9.13.0.00201'. The library component version is '35.35.0.0'. The controller does not use a programmable FPGA. The controller has a version number of '5' (0x00000005). The controller has an insertion length of '0' (0x00000000). This utility will attempt to reset the controller. This utility has successfully reset the controller. Note: This is a key indicator -----[Print the reset-command hardware log-file]----------------------------- The scan-path will be reset by toggling the JTAG TRST signal. The controller is the XDS110 with USB interface. The link from controller to target is direct (without cable). The software is configured for XDS110 features. The controller cannot monitor the value on the EMU[0] pin. Note: We are not using some of these signals so this is OK. Bob The controller cannot monitor the value on the EMU[1] pin. The controller cannot control the timing on output pins. The controller cannot control the timing on input pins. The scan-path link-delay has been set to exactly '0' (0x0000). -----[Perform the Integrity scan-test on the JTAG IR]------------------------ This test will use blocks of 64 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 0 All of the values were scanned correctly. Note: Good news The JTAG IR Integrity scan-test has succeeded. -----[Perform the Integrity scan-test on the JTAG DR]------------------------ This test will use blocks of 64 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 0 All of the values were scanned correctly. Note: Good news The JTAG DR Integrity scan-test has succeeded. -----[An error has occurred and this utility has aborted]-------------------- This error is generated by TI's USCIF driver or utilities. The value is '-382' (0xfffffe82). The title is 'SC_ERR_LIST_SUBPATH_DELETE'. The explanation is: An error occurred when deleting a sub-path from the sub-path select list. The sub-path may already be off the list. Thus it cannot be deleted from that list. [End: Texas Instruments XDS110 USB Debug Probe] [Start: Texas Instruments XDS110 USB Debug Probe_0] Execute the command: %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity [Result] -----[Print the board config pathname(s)]------------------------------------ /home/bob/.ti/ccs1250/0/0/BrdDat/testBoard.dat -----[Print the reset-command software log-file]----------------------------- This utility has selected a 100/110/510 class product. This utility will load the adapter 'libjioxds110.so'. The library build date was 'Sep 6 2023'. The library build time was '09:54:42'. The library package version is '9.13.0.00201'. The library component version is '35.35.0.0'. The controller does not use a programmable FPGA. The controller has a version number of '5' (0x00000005). The controller has an insertion length of '0' (0x00000000). This utility will attempt to reset the controller. This utility has successfully reset the controller. -----[Print the reset-command hardware log-file]----------------------------- The scan-path will be reset by toggling the JTAG TRST signal. The controller is the XDS110 with USB interface. The link from controller to target is direct (without cable). The software is configured for XDS110 features. The controller cannot monitor the value on the EMU[0] pin. The controller cannot monitor the value on the EMU[1] pin. The controller cannot control the timing on output pins. The controller cannot control the timing on input pins. The scan-path link-delay has been set to exactly '0' (0x0000). -----[Perform the Integrity scan-test on the JTAG IR]------------------------ This test will use blocks of 64 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 0 All of the values were scanned correctly. The JTAG IR Integrity scan-test has succeeded. -----[Perform the Integrity scan-test on the JTAG DR]------------------------ This test will use blocks of 64 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 0 All of the values were scanned correctly. The JTAG DR Integrity scan-test has succeeded. [End: Texas Instruments XDS110 USB Debug Probe_0]

1 0

Expense reimbursement
by Burns Fisher (AMSAT) 22 Dec '23

22 Dec '23

73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Pacsat dev mtg 12/21/2023
by Corey Minyard 22 Dec '23

22 Dec '23

This is the Thursday night I can't make. Talk to you next time. -corey On Thu, Dec 21, 2023, 14:20 Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat dev mtg 12/21/2023 > Thu, Dec 21, 2023 7:00 PM - 9:00 PM (CST) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/990259677 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (571) 317-3122 > - One-touch: tel:+15713173122,,990259677# > > Access Code: 990-259-677 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 990 259 677 > Or dial directly: 990259677(a)67.217.95.2 or 67.217.95.2##990259677 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Pacsat dev mtg 12/21/2023
by Bill 21 Dec '23

21 Dec '23

Pacsat dev mtg 12/21/2023 Thu, Dec 21, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/990259677 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3122 - One-touch: tel:+15713173122,,990259677# Access Code: 990-259-677 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 990 259 677 Or dial directly: 990259677(a)67.217.95.2 or 67.217.95.2##990259677 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: BringUp Status
by Jim McCullers 21 Dec '23

21 Dec '23

Good progress Bob The memory chips are a pain to hand solder. You should see about 9ma or so on the AX5043s when idle. Jim Update on BringUp…. I tested the power being provided to the AX5043 and did not see any change in current. I will need to investigate this more later. Decided to move on. I started to solder some of the memory chips back on the board and realized I had to use hot air because pads are bottom of package. To do this I need solder paste and I could not find some I once had. Thought I had in in a freezer but was not there. So I have order solder paste due tomorrow. I did solder a replacement CPU chip on the board. After doing this and cleaning I applied power and did not see any issues with power supply voltages. The board now pulls about 90 mA on 5.3V input to main 5V regulator. Started looking at trying to get the TI XDS110 Debug Prob to talk to the JTAG port. No luck communicating yet. Bob N5BRG ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

BringUp Status
by Bob Stricklin 21 Dec '23

21 Dec '23

Update on BringUp…. I tested the power being provided to the AX5043 and did not see any change in current. I will need to investigate this more later. Decided to move on. I started to solder some of the memory chips back on the board and realized I had to use hot air because pads are bottom of package. To do this I need solder paste and I could not find some I once had. Thought I had in in a freezer but was not there. So I have order solder paste due tomorrow. I did solder a replacement CPU chip on the board. After doing this and cleaning I applied power and did not see any issues with power supply voltages. The board now pulls about 90 mA on 5.3V input to main 5V regulator. Started looking at trying to get the TI XDS110 Debug Prob to talk to the JTAG port. No luck communicating yet. Bob N5BRG

1 0

Re: Bring-Up Status
by Chris Thompson 20 Dec '23

20 Dec '23

This sounds like great progress Bob, well done. Happy holidays Chris On Tue, Dec 19, 2023 at 10:24 PM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > *Here is an update on my progress checking out the QuadRxOneTx board.….* > > I got the power supply working properly with the chips Zack sent. Took > some time to repair the things I did to debug the issue and get the small > parts soldered on the board. > > When i powered up both supplies were working properly. I did add clamping > Zener diodes across the outputs to provide some modest protection. > > Then I had to reinsert the programming resistors on the current limiting > MAX4995 which I removed to isolate sections of the board. > > When I started testing one of the 3.3V supply sections was not powering up > and the supplies were dropping out in a constant pattern. Found the issue > was the Watch Dog was > not dibbled and this was turning things off and back on in time. Disabled > these. I also found I have the control logic which turns the power on and > off reversed. This is another case of > picking the correct logic on the watch dog chip by using the proper > suffix. The one I specified is AL which I assume is Active Low and I needed > active high. I disowned this and hard wire them > all to be on for now. Will need to work on this more later. The watchdog > chip can also be configured in different ways so all this needs to be > worked when CPU is working. > > With all the board functional (minus the TMS570) still had a short on one > 3.3v section. After some investigation I determine the short was in one or > more memory chip. The > data sheet for these indicated they are particularly sensitive. So I > removed all four of them. After removal and some component testing I found > only one of the four was > Actually shorted. However with these off the board the power supplies were > all functioning properly throughout the board. > > One troubling thing i noticed was with the short on the 3.3V supply if you > jumped by the current limiter which I did to find the issue and removed the > jumper that supply would jump up to about 3.8 volts and take a bunch of > seconds to settle back down to 3.3V. This is a issue with a DC to DC > regulator which is plus width modulated and adjusting to hold the output at > a fixed level. Typically we will not have a short but if a temporary short > were to happen in space the supply could over react and zap some other > parts. Could put the clamping zener on for space use if we can find a good > voltage to use but then these could become a failure point. > > None of the other chips on the board seem to have issues from over voltage > now that the supplies are up and working but will need to test individually > to be sure. The AX5043 have never been turned on yet. > > At this point with no CPU and no memory and the AX5043 all turned off the > board is pulling about 25Ma of current. I should also manually turn the > AX5043s on and check current tomorrow. > > Tomorrow I will solder the three memory chips I took off which are not > shorted back on power up to be sure things are still working. > > Next, I will solder a TMS570 I have on hand and check power and function. > If the board still functions I should be able to talk to the TMS570 via > JTAG and load a program into flash. > > While waiting for the chips from Zach I built up an interface cable to > connect the 10 pin JATAG to the 20 pin DSC100 connector with the correct > pins wired together. This took me about 3 > hours because the wires are so small and working out the details. Due to > this I laid out a PCB to support using two off-the-shelf ribbon cables from > Mouser. I will post the connection info to the GitHub. > I will also order enough ribbon cables to support the four board sets but > need to verify what is needed for each programmer people will be using. > > > > I have about 20 of these on order at JLCPCB which should be in my hands in > about a week +- holidays. > > The board is layer out so one can cut and rejumper if there is an error or > another connection is need for a different programmer. > > *Looking to the future…* > > The boot loader and all initial code will have to run from FLASH. I have > not looked at the current memory map to see if this is the case now. Jim if > your blinky program will run from flash you can send it along. > > Need to review the memory test program and hopefully it also runs from > flash. I will want to test the three of four memory chips to see if they > are working and not damaged from voltage or soldering and removing and > desoldering. I will need to purchase one more MR25H40CDE memory chip to > have a full set again. These chips are in the $28 dollar range from mouser > so I hope the three are working. I am assuming I will be able to solder > them back on the board. I believe I can but I want be reflowing the solder > on the pad initially. If they get hot in use I may try to do this later > with hot air system. > > This is all a typical bring-up process for a board this complex. It looks > like if we put replacement voltage regulators on the other boards and tune > the logic on the watch dog or replace the current control devices ($5 each) > which would be easy to do the other three boards should come up working. > > i have also ordered 12 more of the voltage regulators from China which I > hope will be working and equivalent. Should have those in a week also. > > Lots more to test and checkout but if the TMS570 will work it should go > faster. > > Bob N5BRG > > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Bring-Up Status
by Bob Stricklin 20 Dec '23

20 Dec '23

Here is an update on my progress checking out the QuadRxOneTx board.…. I got the power supply working properly with the chips Zack sent. Took some time to repair the things I did to debug the issue and get the small parts soldered on the board. When i powered up both supplies were working properly. I did add clamping Zener diodes across the outputs to provide some modest protection. Then I had to reinsert the programming resistors on the current limiting MAX4995 which I removed to isolate sections of the board. When I started testing one of the 3.3V supply sections was not powering up and the supplies were dropping out in a constant pattern. Found the issue was the Watch Dog was not dibbled and this was turning things off and back on in time. Disabled these. I also found I have the control logic which turns the power on and off reversed. This is another case of picking the correct logic on the watch dog chip by using the proper suffix. The one I specified is AL which I assume is Active Low and I needed active high. I disowned this and hard wire them all to be on for now. Will need to work on this more later. The watchdog chip can also be configured in different ways so all this needs to be worked when CPU is working. With all the board functional (minus the TMS570) still had a short on one 3.3v section. After some investigation I determine the short was in one or more memory chip. The data sheet for these indicated they are particularly sensitive. So I removed all four of them. After removal and some component testing I found only one of the four was Actually shorted. However with these off the board the power supplies were all functioning properly throughout the board. One troubling thing i noticed was with the short on the 3.3V supply if you jumped by the current limiter which I did to find the issue and removed the jumper that supply would jump up to about 3.8 volts and take a bunch of seconds to settle back down to 3.3V. This is a issue with a DC to DC regulator which is plus width modulated and adjusting to hold the output at a fixed level. Typically we will not have a short but if a temporary short were to happen in space the supply could over react and zap some other parts. Could put the clamping zener on for space use if we can find a good voltage to use but then these could become a failure point. None of the other chips on the board seem to have issues from over voltage now that the supplies are up and working but will need to test individually to be sure. The AX5043 have never been turned on yet. At this point with no CPU and no memory and the AX5043 all turned off the board is pulling about 25Ma of current. I should also manually turn the AX5043s on and check current tomorrow. Tomorrow I will solder the three memory chips I took off which are not shorted back on power up to be sure things are still working. Next, I will solder a TMS570 I have on hand and check power and function. If the board still functions I should be able to talk to the TMS570 via JTAG and load a program into flash. While waiting for the chips from Zach I built up an interface cable to connect the 10 pin JATAG to the 20 pin DSC100 connector with the correct pins wired together. This took me about 3 hours because the wires are so small and working out the details. Due to this I laid out a PCB to support using two off-the-shelf ribbon cables from Mouser. I will post the connection info to the GitHub. I will also order enough ribbon cables to support the four board sets but need to verify what is needed for each programmer people will be using. [cid:DDEC065C-32A7-48E1-BD2F-DB766FEA4C7A@StricklinRanch.com] I have about 20 of these on order at JLCPCB which should be in my hands in about a week +- holidays. The board is layer out so one can cut and rejumper if there is an error or another connection is need for a different programmer. Looking to the future… The boot loader and all initial code will have to run from FLASH. I have not looked at the current memory map to see if this is the case now. Jim if your blinky program will run from flash you can send it along. Need to review the memory test program and hopefully it also runs from flash. I will want to test the three of four memory chips to see if they are working and not damaged from voltage or soldering and removing and desoldering. I will need to purchase one more MR25H40CDE memory chip to have a full set again. These chips are in the $28 dollar range from mouser so I hope the three are working. I am assuming I will be able to solder them back on the board. I believe I can but I want be reflowing the solder on the pad initially. If they get hot in use I may try to do this later with hot air system. This is all a typical bring-up process for a board this complex. It looks like if we put replacement voltage regulators on the other boards and tune the logic on the watch dog or replace the current control devices ($5 each) which would be easy to do the other three boards should come up working. i have also ordered 12 more of the voltage regulators from China which I hope will be working and equivalent. Should have those in a week also. Lots more to test and checkout but if the TMS570 will work it should go faster. Bob N5BRG

1 0

tms570
by Bill Reed 19 Dec '23

19 Dec '23

Just picked up 25 TMS570 chips... Bill

1 0

Re: Pacsat dev mtg
by Chris Thompson 13 Dec '23

13 Dec '23

I won't be able to make this Thursday's meeting as I will be at a concert. 73 Chris On Wed, Dec 13, 2023 at 5:36 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > My Thursday with another meeting. FWIW, I just ordered 10 TMS570 debug > boards and the Samtec connectors (FTSH-105-01-L-D-K) that the RTIHU uses. > I've still not quite figured out what is on Bob's board, but I'm not > planning to replace more than one of the connectors. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Wed, Dec 13, 2023 at 5:33 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> > wrote: > >> Pacsat dev mtg >> Thu, Dec 14, 2023 7:00 PM - 9:00 PM (CST) >> >> Please join my meeting from your computer, tablet or smartphone. >> >> https://meet.goto.com/856856893 >> >> You can also dial in using your phone. >> (For supported devices, tap a one-touch number below to join instantly.) >> >> United States: +1 (872) 240-3212 >> - One-touch: tel:+18722403212,,856856893# >> >> Access Code: 856-856-893 >> >> Join from a video-conferencing room or system. >> Dial in or type: 67.217.95.2 or inroomlink.goto.com >> Meeting ID: 856 856 893 >> Or dial directly: 856856893(a)67.217.95.2 or 67.217.95.2##856856893 >> >> >> Get the app now and be ready when your first meeting starts: >> https://meet.goto.com/install >> >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Pacsat dev mtg
by Burns Fisher (AMSAT) 13 Dec '23

13 Dec '23

My Thursday with another meeting. FWIW, I just ordered 10 TMS570 debug boards and the Samtec connectors (FTSH-105-01-L-D-K) that the RTIHU uses. I've still not quite figured out what is on Bob's board, but I'm not planning to replace more than one of the connectors. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Dec 13, 2023 at 5:33 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat dev mtg > Thu, Dec 14, 2023 7:00 PM - 9:00 PM (CST) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/856856893 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (872) 240-3212 > - One-touch: tel:+18722403212,,856856893# > > Access Code: 856-856-893 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 856 856 893 > Or dial directly: 856856893(a)67.217.95.2 or 67.217.95.2##856856893 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Pacsat dev mtg
by Bill 13 Dec '23

13 Dec '23

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

1 0

Re: TMS570 Debug board
by Burns Fisher (AMSAT) 12 Dec '23

12 Dec '23

Well, I got a shipping notice and a tracking number. The tracking number does not yet register with UPS though. I continue to say "we'll see". 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, Dec 8, 2023 at 11:58 AM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > The last thing I ordered from Newark was also shipped from the UK with no > shipping communications and as I recall took a long time. > > It was also an obsolete component by DigiKey and Mouser. > > > > Keep us posted. > > > > Jim > > > > Ok, Bob. The picture sure looks like there are "holes" there, but you > never know. I do think that I asked Zach to put the connector on the > bottom so it would line the ribbon cable up correctly with the RTIHU > connector. We'll find out. BTW, Newark says they are sending the board > from the UK. Hmm. > > 73, > > > > Burns Fisher, WB1FJ > > *AMSAT**(R) **Engineering -- Flight Software* > > > > > > On Fri, Dec 8, 2023 at 11:00 AM Bob Stricklin via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > Burns, > > > > I believe he is talking about a 10 pin connector on the bottom left corner > of the photo that is turned down below the board. > > He probably did this to make a standard ribbon cable work with female IDC > connectors on each end. > > > > We can make that change if the boards are shipped. > > > > It may be that Newark inventory is there because they do not got so much > business on TI product. Normally when an OEM drops a product they pull all > the distributor inventory back. These may be a third party board which is > fine if they have the same processor and code. > > > > It will be interesting to see if the TI ARM processor TM4C1294NCPDTT3R is > on these boards. If it is and several people working on AMSAT projects need > these boards we probably should buy more. > > > > The info I have is the design information I showed last night that Zach > shared with me on an AMSAT version of this programming interface board. > > > > Bob > > > > > > > > On Dec 8, 2023, at 9:41 AM, Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > > > Thanks, Zach. That might mean that what I ordered is different. See in > the picture, the place where you added the connector is not populated. > (You have to hover over it to get the expanded version in order to see it). > > > > > https://www.newark.com/texas-instruments/cc-devpack-debug/debugger-devpak-s… > > > > Well see what happens. Actually do you have a couple of male connectors > that you could send me? That way, I could easily add it in and test the > new board (assuming it comes...maybe you'd better wait until I get a > shipping number :-) ) > > > 73, > > > > Burns Fisher, WB1FJ > > *AMSAT**(R) **Engineering -- Flight Software* > > > > > > On Fri, Dec 8, 2023 at 10:32 AM Zach Metzinger <zmetzing(a)pobox.com> wrote: > > On 12/8/23 08:07, Burns Fisher (AMSAT) wrote: > > Note to Pacsat folks: It appears (and Zach can confirm) that Zach must > > have just ADDED a connector into a DNP space on the board...this is > > based on the pictures. > > Hello Burns and the Pacsat team, > > This is not correct; I replace the female 2x5 connector with a male 2x5 > shrouded/keyed connector. Instructions, already sent to Bob Strickland, > attached. > > 73, > > --- Zach > N0ZGO > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 2

Re: Power Regulator issue
by Burns Fisher (AMSAT) 11 Dec '23

11 Dec '23

I must have sent this only to Bob. AFAIK this chip only appears in the RT-IHU V1.1. Eric did not build the RT-IHU so probably not. Zach might. However, he apparently knew it was obsolete so V1.2 has a different but incompatible chip. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, Dec 11, 2023 at 1:27 PM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Bummer > > In most cases a suffix indicates a minor difference. > > Getting more difficult to deal with older components and variations. > Try getting a 2N3177, used in almost every linear power supply since the > 70s. > No longer manufactured and stocks are limited with the expected increase in > price. > I have several Astron power supplies donated to our local club that need > refreshing. > At the moment the best source appears to be Astron, who apparently bought a > large stock. > > Burns, would Eric or Zach have the MAX1556A inventory? > > Jim > WA4CWI > > > After looking into this more I see the MAX1556A was specified in the > schematic and BOM. The MAX1556 was placed on the board. These two parts > work > differently WRT to the programming pins D1, D2. > If the MAX1556A had been used we would have been fine. > > I see no stock not his part at Mouser or Digikey or Newark, or anyone in > the > US so far. I do see inventory in ASIA. If they will sell a small quantity > of > say 16 we should be able to swap out the parts. Shipping cost will be $40 > to > $60. > > This part is now Obsolete at Analog Devices. > > I think these part was used on earlier AMSAT boards. I would like to know > if > there is any inventory available before ordering the parts from Asia? We > need a minimum of 8 but I would like to have 16 to be sure we get them > soldered on the boards. > > Bob > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org Manage all of > your AMSAT-NA mailing list preferences at https://mailman.amsat.org > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Power Regulator issue
by Jim McCullers 11 Dec '23

11 Dec '23

Bummer In most cases a suffix indicates a minor difference. Getting more difficult to deal with older components and variations. Try getting a 2N3177, used in almost every linear power supply since the 70s. No longer manufactured and stocks are limited with the expected increase in price. I have several Astron power supplies donated to our local club that need refreshing. At the moment the best source appears to be Astron, who apparently bought a large stock. Burns, would Eric or Zach have the MAX1556A inventory? Jim WA4CWI After looking into this more I see the MAX1556A was specified in the schematic and BOM. The MAX1556 was placed on the board. These two parts work differently WRT to the programming pins D1, D2. If the MAX1556A had been used we would have been fine. I see no stock not his part at Mouser or Digikey or Newark, or anyone in the US so far. I do see inventory in ASIA. If they will sell a small quantity of say 16 we should be able to swap out the parts. Shipping cost will be $40 to $60. This part is now Obsolete at Analog Devices. I think these part was used on earlier AMSAT boards. I would like to know if there is any inventory available before ordering the parts from Asia? We need a minimum of 8 but I would like to have 16 to be sure we get them soldered on the boards. Bob ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

UPS notification of Newark deliver
by Burns Fisher (AMSAT) 11 Dec '23

11 Dec '23

UPS tells me that the package from Newark will arrive tomorrow. Zach, perhaps it is now safe to send me two of those connectors for the debug board. Thanks! 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Power Regulator issue
by Burns Fisher (AMSAT) 10 Dec '23

10 Dec '23

Yep, they are on the RTIHU. Zach would be the one who might have spare parts. BTW, did you check Arrow Electronics? Analog Devices says they have an agreement with Arrow to stock obsolete parts. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Sun, Dec 10, 2023 at 4:32 PM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > After looking into this more I see the MAX1556A was specified in the > schematic and BOM. The MAX1556 was placed on the board. These two parts > work differently WRT to the programming pins D1, D2. > If the MAX1556A had been used we would have been fine. > > I see no stock not his part at Mouser or Digikey or Newark, or anyone in > the US so far. I do see inventory in ASIA. If they will sell a small > quantity of say 16 we should be able to swap out the parts. Shipping cost > will be $40 to $60. > > This part is now Obsolete at Analog Devices. > > I think these part was used on earlier AMSAT boards. I would like to know > if there is any inventory available before ordering the parts from Asia? > We need a minimum of 8 but I would like to have 16 to be sure we get them > soldered on the boards. > > Bob > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 1

Power Regulator issue
by Bob Stricklin 10 Dec '23

10 Dec '23

After looking into this more I see the MAX1556A was specified in the schematic and BOM. The MAX1556 was placed on the board. These two parts work differently WRT to the programming pins D1, D2. If the MAX1556A had been used we would have been fine. I see no stock not his part at Mouser or Digikey or Newark, or anyone in the US so far. I do see inventory in ASIA. If they will sell a small quantity of say 16 we should be able to swap out the parts. Shipping cost will be $40 to $60. This part is now Obsolete at Analog Devices. I think these part was used on earlier AMSAT boards. I would like to know if there is any inventory available before ordering the parts from Asia? We need a minimum of 8 but I would like to have 16 to be sure we get them soldered on the boards. Bob

1 0

Re: Comments on Broad bringup
by Jim McCullers 09 Dec '23

09 Dec '23

Does it appear the board survived the slight over voltage or is it too early to tell? I don't believe I have a 6.8k or 24k in those sizes. Jim WA4CWI While reviewing things today I realized i had the Watchdog timer enabled for protection until things are working. However we have a watchdog that turns on at power up and stayed active for about 1.2 seconds. After 1.2 seconds it turns the general power to the board off. I am doing my testing by slowly increasing the power supply current which means the voltage comes up slowly. The 1.8 volt supply has never been turned on so far. When Power and clocks are stable we will disable the watchdog until code is running in CPU at power up. Something to think about later, A watchdog normally resets a processor. In this case i have one watchdog turning off the distributed power to the board. We may need a power cycle to restart the watchdog process. If we are a host on a larger platform we do have a method to cycle power. If we do not want to rely on intervention we may need to change things in this design. I needed a 6.8K resistor and a 24K resistor to recondition the 3.3 volt regulator. I purchased 100 6.8K resistors a year ago but can’t find them. Kent WA5VJB will bring me the resistors to the NTMS meeting tomorrow so I can keep moving forward. Bob ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Comments on Broad bringup
by Bob Stricklin 08 Dec '23

08 Dec '23

While reviewing things today I realized i had the Watchdog timer enabled for protection until things are working. However we have a watchdog that turns on at power up and stayed active for about 1.2 seconds. After 1.2 seconds it turns the general power to the board off. I am doing my testing by slowly increasing the power supply current which means the voltage comes up slowly. The 1.8 volt supply has never been turned on so far. When Power and clocks are stable we will disable the watchdog until code is running in CPU at power up. Something to think about later, A watchdog normally resets a processor. In this case i have one watchdog turning off the distributed power to the board. We may need a power cycle to restart the watchdog process. If we are a host on a larger platform we do have a method to cycle power. If we do not want to rely on intervention we may need to change things in this design. I needed a 6.8K resistor and a 24K resistor to recondition the 3.3 volt regulator. I purchased 100 6.8K resistors a year ago but can’t find them. Kent WA5VJB will bring me the resistors to the NTMS meeting tomorrow so I can keep moving forward. Bob

1 0

JTAG Connection
by Bob Stricklin 08 Dec '23

08 Dec '23

1 0

Connector for JTAG on the 4RX1TX PCB
by Bob Stricklin 08 Dec '23

08 Dec '23

The connector placed on the PCB is Samtec FTSH-105-01-L-DV-K Its a .050” pitch 2X5 connector. This part number is on the schematic CPU page top left. I purchased a ribbon cable from Mouser and raced it today. This cable will work with the PCB connector. Mouser # 200-FFSD05D08.0001N The connector on the TI programming board and likely the lower cost programming board have a different arrangement. My solution is to purchase ribbon cables for both types and cut and splice them together properly. Bob

1 0