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

QEMU emulation not feasibly doable
by Corey Minyard 24 Feb '23

24 Feb '23

I was studying the design of the serial port and the N2HET device on the TMS570, and emulating that in QEMU is not really an option. Since that's how the debug serial port is done and perhaps how some I2C devices are accessed, it doesn't make sense to do the QEMU emulator. Just for details on this, the N2HET is a separate coprocessor, and would require writing an instruct set front end to work properly, or writing an emulator of some kind. That's a pretty big job in QEMU, but it could be done. However, even if you got one of these working, it still wouldn't work for our purposes. The way the N2HET is used, it's bit-banging (sending and receiving a bit at a time) in and out serial and I2C data. That's extremely timing dependent for serial (not so much for I2C), and an emulator is not going to be able to do that easily. Again, it could be done, but the code required to take the outputs of the N2HET and covert it back to bytes would be hard. It would be more feasible to emulate what the N2HET does in our configuration, but that's not going to be accepted into QEMU, so maintenance for this would fall on us. Sorry for the bad news. It would have been nice to have this. Looks like I'm going to need a board. Note, as an aside, this kind of thing uses a lot of power. The SCI and I2C devices on the TMS570 are likely to use a lot less power. Not all TMS570 SOCs have an I2C, though. -corey

1 0

PACSAT Weekly Engineering Meeting 2023-02-23
by Jonathan Brandenburg 23 Feb '23

23 Feb '23

Here's the info for tomorrow's meeting: *PACSAT Weekly Engineering Meeting 2022-02-23* Feb 23, 2023, 7:00 – 8:00 PM (America/Chicago) *Please join my meeting from your computer, tablet or smartphone.* https://meet.goto.com/742034085 *You can also dial in using your phone.* Access Code: 742-034-085 United States: +1 (872) 240-3412 <tel:+18722403412,,742034085> *Get the app now and be ready when your first meeting starts:* https://meet.goto.com/install -- jbrandenburg(a)amsat.org

1 0

Re: More documentation
by Chris Thompson 22 Feb '23

22 Feb '23

Thanks Burns. These were very helpful. 73 Chris G0KLA On Tue, Feb 21, 2023 at 10:47 AM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I have copied documentation about the flight software from both the Golf > SVN and from the Golf redmine wiki and placed them in the pacsat reference > repo under "Golf". This include Golf Driver Documentation and Golf Flight > Software Description. Both are reasonably up to date, although the flight > software has a lot of Golf stuff that is not relevant. However it does > talk about how various RTOS primitives are used and the general scheme of > how it is put together. > > This is all on github under AMSAT-NA/pacsat/reference/Golf. > > 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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

More documentation
by Burns Fisher (AMSAT) 21 Feb '23

21 Feb '23

I have copied documentation about the flight software from both the Golf SVN and from the Golf redmine wiki and placed them in the pacsat reference repo under "Golf". This include Golf Driver Documentation and Golf Flight Software Description. Both are reasonably up to date, although the flight software has a lot of Golf stuff that is not relevant. However it does talk about how various RTOS primitives are used and the general scheme of how it is put together. This is all on github under AMSAT-NA/pacsat/reference/Golf. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

LTM (PC104) document in git
by Burns Fisher (AMSAT) 17 Feb '23

17 Feb '23

Last night I promised to provide the current pinout on the PC-104 used by the LTM. I decided to put it in pacsat.git rather than just mailing it. I then noticed that there was already a subdirectory called "reference" which had things like the RT-IHU data whose main home is actually elsewhere. That seemed like a good plan, so I added an "LTM" directory, and put the entire LTM Generic ICD there. The LTM Generic ICD may be changed in the future, but the intention is that it is the ICD for groups using the LTM, but with some choices. The plan is that there would be a "customer"-specific ICD as an appendix that showed which choices were made. But in any case, page 9 shows the PC-104 pinout that I was asked for. Note: Jonathan says he prefers source documents to PDF. My opinion is that if a document is going to be sent around to a number of people/places, it should be sent as PDF, largely because it is difficult to change the PDF. This (to me) ensures much better version control if the document is in multiple places, so that is what I put in the pacsat document git (the source file is in the GOLF SVN). I'm guessing Jonathan and I don't really much disagree but are maybe talking about somewhat different cases. But I'd be happy to talk about it. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: PACSAT Weekly Engineering Meeting 2023-02-16
by Rich Gopstein 16 Feb '23

