January 2024 - pacsat-dev - mailman.amsat.org

Code Composer Search
by Jim McCullers 12 Jan '24

12 Jan '24

Bob is correct. The search symbol looks more like a rocket than flashlight. Chris told me there was a symbol on the tool bar and through experimentation and Google I realized it was a flashlight, not the common search symbol. Attached is an image how I do project searches. Like the flashlight it wasn't intuitive. Jim McCullers WA4CWI

1 0

Re: Pacsat dev mtg 1/11/2024
by Burns Fisher (AMSAT) 11 Jan '24

11 Jan '24

As usual, this is my other-meeting Thursday. See you next week. Bob, BTW, I got the debug board today. Looks good! Thank you. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Jan 11, 2024 at 1:09 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat dev mtg 1/11/2024 > Thu, Jan 11, 2024 7:00 PM - 9:00 PM (CST) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/272073445 > > 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-3112 > - One-touch: tel:+15713173112,,272073445# > > Access Code: 272-073-445 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 272 073 445 > Or dial directly: 272073445(a)67.217.95.2 or 67.217.95.2##272073445 > > > 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/[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

Pacsat dev mtg 1/11/2024
by Bill 11 Jan '24

11 Jan '24

Pacsat dev mtg 1/11/2024 Thu, Jan 11, 2024 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/272073445 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-3112 - One-touch: tel:+15713173112,,272073445# Access Code: 272-073-445 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 272 073 445 Or dial directly: 272073445(a)67.217.95.2 or 67.217.95.2##272073445 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Jonathan's request for TMS570 programming boards
by Burns Fisher (AMSAT) 10 Jan '24

10 Jan '24

Many moons ago, Jonathan had someone (Chris Grill) designing programming boards for the TMS570 since the one we use was obsolete. That never went anywhere. I recently saw a bunch for sale and bought them up and now have 10-ish additional boards. In addition, Carl Wick designed a nice little 3D printed case for them. Right now, Zach, Rich, Bob Strickland, and I have at least one board and Rich and I have a couple prototype cases. My question is: Is someone other than Golf-TEE folks and Pacsat really planning to use the TMS570 and could benefit from the programming boards? If not immediately, I can hold onto them, but I don't want anyone to waste time trying to build or buy them again now that we have plenty. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* PS: To be clear, there are at least three ways to load a program into a TMS570: One is via a LaunchPad evaluation board, which has something similar to the programming board built in. Another is a TI XDS110 programming device (a $200 piece of hardware that may or may not be available). And third using this board that I am talking about, a $20 board called a SensorTag board. (And Heimir has also written a boot loader to load via a serial port, but it must be loaded using one of the above methods in order to be used).

1 0

Re: Blinky Working
by Jim McCullers 10 Jan '24

10 Jan '24

Thanks Jim WA4CWI Jim, I appreciate you trying to make it work. Zipped code attached. Seems like a small zip file so may not be all there. On the other hand it is mostly text files. Bob On Jan 9, 2024, at 4:07 PM, Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org <mailto:[email protected]> > wrote: Blinky was a crap shoot at best to try the HCG and FreeRTOS. I’ll look at your HCG and see if I find a difference. I see the HCG below but not the source code. Send it along. At least it gave you something to test load. If the problem is not resolved when I receive a working board I’ll debug the code as the exercise it was intended to be. Congrats and 73, Jim McCullers WA4CWI ----------------------------------------------------------- pacsat-dev mailing list -- <mailto:[email protected]> pacsat-dev(a)amsat.org View archives of this mailing list at <https://mailman.amsat.org/hyperkitty/list/[email protected]> https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to <mailto:[email protected]> pacsat-dev-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at <https://mailman.amsat.org/> https://mailman.amsat.org

1 0

Re: Blinky Working
by Bob Stricklin 10 Jan '24

10 Jan '24

Jim, I appreciate you trying to make it work. Zipped code attached. Seems like a small zip file so may not be all there. On the other hand it is mostly text files. Bob On Jan 9, 2024, at 4:07 PM, Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org<mailto:[email protected]>> wrote: Blinky was a crap shoot at best to try the HCG and FreeRTOS. I’ll look at your HCG and see if I find a difference. I see the HCG below but not the source code. Send it along. At least it gave you something to test load. If the problem is not resolved when I receive a working board I’ll debug the code as the exercise it was intended to be. Congrats and 73, Jim McCullers WA4CWI ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:[email protected]> 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<mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://mailman.amsat.org/>

