Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/2MZEUOIIYV2BL4LHVSLJWJPW5NYWHAYO/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "2MZEUOIIYV2BL4LHVSLJWJPW5NYWHAYO",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/2MZEUOIIYV2BL4LHVSLJWJPW5NYWHAYO/?format=api",
    "sender": {
        "address": "bstrick (a) N5BRG.COM",
        "mailman_id": "953542c988dd4c549175bb02a8a6a1ed",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/953542c988dd4c549175bb02a8a6a1ed/emails/?format=api"
    },
    "sender_name": "Bob Stricklin",
    "subject": "[pacsat-dev] Re: Quick test for AX5043",
    "date": "2024-02-08T22:53:56Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Get MRAM size reports 512 which is 512 x 8 so 4 meg.\r\n\r\nTest MRAM seems to be working.\r\n\r\nOn Feb 8, 2024, at 4:47 PM, Bob Stricklin via pacsat-dev <[email protected]> wrote:\r\n\r\n\r\n\r\n<IMG_0005.jpeg>\r\n\r\nOk, I did clean project. Rebuild and load.\r\nThe clear MRAM\r\n\r\nSee 4 now.\r\n\r\nBob\r\nOn Feb 8, 2024, at 4:40 PM, Burns Fisher (AMSAT) via pacsat-dev <[email protected]> wrote:\r\n\r\n\r\nIt IS seeing 4 chips.  It is getting values that are not 0xff.  I think this is very promising!  Try get mram size too!\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n\r\nOn Thu, Feb 8, 2024 at 5:38 PM Bob Stricklin via pacsat-dev <[email protected]<mailto:[email protected]>> wrote:\r\n<IMG_0004.jpeg>\r\n\r\n\r\nI see version is q so I think this is most current. Not seeing 4 chips yet.\r\n\r\nBob\r\nOn Feb 8, 2024, at 4:01 PM, Burns\r\n\r\nFisher (AMSAT) via pacsat-dev <[email protected]<mailto:[email protected]>> wrote:\r\n\r\n\r\nOk, please also get X0.1q (just pushed upstream).\r\n\r\nI may have said before that I got one MRAM to work on my board.  Now I have changed a few things so that it seems to do at least some of the tests correctly.  I'm not 100% sure if it will work with only 1 and 4 chips or if it will work with yours as well.  But anyway, it is an improvement.  Do \"clear mram\" first.\r\n\r\n\r\nPacsat>get mram sr\r\nMRAM0: status ff, MRAM1: status 32\r\nMRAM2: status ff, MRAM3: status ff\r\n\r\nPacsat>clear mram\r\nPost Launch Time Set to 2 minutesSet to start in safe mode\r\nWOD Frequency,size set to Default, and WOD Indices initialized\r\nTelemetry min/max in MRAM initialized\r\nReset Count set to 0\r\nNonfatal error count zeroed (TBD)\r\nCRC calculated for init code and full code (TBD)\r\nMRAM Version Number Initialized\r\nMRAM config partition size is 1008 bytes\r\nMRAM file partition 1 size is 523280\r\n\r\nPacsat>get mram size\r\nMRAM Address Size=3\r\nPartition 0 size=1008, partition 1=523280\r\nMRAM0 size is 0KBytes, MRAM1 size is 512KBytes\r\nMRAM2 size is 0KBytes, MRAM3 size is 0KBytes\r\nPacsat>test mram 4 42\r\nNOTE:  This test will wipe out the file system and configuration values in MRAM.\r\n\r\nTesting with read/write size = 4 bytes, random value base is 0x1864\r\nWrite starting at 0KB\r\nWrite starting at 16KB\r\nWrite starting at 32KB\r\nWrite starting at 48KB\r\nWrite starting at 64KB\r\nWrite starting at 80KB\r\n<skipping a bunch of additional writes>\r\nRead starting at 0KB\r\nRead starting at 16KB\r\nRead starting at 32KB\r\nRead starting at 48KB\r\nRead starting at 64KB\r\nRead starting at 80KB\r\nRead starting at 96KB\r\nRead starting at 112KB\r\nRead starting at 128KB\r\n<...>\r\nRead starting at 432KB\r\nRead starting at 448KB\r\nRead starting at 464KB\r\nRead starting at 480KB\r\nRead starting at 496KB\r\nRead starting at 512KB\r\nTest is ok!  Time is 37 seconds\r\n\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n\r\nOn Thu, Feb 8, 2024 at 4:30 PM Bob Stricklin via pacsat-dev <[email protected]<mailto:[email protected]>> wrote:\r\nOk Burns. Will check soon. At the gym and will be home in about 30 minutes.\r\n\r\nGood that you fixed this.\r\n\r\nI added 20k pull-up on MOSI and security chip. Also moved the enable lines on the two supply control chips will give details on that later.\r\n\r\nBob\r\n\r\nOn Feb 8, 2024, at 3:07 PM, Burns Fisher (AMSAT) via pacsat-dev <[email protected]<mailto:[email protected]>> wrote:\r\n\r\n\r\nI got one MRAM working, specifically #1.  I apparently fixed the chip select for that one.\r\n\r\nPlease try \"get mram sr\" with X0.1p.  If they say something other than 0xff, they are probably working.  Don't mess with the other MRAM commands unless it sees all the MRAMs.  I think a lot of that code assumes there are 4 good MRAMs.\r\n\r\nIn the meantime, I now KNOW that most the SPI bus is ~good on my board, so I'll focus a bit more on the chip selects for 0 and 2.  If I have time, I'll see if I can get some of the other tests working for only some MRAMs.\r\n\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n\r\nOn Thu, Feb 8, 2024 at 9:20 AM Burns Fisher (AMSAT) <[email protected]<mailto:[email protected]>> wrote:\r\nOk, Bob, glad you figured out how to get the new code.\r\n\r\nRegarding 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.\r\n\r\nRegarding 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 :-)\r\n\r\nMore in a separate mailing.\r\n\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n\r\nOn Thu, Feb 8, 2024 at 4:17 AM Bob Stricklin via pacsat-dev <[email protected]<mailto:[email protected]>> wrote:\r\nI resolved the issue with GIT I had.\r\n\r\nI was setting things up initially with my GIT username and password and apparently you must in CCS.\r\n\r\nI have built and run Version ‘o’.\r\n\r\nI am seeing data  back from 2 of the AX5043s. Probably need to expand code to work with all 4 devices. Later.\r\n\r\nget ax returns this …. screen capture\r\n\r\n<Screenshot from 2024-02-08 02-56-00.png>\r\n\r\nget mram size just returns two of the mram   0 and 2 and indicates their size is 0k.\r\ntest 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.\r\nMRAM chips are 4 meg so maybe code only setup for 1 meg.\r\n\r\n\r\nMore testing on hardware later today.\r\n\r\nBob\r\n\r\n\r\nOn Feb 7, 2024, at 10:47 AM, Burns Fisher (AMSAT) <[email protected]<mailto:[email protected]>> wrote:\r\n\r\nYes, the same branch.  What errors are you getting?\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n\r\nOn Wed, Feb 7, 2024 at 11:33 AM Bob Stricklin <[email protected]<mailto:[email protected]>> wrote:\r\nBurns,\r\n\r\nConfirm for me the branch you are working with is\r\nWB1FJ_Port_to_Blinky\r\n\r\nI 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.\r\n\r\nBob\r\n\r\nOn Feb 6, 2024, at 5:34 PM, Bob Stricklin <[email protected]<mailto:[email protected]>> wrote:\r\n\r\n OK\r\n\r\nBob\r\n\r\nOn Feb 6, 2024, at 4:16 PM, Burns Fisher (AMSAT) via pacsat-dev <[email protected]<mailto:[email protected]>> wrote:\r\n\r\nI'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.\r\n\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n\r\nOn Tue, Feb 6, 2024 at 4:43 PM Burns Fisher (AMSAT) <[email protected]<mailto:[email protected]>> wrote:\r\nI added a quick test to tell if the 5043 SPI interface is working.  This is in version 0.1n and has been pushed upstream.\r\n\r\nPacsat>test ax\r\nAX5043 #0: Revision=7, scratch=7\r\nAX5043 #1: Revision=7, scratch=7\r\nAX5043 #2: Revision=119, scratch=119\r\nAX5043 #3: Revision=7, scratch=7\r\nAX5043 #4: Revision=119, scratch=119\r\nAX5043 #5: Revision=7, scratch=7\r\n\r\nThis 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.\r\n\r\nYou might as well try it on yours Bob.  In the meantime, I'll try to see if I can tell anything on mine.\r\n\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://mailman.amsat.org/>\r\n\r\n\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/2MZEUOIIYV2BL4LHVSLJWJPW5NYWHAYO/?format=api",
            "counter": 3,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "utf-8",
            "size": 26640,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/2MZEUOIIYV2BL4LHVSLJWJPW5NYWHAYO/attachment/3/attachment.html"
        },
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/2MZEUOIIYV2BL4LHVSLJWJPW5NYWHAYO/?format=api",
            "counter": 4,
            "name": "IMG_0005.jpeg",
            "content_type": "image/jpeg",
            "encoding": null,
            "size": 139647,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/2MZEUOIIYV2BL4LHVSLJWJPW5NYWHAYO/attachment/4/IMG_0005.jpeg"
        }
    ]
}