16 Feb '23

I can't attend tonight. Rich On Thu, Feb 16, 2023, 7:57 AM Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Here is the meeting info for tonight's meeting: > > *PACSAT Weekly Engineering Meeting 2023-02-16* > Feb 16, 2023, 7:00 – 8:00 PM (America/Chicago) > > > *Please join my meeting from your computer, tablet or smartphone.* > https://meet.goto.com/213900749 > > *You can also dial in using your phone.* > Access Code: 213-900-749 > United States: +1 (669) 224-3412 <+16692243412,,213900749> > > > *Get the app now and be ready when your first meeting starts:* > https://meet.goto.com/install > > > > > -- jbrandenburg(a)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 >

1 0

PACSAT Weekly Engineering Meeting 2023-02-16
by Jonathan Brandenburg 16 Feb '23

16 Feb '23

Here is the meeting info for tonight's meeting: *PACSAT Weekly Engineering Meeting 2023-02-16* Feb 16, 2023, 7:00 – 8:00 PM (America/Chicago) *Please join my meeting from your computer, tablet or smartphone.* https://meet.goto.com/213900749 *You can also dial in using your phone.* Access Code: 213-900-749 United States: +1 (669) 224-3412 <tel:+16692243412,,213900749> *Get the app now and be ready when your first meeting starts:* https://meet.goto.com/install -- jbrandenburg(a)amsat.org

1 0

Fwd: BPSK on ax5043 Service Request #242527
by Rich Gopstein 13 Feb '23

13 Feb '23

---------- Forwarded message --------- From: <onhelp(a)onsemi.com> Date: Tue, Dec 17, 2019 at 11:51 AM Subject: Re: BPSK on ax5043 Service Request #242527 To: <rich(a)ourowndomain.com> Response From ON Semiconductor Service Request #242527 ON Semiconductor Technical Support Center Voice Mail: 800-282-9855 (US & Canada) Web Site: http://www.onsemi.com/pub/tech_support **************************************************************** Please do not reply to this email. Please submit any additional questions via our web site or by calling the ON Semiconductor Technical Support Center. Thank you. **************************************************************** Hello Rich Gopstein, Thank you for contacting ON Semiconductor. There is option for PSK mode only, configuration can be created with AX-RadioLab. You need to enter '1962' in the TX Periodic field on the main screen, and press enter. PSK mode, along with other more advanced options will be available in the PHY screen. If you have any further questions, please do not hesitate to contact us back. Regards, Martin ON Semiconductor Technical Support Center Subject: BPSK on ax5043 Description of customer request: I am working on software to drive an AX5043 which needs to transmit and receive BPSK. It doesn't look like AX-RadioLAB has BPSK as an option and I can't find any application notes about using BPSK on the ax5043.

2 1

Re: Pacsat dev meeting 2-9-2023
by Burns Fisher (AMSAT) 09 Feb '23

09 Feb '23

I'm afraid that I can (almost) never make it on the 2nd Thursday of the month, so I won't be there tonight. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Feb 9, 2023 at 9:32 AM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat dev meeting 2-9-2023 > Thu, Feb 9, 2023 7:00 PM - 9:00 PM (CST) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/618296317 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (646) 749-3122 > - One-touch: tel:+16467493122,,618296317# > > Access Code: 618-296-317 > > > 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 meeting 2-9-2023
by Bill 09 Feb '23

09 Feb '23

Pacsat dev meeting 2-9-2023 Thu, Feb 9, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/618296317 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (646) 749-3122 - One-touch: tel:+16467493122,,618296317# Access Code: 618-296-317 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0