1 0

Re: Blinky Working
by Jim McCullers 09 Jan '24

09 Jan '24

Blinky was a crap shoot at best to try the HCG and FreeRTOS. I’ll look at your HCG and see if I find a difference. I see the HCG below but not the source code. Send it along. At least it gave you something to test load. If the problem is not resolved when I receive a working board I’ll debug the code as the exercise it was intended to be. Congrats and 73, Jim McCullers WA4CWI

1 0

Blinking Less Mov
by Bob Stricklin 09 Jan '24

09 Jan '24

Here is short movie of the LEDs. It gives us an idea how fast the processor can run through 1.6 million instructions in C code. Bob

1 0

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

09 Jan '24

Used a hot air with board held in vice. Lightly tug on the connector from bottom side while heating the pin solder side with 400 C hot air. Then put flux on the for pins and used solder wick and a soldering iron to remove solder and most pin holes opened up. On holes that do not open I use a dental explore tool to stick it hole when solder is melted. Remove iron and then take dental tool out. Then solder in new connector. I can do more for you if you want me to. I forgot to clean the flux off the board I am sending back. You can use isopropyl alcohol to do this. I usually use Everclear or Ethel alcohol which leaves no white residue. Bob > On Jan 9, 2024, at 12:06 PM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > --===============0108675984297293611== > Content-Type: multipart/alternative; boundary="00000000000059bbda060e872bbb" > > --00000000000059bbda060e872bbb > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Thanks Bob. I now have the parts, but have had nothing but trouble both > removing and replacing those dumb little connectors! Any hints? Are you > using hot air or a small iron? > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Tue, Jan 9, 2024 at 1:04=E2=80=AFPM Bob Stricklin via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I received the two Devpack programming boards from Burns. Replaced >> connectors on both boards and I have tested them on the Quad board and th= > ey >> 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(a)amsat.org> wrote: >> >> I included a little extra. The connectors that I had ordered just arrive= > d >> (hot off the plane from Singapore) and I realized that Newark Electroncis >> had apparently switched the part number around on me, and they were surfa= > ce >> mount! Not useful for me in this case, but if they are useful for anythi= > ng >> you build, I sent you a few. >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Fri, Jan 5, 2024 at 11:28=E2=80=AFAM Bob Stricklin via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Thank you sir. >>> >>> Bob >>> >>> On Jan 5, 2024, at 10:09=E2=80=AFAM, Burns Fisher (AMSAT) via pacsat-dev= > < >>> pacsat-dev(a)amsat.org> wrote: >>> >>> =EF=BB=BF >>> 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 b= > e >>> 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=E2=80=AFAM Burns Fisher (AMSAT) <wb1fj@fish= > er.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 fema= > le >>>> with no key. The new one is male with shroud and key. The key is on t= > he >>>> 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 t= > he >>>> firmware from 2.2.5.1 to 3.0.0.15 (and there was an update button). Thi= > s >>>> works ok, and now since I am not connected to the RTIHU, it is correctl= > y >>>> claiming that it can't connect to the target. >>>> >>>> I'll update the serial and firmware on the second one I send you as wel= > l. >>>> >>>> >>>> 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 >>> >>> >>> ----------------------------------------------------------- >>> >>> 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 >>> >> >> ----------------------------------------------------------- >> >> 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 >> >> >> >> ----------------------------------------------------------- >> >> 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 >> > > --00000000000059bbda060e872bbb > Content-Type: text/html; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"><d= > iv dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,sans= > -serif">Thanks Bob.  I now have the parts, but have had nothing but tr= > ouble both removing and replacing those dumb little connectors!  Any h= > ints?  Are you using hot air or a small iron?</div><div class=3D"gmail= > _default" style=3D"font-family:arial,sans-serif"><br clear=3D"all"></div><d= > iv><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signa= > ture"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><di= > v dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><font face=3D"ari= > al, sans-serif">73,</font><div><font face=3D"arial, sans-serif"><br></font>= > </div><div><font face=3D"arial, sans-serif">Burns Fisher, WB1FJ</font></div= >> <div><i><span style=3D"font-family:arial,helvetica,sans-serif">AMSAT</span= >> <font face=3D"garamond, serif">(R) </font><font face=3D"arial, sans-serif"= >> Engineering -- Flight Software</font></i></div></div></div></div></div></d= > iv></div></div></div></div></div></div></div></div><br></div><br><div class= > =3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 9, 2024 = > at 1:04=E2=80=AFPM Bob Stricklin via pacsat-dev <<a href=3D"mailto:pacsa= > t-dev(a)amsat.org">pacsat-dev(a)amsat.org</a>> wrote:<br></div><blockquote c= > lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli= > d rgb(204,204,204);padding-left:1ex"> > > > > <div style=3D"overflow-wrap: break-word;"> > I received the two Devpack programming boards from Burns. Replaced connecto= > rs on both boards and I have tested them on the Quad board and they both wo= > rked fine. > <div><br> > </div> > <div>Returning one of these to Burns today.</div> > <div><br> > </div> > <div>Bob</div> > <div><br> > <div><br> > <blockquote type=3D"cite"> > <div>On Jan 5, 2024, at 11:21 AM, Burns Fisher (AMSAT) via pacsat-dev <<= > a href=3D"mailto:[email protected]" target=3D"_blank">pacsat-dev(a)amsat.o= > rg</a>> wrote:</div> > <br> > <div> > <div dir=3D"ltr"> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif">I inclu= > ded a little extra.  The connectors that I had ordered just arrived (h= > ot 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.<br clear= > =3D"all"> > </div> > <div> > <div dir=3D"ltr" class=3D"gmail_signature"> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"><font face=3D"arial, sans-serif">73,</font> > <div><font face=3D"arial, sans-serif"><br> > </font></div> > <div><font face=3D"arial, sans-serif">Burns Fisher, WB1FJ</font></div> > <div><i><span style=3D"font-family:arial,helvetica,sans-serif">AMSAT</span>= > <font face=3D"garamond, serif">(R) > </font><font face=3D"arial, sans-serif">Engineering -- Flight Software</fon= > t></i></div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > <br> > </div> > <br> > <div class=3D"gmail_quote"> > <div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 5, 2024 at 11:28=E2=80=AF= > AM Bob Stricklin via pacsat-dev <<a href=3D"mailto:[email protected]"= > target=3D"_blank">pacsat-dev(a)amsat.org</a>> wrote:<br> > </div> > <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-= > left:1px solid rgb(204,204,204);padding-left:1ex"> > <div dir=3D"auto"> > <div dir=3D"ltr"></div> > <div dir=3D"ltr">Thank you sir. </div> > <div dir=3D"ltr"><br> > </div> > <div dir=3D"ltr">Bob</div> > <div dir=3D"ltr"><br> > <blockquote type=3D"cite">On Jan 5, 2024, at 10:09=E2=80=AFAM, Burns Fisher= > (AMSAT) via pacsat-dev <<a href=3D"mailto:[email protected]" target= > =3D"_blank">pacsat-dev(a)amsat.org</a>> wrote:<br> > <br> > </blockquote> > </div> > <blockquote type=3D"cite"> > <div dir=3D"ltr">=EF=BB=BF > <div dir=3D"ltr"> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif">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 :-)</div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif"><br> > </div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif">I don't= > care which one you return to be with the connector replace, btw.  > <br> > </div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif"><br> > </div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif">Good lu= > ck!<br> > </div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif"><br cle= > ar=3D"all"> > </div> > <div> > <div dir=3D"ltr" class=3D"gmail_signature"> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"><font face=3D"arial, sans-serif">73,</font> > <div><font face=3D"arial, sans-serif"><br> > </font></div> > <div><font face=3D"arial, sans-serif">Burns Fisher, WB1FJ</font></div> > <div><i><span style=3D"font-family:arial,helvetica,sans-serif">AMSAT</span>= > <font face=3D"garamond, serif">(R) > </font><font face=3D"arial, sans-serif">Engineering -- Flight Software</fon= > t></i></div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > <br> > </div> > <br> > <div class=3D"gmail_quote"> > <div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 5, 2024 at 10:59=E2=80=AF= > AM Burns Fisher (AMSAT) <<a href=3D"mailto:[email protected]" target=3D"_b= > lank">wb1fj(a)fisher.cc</a>> wrote:<br> > </div> > <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-= > left:1px solid rgb(204,204,204);padding-left:1ex"> > <div dir=3D"ltr"> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif">Bob, et= > al:</div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif"><br> > </div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif">FWIW, t= > he official name of the little boards I'm send is TI Simplelink SensorTag D= > evpack.</div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif"><br> > </div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif">I'm inc= > luding 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 bo= > ard from the existing 10-pin connector.  > The existing one is female with no key.  The new one is male with shr= > oud and key.  The key is on the outside edge of the board, and the con= > nector is on the opposite side of the board from the chip (on the same side= > as the larger connector.</div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif"><br> > </div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif">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 tal= > ks about and discovered this:</div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif"><br> > </div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif"><span s= > tyle=3D"font-family:monospace">./ti/ccs1020/ccs/ccs_base/common/uscif/xds11= > 0/xdsdfu -e<br> > <br> > USB Device Firmware Upgrade Utility<br> > Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights re= > served.<br> > <br> > Scanning USB buses for supported XDS110 devices...<br> > <<<< Device 0 >>>><br> > VID: 0x0451    PID: 0xbef3<br> > Device Name:   XDS110 with CMSIS-DAP<br> > Version:       2.2.5.1<br> > Manufacturer:  Texas Instruments<br> > Serial Num:    L787<br> > Mode:          Runtime<br> > Configuration: Standard<br> > Found 1 device.</span><br> > </div> > <div class=3D"gmail_default" style=3D"font-family:arial,sans-serif"><br cle= > ar=3D"all"> > </div> > <div> > <div dir=3D"ltr" class=3D"gmail_signature"> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"> > <div> > <div dir=3D"ltr"><font face=3D"arial, sans-serif"><span class=3D"gmail_defa= > ult" style=3D"font-family:arial,sans-serif">Notice the serial number L787.&= > nbsp; One of my working ones has the serial number > </span></font>L3122222<span class=3D"gmail_default" style=3D"font-family:ar= > ial,sans-serif">.  So letter L and 7 digits.  I am setting yours = > to L31444444 and L31555555.  Like this:</span></div> > <div dir=3D"ltr"><br> > </div> > <div dir=3D"ltr"><br> > </div> > <div dir=3D"ltr"><span style=3D"font-family:monospace">bfisher@skylab:~$ ./= > ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -m<br> > USB Device Firmware Upgrade Utility<br> > Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights re= > served.<br> > Scanning USB buses for supported XDS110 devices...<br> > <<<< Device 0 >>>><br> > VID: 0x0451    PID: 0xbef3<br> > Device Name:   XDS110 with CMSIS-DAP<br> > Version:       2.2.5.1<br> > Manufacturer:  Texas Instruments<br> > Serial Num:    L787<br> > Mode:          Runtime<br> > Configuration: Standard<br> > Switching device into DFU mode.</span></div> > <div dir=3D"ltr"><span style=3D"font-family:monospace"><br> > </span></div> > <div dir=3D"ltr"><span style=3D"font-family:monospace">bfisher@skylab:~$ ./= > ti/ccs1020/ccs/ccs_base/common/uscif/xds110/xdsdfu -s L3144444 -r<br> > USB Device Firmware Upgrade Utility<br> > Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights re= > served.<br> > Scanning USB buses for supported XDS110 devices...<br> > Setting serial number to "L3144444"...</span><br> > </div> > <div dir=3D"ltr"><span class=3D"gmail_default" style=3D"font-family:arial,s= > ans-serif"><br> > </span></div> > <div style=3D"font-family:arial,sans-serif" class=3D"gmail_default">And now= > the box asks me to select whether I want to use TIXDS110_Connection-S/N:L3= > 1444444.  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 correc= > tly claiming that it can't connect to the target.<br> > </div> > <div style=3D"font-family:arial,sans-serif" class=3D"gmail_default"><br> > </div> > <div style=3D"font-family:arial,sans-serif" class=3D"gmail_default">I'll up= > date the serial and firmware on the second one I send you as well.<br> > </div> > <br> > <div dir=3D"ltr"><font face=3D"arial, sans-serif"><br> > </font></div> > <div dir=3D"ltr"><font face=3D"arial, sans-serif">73,</font> > <div><font face=3D"arial, sans-serif"><br> > </font></div> > <div><font face=3D"arial, sans-serif">Burns Fisher, WB1FJ</font></div> > <div><i><span style=3D"font-family:arial,helvetica,sans-serif">AMSAT</span>= > <font face=3D"garamond, serif">(R) > </font><font face=3D"arial, sans-serif">Engineering -- Flight Software</fon= > t></i></div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </div> > </blockquote> > </div> > <span></span><br> > <span>-----------------------------------------------------------</span><br= >> > <span></span><br> > <span>pacsat-dev mailing list -- <a href=3D"mailto:[email protected]" ta= > rget=3D"_blank"> > pacsat-dev(a)amsat.org</a></span><br> > <span>View archives of this mailing list at <a href=3D"https://mailman.amsa= > t.org/hyperkitty/list/pacsat-dev(a)amsat.org" target=3D"_blank"> > https://mailman.amsat.org/hyperkitty/list/[email protected]</a></span><b= > r> > <span>To unsubscribe send an email to <a href=3D"mailto:pacsat-dev-leave@am= > sat.org" target=3D"_blank"> > pacsat-dev-leave(a)amsat.org</a></span><br> > <span>Manage all of your AMSAT-NA mailing list preferences at <a href=3D"ht= > tps://mailman.amsat.org/" target=3D"_blank"> > https://mailman.amsat.org</a></span><br> > </div> > </blockquote> > </div> > <br> > -----------------------------------------------------------<br> > <br> > pacsat-dev mailing list -- <a href=3D"mailto:[email protected]" target= > =3D"_blank"> > pacsat-dev(a)amsat.org</a><br> > View archives of this mailing list at <a href=3D"https://mailman.amsat.org/= > hyperkitty/list/pacsat-dev(a)amsat.org" rel=3D"noreferrer" target=3D"_blank"> > https://mailman.amsat.org/hyperkitty/list/[email protected]</a><br> > To unsubscribe send an email to <a href=3D"mailto:[email protected]= > g" target=3D"_blank"> > pacsat-dev-leave(a)amsat.org</a><br> > Manage all of your AMSAT-NA mailing list preferences at <a href=3D"https://= > mailman.amsat.org/" rel=3D"noreferrer" target=3D"_blank"> > https://mailman.amsat.org</a><br> > </blockquote> > </div> > <br> > -----------------------------------------------------------<br> > <br> > pacsat-dev mailing list -- <a href=3D"mailto:[email protected]" target= > =3D"_blank">pacsat-dev(a)amsat.org</a><br> > View archives of this mailing list at <a href=3D"https://mailman.amsat.org/= > hyperkitty/list/pacsat-dev(a)amsat.org" target=3D"_blank"> > https://mailman.amsat.org/hyperkitty/list/[email protected]</a><br> > To unsubscribe send an email to <a href=3D"mailto:[email protected]= > g" target=3D"_blank"> > pacsat-dev-leave(a)amsat.org</a><br> > Manage all of your AMSAT-NA mailing list preferences at <a href=3D"https://= > mailman.amsat.org" target=3D"_blank"> > https://mailman.amsat.org</a><br> > </div> > </blockquote> > </div> > <br> > </div> > </div> > > <br> > -----------------------------------------------------------<br> > <br> > pacsat-dev mailing list -- <a href=3D"mailto:[email protected]" target= > =3D"_blank">pacsat-dev(a)amsat.org</a><br> > View archives of this mailing list at <a href=3D"https://mailman.amsat.org/= > hyperkitty/list/pacsat-dev(a)amsat.org" rel=3D"noreferrer" target=3D"_blank">= > https://mailman.amsat.org/hyperkitty/list/[email protected]</a><br> > To unsubscribe send an email to <a href=3D"mailto:[email protected]= > g" target=3D"_blank">pacsat-dev-leave(a)amsat.org</a><br> > Manage all of your AMSAT-NA mailing list preferences at <a href=3D"https://= > mailman.amsat.org" rel=3D"noreferrer" target=3D"_blank">https://mailman.ams= > at.org</a><br> > </blockquote></div> > > --00000000000059bbda060e872bbb-- > > --===============0108675984297293611== > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > > ----------------------------------------------------------- > > 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 > > --===============0108675984297293611==--

1 0

Blinky Working
by Bob Stricklin 09 Jan '24

09 Jan '24

I have a simple Blinky program working no the board. with this running we are pulling about 180 mA from the 5V supply. Still have things on the board that are not turned on yet. This is what i did to get it working… Using Halcogen I configured the Drivers, Pinmux and Het1. Then I only had to write a short program in sys_main.c. All attached here. Jim, your blinky code is not blinking LEDs. I checked with a scope also. Bob [cid:[email protected]] [cid:[email protected]] [cid:[email protected]]

1 0