At this point we don't even know if the radio SPI is working. Plus most of the tasks are turned off just to simplify debugging.
Bob, I pushed upstream the version that should (might???) have the correct chip select lines. Could you please try this one?
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Mon, Feb 5, 2024 at 5:22 PM Chris Thompson via pacsat-dev < pacsat-dev@amsat.org> wrote:
Looks promising but the radio chips have the wrong frequencies. Those are loaded at boot and these routines read back from the chips.
I think it prints error messages if the chips don't respond though.. Need to check that but I am out with family at the moment.
Chris
On Mon, Feb 5, 2024, 17:05 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev@amsat.org> wrote:
BTW, I don't if I ever said this (if so, just a remnider):
Before you generate code from HalCoGen, you MUST put the code that is in CCS back in the place where HalCoGen puts its code. That is because there are a few places where I put some stuff in the "USER CODE BEGIN" section. Look in particular at sys_main.c and spi.c (in which I actually commented out a whole bunch of code and put in my own version in hcgExtras).
I run CCS on Linux and HCG on Windows, and use dropbox to connect them. HalCoGen writes directly into DropBox. Then I just copy all the files on the Linux side from dropbox into CCS, and if I make any changes in the USER CODE section then I copy it from CCS back to HCG.
I'm not sure what you meant about HCG a few mails back. The HalCoGen file PACSatBlinky.hcg certainly is set up for the TMS570LS0914.
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Mon, Feb 5, 2024 at 4:56 PM Bob Stricklin via pacsat-dev < pacsat-dev@amsat.org> wrote:
Just realized that the second temp sensor is not on this board. I took it off to change address and have not put it back yet. Probably will work fine.
*From:* Burns Fisher (AMSAT) via pacsat-dev pacsat-dev@amsat.org *Sent:* Monday, February 5, 2024 3:53 PM *To:* Bob Stricklin bstrick@n5brg.com *Cc:* Bill via pacsat-dev pacsat-dev@amsat.org *Subject:* [pacsat-dev] Re: One board now talking
Oh, I see. So this is saying that I2c in general is ok, but that the temp sensor near the CPU is not working for whatever reason (bad bus connection, bad address bit connection, or bad chip).
And regarding the MRAM, I have the chip select wrong on at least one of those MRAM devices. I just found that earlier and did not push it up to the repository.. Let me check what else I have done since I pushed upstream, and if all is ok, I'll push this change too. Looks like most everything in the MRAM is ok otheriwise (whew! Was driving me crazy)
I see you sent something else. Have not seen it yet but will send this.
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Mon, Feb 5, 2024 at 4:43 PM Burns Fisher (AMSAT) wb1fj@fisher.cc wrote:
Ok, looks like two of the MRAMs are ok, and two are not for whatever reason. Oh, I bet I know...I think I got the chip select lines wrong on one or two of them. Funny the temp actually looks ok despite the error. In the middle of checking something else. Will get back after a bit more testing. 73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Mon, Feb 5, 2024 at 4:41 PM Bob Stricklin via pacsat-dev < pacsat-dev@amsat.org> wrote:
Pacsat> Pacsat>get mram sr MRAM0: status 32, MRAM1: status ff MRAM2: status 2, MRAM3: status ff Pacsat>get temp CPU Temp request failed Transmitter temp: 99 ( 29.5 degrees C) Pacsat>
*From:* Burns Fisher (AMSAT) wb1fj@fisher.cc *Sent:* Monday, February 5, 2024 3:35 PM *To:* Bob Stricklin bstrick@n5brg.com *Cc:* Bill via pacsat-dev pacsat-dev@amsat.org *Subject:* Re: [pacsat-dev] One board now talking
Oh, I just sent you a mail before seeing this.
Wow! Looks like there may be something wrong with my board. Could you do "get mram sr" please? You could try "get temp" also.
I'm not sure if those are the right values for the DCT (the AX5043). I know I had a quick way at one point that I could tell if one particular register was correct. I'll see if I can find it.
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Mon, Feb 5, 2024 at 4:24 PM Bob Stricklin via pacsat-dev < pacsat-dev@amsat.org> wrote:
After getting TX and RX connected correctly now working. Do not know what the correct report back is but here is some checks...
This board has four 4Mb MRAMs installed.
Pacsat>get version
AMSAT-NA PacSat Console Flight Software X0.1k (built on Feb 4 2024 at 21:53:10) Compiled *RELEASE* **X, E, U, or DEBUG Version: Not configured for flight** Watchdog NOT Enabled Using FreeRTOS withOUT premption enabled; Free heap size is 75504 Flash memory size 1Mb+0Kb MRAM config data partition size=1008, file system size=1047568 Pacsat>>get version
AMSAT-NA PacSat Console Flight Software X0.1k (built on Feb 4 2024 at 21:53:10) Compiled *RELEASE* **X, E, U, or DEBUG Version: Not configured for flight** Watchdog NOT Enabled Using FreeRTOS withOUT premption enabled; Free heap size is 75504 Flash memory size 1Mb+0Kb MRAM config data partition size=1008, file system size=1047568 Pacsat>
Pacsat>get RSSI RSSI is -64 dBm Pacsat>
Pacsat>get ax AX5043 dev 1 TX: FIFOSTAT: 00 PWRMODE:: 77 XTALCAP: 119 PLLLOOP: 77 PLLCPI: 77 PLLVCOI: 77 PLLRANGINGA: 77 PLLVCODIV: 77 FREQ 1911466666 Hz MODULATION: 77 TXPWRCOEFFB0: 77 TXPWRCOEFFB1: 77
AX5043 dev 0 RX: FIFOSTAT: 00 PWRMODE: 67 XTALCAP: 103 PLLLOOP: 67 PLLCPI: 67 PLLVCOI: 67 PLLRANGINGA: 67 PLLVCODIV: 67 FREQ 1654462744 Hz MODULATION: 67 TXPWRCOEFFB0: 67 TXPWRCOEFFB1: 67 Pacsat>
pacsat-dev mailing list -- pacsat-dev@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@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- pacsat-dev@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@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- pacsat-dev@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@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- pacsat-dev@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@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- pacsat-dev@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@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org