Ok, Bob, glad you figured out how to get the new code.

Regarding the MRAM. I at first thought that you said "okay", but now I think you said zero K. I originally set up the MRAM code to figure out the size of the MRAMs, whether they needed 2 or 3 address bytes, and how many were present. But I only had the one example of Jim's launchpad board, so I'm not surprised it is not quite right for larger MRAMs and especially if the failing MRAMs are not in order (i.e. 0 and 1 work, 2 and 3 do not). But since none work on my board, I could not do anything more. As soon as I can get a board with working MRAMs, I'll fix all that. Also with all the MRAM errors that I get I have disabled a number of the tasks because they quickly failed and reset the processor. I'll fix that when I get a working MRAM board.

Regarding the 5043: Did you do "test ax"? That shows a couple registers from each of the 5043s which we know the value of. I think you can say "get ax 2" to read AX5043 #2, but I'm less sure about that. I did not display all 5 just because I did not know the correct values anyway, and it would just run off the bottom of the screen :-)

More in a separate mailing.

73,

Burns Fisher, WB1FJ

AMSAT(R) Engineering -- Flight Software

On Thu, Feb 8, 2024 at 4:17 AM Bob Stricklin via pacsat-dev <pacsat-dev@amsat.org> wrote:

I resolved the issue with GIT I had.

I was setting things up initially with my GIT username and password and apparently you must in CCS.

I have built and run Version ‘o’.

I am seeing data back from 2 of the AX5043s. Probably need to expand code to work with all 4 devices. Later.

get ax returns this …. screen capture

get mram size just returns two of the mram 0 and 2 and indicates their size is 0k.

test mram 1 42 seems to run saying Write starting at etc and goes from 0KB to 1024KB. Then it does a Read in same area and does not report any errors but says: Test is OK! Time is 75 seconds.

MRAM chips are 4 meg so maybe code only setup for 1 meg.

More testing on hardware later today.

Bob

On Feb 7, 2024, at 10:47 AM, Burns Fisher (AMSAT) <wb1fj@fisher.cc> wrote:

Yes, the same branch. What errors are you getting?

73,

Burns Fisher, WB1FJ

AMSAT(R) Engineering -- Flight Software

On Wed, Feb 7, 2024 at 11:33 AM Bob Stricklin <bstrick@n5brg.com> wrote:

Burns,

Confirm for me the branch you are working with is

WB1FJ_Port_to_Blinky

I am having an issue getting a clean build. I know you were still working CS problem but I am trying to get the GIT build process to work properly.

Bob

On Feb 6, 2024, at 5:34 PM, Bob Stricklin <bstrick@n5brg.com> wrote:

OK

Bob

On Feb 6, 2024, at 4:16 PM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev@amsat.org> wrote:

I'm reasonably sure that I have the chip select lines screwed up in s/w. I have band rehearsal tonight, so I won't be able to do anything till tomorrow.

73,

Burns Fisher, WB1FJ

AMSAT(R) Engineering -- Flight Software

On Tue, Feb 6, 2024 at 4:43 PM Burns Fisher (AMSAT) <wb1fj@fisher.cc> wrote:

I added a quick test to tell if the 5043 SPI interface is working. This is in version 0.1n and has been pushed upstream.

Pacsat>test ax
AX5043 #0: Revision=7, scratch=7
AX5043 #1: Revision=7, scratch=7
AX5043 #2: Revision=119, scratch=119
AX5043 #3: Revision=7, scratch=7
AX5043 #4: Revision=119, scratch=119
AX5043 #5: Revision=7, scratch=7

This is what it looks like. However the numbers are all wrong. I'm not sure how they can be other than right or 0xff, but something is screwed up. The Revision should be 0x51, which would be printed in decimal as 81. The scratch register, I wrote the AX5043 number into, so each one should read the same as the first number in the line, i.e. 0, 1, 2, 3, 4, 5.

You might as well try it on yours Bob. In the meantime, I'll try to see if I can tell anything on mine.

73,

Burns Fisher, WB1FJ

AMSAT(R) Engineering -- Flight Software

-----------------------------------------------------------

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