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

Pacsat dev meeting #6
by Bill 08 Dec '22

08 Dec '22

Pacsat dev meeting #6 Thu, Dec 8, 2022 7:00 PM - 8:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/285772213 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,,285772213# Access Code: 285-772-213 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install Agenda: Open

1 0

Summary of several bits of work
by Burns Fisher (AMSAT) 06 Dec '22

06 Dec '22

Rich, Chris, and I have had a number of private emails, so this is a quick summary: 1) We have all been able to "talk to" the Pi 5043 board over SPI from the LaunchPad, although one of the boards had a short that required fixing. 2) Chris has managed to get it to transmit. 3) Rich and Burns (mainly Rich) determined that L8 on Pi 5043 board is actually a 0-ohm resistor. That's ok for 70cm. But for 2m, an inductor is needed. Rich has made a hand wound air core coil that seems to work. Burns tried one that did not work. I probably screwed up soldering the big coil to the tiny pad. In fact I probably lifted the foil. I recommend if we are going to continue with the Pi board we get the actual SM 0603 or 0402 or whatever inductors. 4) Eric made up 3 MRAM-on-DIP adapter boards for me to check out, but we think Chris has successfully done that too. I will write the s/w to test more thoroughly and to allow multiple MRAMs to work and to sleep when not in use. 5) The I2c temperature chip on the Pi board works fine with the Launchpad. In summary, I think we are convinced that the chips are all usable with the Launchpad. I'd recommend going ahead with a board that contains a couple of MRAMs and a couple of 5043s. Jumpers are REAL easy to make mistakes with, and jumpers to 4 different boards (2 mrams, 2 5043s) would be a real bear to use. I'm most likely not going to be available on Thursday unless my monthly 6:30 in-person meeting gets out early! 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Updated pacsat sw
by Burns Fisher (AMSAT) 05 Dec '22

05 Dec '22

Hi All, I've just merged in a branch (after testing by Chris) which has a HALCoGen configuration that is specifically for the LaunchPad. In addition, I've moved the console to be on a real UART rather than the N2HET emulated one (which has some problems with missing characters). The console serial connections are now: Ground: pin 32 Rx: Pin 33 Tx Pin 34 Chris and I are both able to talk to the 5043 chip on the Pi board, but at some point during initialization, the crystal stops oscillating. As soon as I get a couple MRAMs to use (maybe today or tomrorow?) I'll try to get them set up both to sleep when not in use and to make the fact that there are multiple MRAMs transparent--just specify an address and it will choose the right one. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

2 3

New HALCoGen ready to test
by Burns Fisher (AMSAT) 02 Dec '22

02 Dec '22

Hi, As discussed last night, I have a HALCoGen configuration set up that is specifically designed for the LaunchPad. I've also added a command "test mram" and another called "mram wren". The former writes 10 bytes into the mram at a specified address and then reads them back. It prints what it was writing, and what the read-back results are. It does this twice with one pattern of data and once with a different one. You can specify an address following the command. For example "test mram 100". It will take 0xnnn" as well for hex "mram wren" sends a write enable command to the mram. The existing command "get mram sr" should show this. If it returns "40" the chip is not write enabled. If it returns 42, it is write enabled. There is also, in config.h, a #ifdef FRAM64K. If this is set, the address sent to the non-volatile RAM is 2 bytes. If it is not defined (just comment it out) it will be 3 bytes. I've left it set up for 3-byte addresses since that is what Chris is using. Please let me know if you have tried this successfully, especially with a real MRAM (most of those tests were for my funky F-RAM). If so, I'll move it to the main branch. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

2 10

Last nights dev meeting
by Bill 02 Dec '22

02 Dec '22

Thanks for attending. See you next Thursday. Bill

2 1

AX5043 I/Q Data
by Jim McCullers 02 Dec '22

02 Dec '22

Interesting side note on the AX5043. https://www.onsemi.com/forum/t/i-q-data-from-ax5043-and-ax5045-experimental- feature/879

1 0

Pacsat Dev Meeting tonight
by Bill 01 Dec '22

01 Dec '22

Pacsat Dev Mtg #5 Thu, Dec 1, 2022 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/542795717 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (408) 650-3123 - One-touch: tel:+14086503123,,542795717# Access Code: 542-795-717 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install Agenda: Review task list Discuss Fram/Mram daughter board. Bill

1 0