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

Re: Filesystem code
by Corey Minyard 08 Apr '23

08 Apr '23

On Sat, Apr 08, 2023 at 09:52:49PM +0000, Chris Thompson via pacsat-dev wrote: > Reading and writing works fine! > > This looks fantastic Corey. No doubt there is a lot of work still to tweak > all the settings and make sure it will be reliable, but my initial > impression is very good. Well done. Well, you and Burns did a lot of the work of testing and debugging. If I hadn't removed the initMRAM() call from main.c it would have gone a lot better. It reminds me of the olden days when the people that wrote the code sent it to another group to punch onto cards and submit it and bring you back the results. It does make you review your code more carefully. We need to figure out what to do with the volume name and maybe tweak partition sizes. But it could probably go to the main branch at this point. Thanks for working on this, -corey

1 0

Re: Filesystem code
by Chris Thompson 08 Apr '23

08 Apr '23

Reading and writing works fine! This looks fantastic Corey. No doubt there is a lot of work still to tweak all the settings and make sure it will be reliable, but my initial impression is very good. Well done. 73 Chris On Sat, Apr 8, 2023 at 4:50 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Burns, > > I pulled your branch directly and now it runs without the errors. > Something strange had happened in the merge. > > Anyway, that was the issue. Now I can write to the file system. You do > need / as the volume name and / as the root dir. So //test_file worked. > /test_file did not. Despite the documentation suggesting it would. > > I'll try to read it back next. > > 73 > Chris > > On Sat, Apr 8, 2023 at 4:38 PM Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Better check if there is a call to initMRAM in main.c immediately after >> SPIInit(MRAM3Dev). It is line 206 for me. That's what I had to do in >> order to avoid all the errors at startup. >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Sat, Apr 8, 2023 at 4:26 PM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> From what I can tell in the developer guide, "//test_file" should have >>> worked. But so should "/test_file". It says that as a special case a >>> volume prefix by itself is interpreted as a reference to the root directory. >>> >>> So, hmmm.... >>> >>> Chris >>> >>> On Sat, Apr 8, 2023 at 3:36 PM Chris Thompson via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> Burns, I think the initMRAM() is there. I merged your branch in. I >>>> see the function call in ConsolTask() right after the SPInit() calls for >>>> the MRAMs. But I also see a lot of MRAM errors at boot. Error 19s and >>>> Error 20s... >>>> >>>> Corey, I tried //test_file and that did not work either. >>>> >>>> 73 >>>> Chris >>>> >>>> On Sat, Apr 8, 2023 at 2:54 PM Burns Fisher (AMSAT) via pacsat-dev < >>>> pacsat-dev(a)amsat.org> wrote: >>>> >>>>> Chris, I assume that you did add the "initMRAM" near boot (right after >>>>> the SPI init). If not, you may have to do format the file system after >>>>> doing it because it may have the size and the partition setup wrong >>>>> otherwise. >>>>> >>>>> 73, >>>>> >>>>> Burns Fisher, WB1FJ >>>>> *AMSAT(R) Engineering -- Flight Software* >>>>> >>>>> >>>>> On Sat, Apr 8, 2023 at 2:39 PM Corey Minyard <minyard(a)acm.org> wrote: >>>>> >>>>>> On Sat, Apr 08, 2023 at 02:19:29PM -0400, Chris Thompson wrote: >>>>>> > I tried a simple example but I can't open a file. Is there a >>>>>> volume name >>>>>> > that I need to specify? I presume you don't need to create a >>>>>> directory. >>>>>> >>>>>> "/" should be the volume name, but maybe you need two of them? I >>>>>> wasn't >>>>>> sure from what the documentation said. >>>>>> >>>>>> If you can open "//test_file", then that's what it is. >>>>>> >>>>>> -corey >>>>>> >>>>>> > >>>>>> > Here is the code, but the open fails with "No such file or >>>>>> directory" >>>>>> > >>>>>> > // TEST File System >>>>>> > char *test_string = "This is data"; >>>>>> > int32_t fp; >>>>>> > printf("FS Test: Writing:\n"); >>>>>> > fp = red_open("/test_file", RED_O_CREAT | RED_O_WRONLY); >>>>>> > if (fp != -1) { >>>>>> > printf("Writing string\n"); >>>>>> > int32_t numOfBytesWritten = red_write(fp, test_string, >>>>>> > strlen(test_string)); >>>>>> > if (numOfBytesWritten == strlen(test_string)) { >>>>>> > printf("Success\n"); >>>>>> > } else { >>>>>> > printf("Write returned: %d\n",numOfBytesWritten); >>>>>> > if (numOfBytesWritten == -1) >>>>>> > printf("Unable to write to file: %s\n", >>>>>> > red_strerror(red_errno)); >>>>>> > } >>>>>> > int32_t rc = red_close(fp); >>>>>> > if (rc != 0) { >>>>>> > printf("Unable to close file: %s\n", >>>>>> red_strerror(red_errno)); >>>>>> > } >>>>>> > >>>>>> > } else { >>>>>> > printf("Unable to open file: %s\n", >>>>>> red_strerror(red_errno)); >>>>>> > } >>>>>> > >>>>>> > Any thoughts? >>>>>> > >>>>>> > 73 >>>>>> > Chris >>>>>> > >>>>>> > On Fri, Apr 7, 2023 at 5:10 PM Burns Fisher (AMSAT) via pacsat-dev < >>>>>> > pacsat-dev(a)amsat.org> wrote: >>>>>> > >>>>>> > > >I assumed that since this was ARM it was little endian. >>>>>> > > >>>>>> > > Yeah, I would have too. But apparently ARM can go either way. >>>>>> Turns out >>>>>> > > that for some reason the automotive world seems to standardize on >>>>>> big >>>>>> > > endian. This has caused nothing but hassle on the TMS570 (the >>>>>> STM32L is >>>>>> > > little). >>>>>> > > >>>>>> > > >>>>>> > > ----------------------------------------------------------- >>>>>> > > >>>>>> > > 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 >>>>>> >>>>> >>>>> ----------------------------------------------------------- >>>>> >>>>> 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 >>>> >>>> ----------------------------------------------------------- >>>> >>>> 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 >>> >>> ----------------------------------------------------------- >>> >>> 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 >>> >> >> ----------------------------------------------------------- >> >> 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 > > ----------------------------------------------------------- > > 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

Re: Filesystem code
by Chris Thompson 08 Apr '23

08 Apr '23

Burns, I pulled your branch directly and now it runs without the errors. Something strange had happened in the merge. Anyway, that was the issue. Now I can write to the file system. You do need / as the volume name and / as the root dir. So //test_file worked. /test_file did not. Despite the documentation suggesting it would. I'll try to read it back next. 73 Chris On Sat, Apr 8, 2023 at 4:38 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Better check if there is a call to initMRAM in main.c immediately after > SPIInit(MRAM3Dev). It is line 206 for me. That's what I had to do in > order to avoid all the errors at startup. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Sat, Apr 8, 2023 at 4:26 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> From what I can tell in the developer guide, "//test_file" should have >> worked. But so should "/test_file". It says that as a special case a >> volume prefix by itself is interpreted as a reference to the root directory. >> >> So, hmmm.... >> >> Chris >> >> On Sat, Apr 8, 2023 at 3:36 PM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Burns, I think the initMRAM() is there. I merged your branch in. I see >>> the function call in ConsolTask() right after the SPInit() calls for the >>> MRAMs. But I also see a lot of MRAM errors at boot. Error 19s and Error >>> 20s... >>> >>> Corey, I tried //test_file and that did not work either. >>> >>> 73 >>> Chris >>> >>> On Sat, Apr 8, 2023 at 2:54 PM Burns Fisher (AMSAT) via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> Chris, I assume that you did add the "initMRAM" near boot (right after >>>> the SPI init). If not, you may have to do format the file system after >>>> doing it because it may have the size and the partition setup wrong >>>> otherwise. >>>> >>>> 73, >>>> >>>> Burns Fisher, WB1FJ >>>> *AMSAT(R) Engineering -- Flight Software* >>>> >>>> >>>> On Sat, Apr 8, 2023 at 2:39 PM Corey Minyard <minyard(a)acm.org> wrote: >>>> >>>>> On Sat, Apr 08, 2023 at 02:19:29PM -0400, Chris Thompson wrote: >>>>> > I tried a simple example but I can't open a file. Is there a volume >>>>> name >>>>> > that I need to specify? I presume you don't need to create a >>>>> directory. >>>>> >>>>> "/" should be the volume name, but maybe you need two of them? I >>>>> wasn't >>>>> sure from what the documentation said. >>>>> >>>>> If you can open "//test_file", then that's what it is. >>>>> >>>>> -corey >>>>> >>>>> > >>>>> > Here is the code, but the open fails with "No such file or directory" >>>>> > >>>>> > // TEST File System >>>>> > char *test_string = "This is data"; >>>>> > int32_t fp; >>>>> > printf("FS Test: Writing:\n"); >>>>> > fp = red_open("/test_file", RED_O_CREAT | RED_O_WRONLY); >>>>> > if (fp != -1) { >>>>> > printf("Writing string\n"); >>>>> > int32_t numOfBytesWritten = red_write(fp, test_string, >>>>> > strlen(test_string)); >>>>> > if (numOfBytesWritten == strlen(test_string)) { >>>>> > printf("Success\n"); >>>>> > } else { >>>>> > printf("Write returned: %d\n",numOfBytesWritten); >>>>> > if (numOfBytesWritten == -1) >>>>> > printf("Unable to write to file: %s\n", >>>>> > red_strerror(red_errno)); >>>>> > } >>>>> > int32_t rc = red_close(fp); >>>>> > if (rc != 0) { >>>>> > printf("Unable to close file: %s\n", >>>>> red_strerror(red_errno)); >>>>> > } >>>>> > >>>>> > } else { >>>>> > printf("Unable to open file: %s\n", red_strerror(red_errno)); >>>>> > } >>>>> > >>>>> > Any thoughts? >>>>> > >>>>> > 73 >>>>> > Chris >>>>> > >>>>> > On Fri, Apr 7, 2023 at 5:10 PM Burns Fisher (AMSAT) via pacsat-dev < >>>>> > pacsat-dev(a)amsat.org> wrote: >>>>> > >>>>> > > >I assumed that since this was ARM it was little endian. >>>>> > > >>>>> > > Yeah, I would have too. But apparently ARM can go either way. >>>>> Turns out >>>>> > > that for some reason the automotive world seems to standardize on >>>>> big >>>>> > > endian. This has caused nothing but hassle on the TMS570 (the >>>>> STM32L is >>>>> > > little). >>>>> > > >>>>> > > >>>>> > > ----------------------------------------------------------- >>>>> > > >>>>> > > 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 >>>>> >>>> >>>> ----------------------------------------------------------- >>>> >>>> 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 >>> >>> ----------------------------------------------------------- >>> >>> 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 >> >> ----------------------------------------------------------- >> >> 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 >> > > ----------------------------------------------------------- > > 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

Re: Filesystem code
by Burns Fisher (AMSAT) 08 Apr '23

08 Apr '23

Better check if there is a call to initMRAM in main.c immediately after SPIInit(MRAM3Dev). It is line 206 for me. That's what I had to do in order to avoid all the errors at startup. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Sat, Apr 8, 2023 at 4:26 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > From what I can tell in the developer guide, "//test_file" should have > worked. But so should "/test_file". It says that as a special case a > volume prefix by itself is interpreted as a reference to the root directory. > > So, hmmm.... > > Chris > > On Sat, Apr 8, 2023 at 3:36 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Burns, I think the initMRAM() is there. I merged your branch in. I see >> the function call in ConsolTask() right after the SPInit() calls for the >> MRAMs. But I also see a lot of MRAM errors at boot. Error 19s and Error >> 20s... >> >> Corey, I tried //test_file and that did not work either. >> >> 73 >> Chris >> >> On Sat, Apr 8, 2023 at 2:54 PM Burns Fisher (AMSAT) via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Chris, I assume that you did add the "initMRAM" near boot (right after >>> the SPI init). If not, you may have to do format the file system after >>> doing it because it may have the size and the partition setup wrong >>> otherwise. >>> >>> 73, >>> >>> Burns Fisher, WB1FJ >>> *AMSAT(R) Engineering -- Flight Software* >>> >>> >>> On Sat, Apr 8, 2023 at 2:39 PM Corey Minyard <minyard(a)acm.org> wrote: >>> >>>> On Sat, Apr 08, 2023 at 02:19:29PM -0400, Chris Thompson wrote: >>>> > I tried a simple example but I can't open a file. Is there a volume >>>> name >>>> > that I need to specify? I presume you don't need to create a >>>> directory. >>>> >>>> "/" should be the volume name, but maybe you need two of them? I wasn't >>>> sure from what the documentation said. >>>> >>>> If you can open "//test_file", then that's what it is. >>>> >>>> -corey >>>> >>>> > >>>> > Here is the code, but the open fails with "No such file or directory" >>>> > >>>> > // TEST File System >>>> > char *test_string = "This is data"; >>>> > int32_t fp; >>>> > printf("FS Test: Writing:\n"); >>>> > fp = red_open("/test_file", RED_O_CREAT | RED_O_WRONLY); >>>> > if (fp != -1) { >>>> > printf("Writing string\n"); >>>> > int32_t numOfBytesWritten = red_write(fp, test_string, >>>> > strlen(test_string)); >>>> > if (numOfBytesWritten == strlen(test_string)) { >>>> > printf("Success\n"); >>>> > } else { >>>> > printf("Write returned: %d\n",numOfBytesWritten); >>>> > if (numOfBytesWritten == -1) >>>> > printf("Unable to write to file: %s\n", >>>> > red_strerror(red_errno)); >>>> > } >>>> > int32_t rc = red_close(fp); >>>> > if (rc != 0) { >>>> > printf("Unable to close file: %s\n", >>>> red_strerror(red_errno)); >>>> > } >>>> > >>>> > } else { >>>> > printf("Unable to open file: %s\n", red_strerror(red_errno)); >>>> > } >>>> > >>>> > Any thoughts? >>>> > >>>> > 73 >>>> > Chris >>>> > >>>> > On Fri, Apr 7, 2023 at 5:10 PM Burns Fisher (AMSAT) via pacsat-dev < >>>> > pacsat-dev(a)amsat.org> wrote: >>>> > >>>> > > >I assumed that since this was ARM it was little endian. >>>> > > >>>> > > Yeah, I would have too. But apparently ARM can go either way. >>>> Turns out >>>> > > that for some reason the automotive world seems to standardize on >>>> big >>>> > > endian. This has caused nothing but hassle on the TMS570 (the >>>> STM32L is >>>> > > little). >>>> > > >>>> > > >>>> > > ----------------------------------------------------------- >>>> > > >>>> > > 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 >>>> >>> >>> ----------------------------------------------------------- >>> >>> 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 >> >> ----------------------------------------------------------- >> >> 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 > > ----------------------------------------------------------- > > 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

Re: Filesystem code
by Chris Thompson 08 Apr '23

08 Apr '23

From what I can tell in the developer guide, "//test_file" should have worked. But so should "/test_file". It says that as a special case a volume prefix by itself is interpreted as a reference to the root directory. So, hmmm.... Chris On Sat, Apr 8, 2023 at 3:36 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Burns, I think the initMRAM() is there. I merged your branch in. I see > the function call in ConsolTask() right after the SPInit() calls for the > MRAMs. But I also see a lot of MRAM errors at boot. Error 19s and Error > 20s... > > Corey, I tried //test_file and that did not work either. > > 73 > Chris > > On Sat, Apr 8, 2023 at 2:54 PM Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Chris, I assume that you did add the "initMRAM" near boot (right after >> the SPI init). If not, you may have to do format the file system after >> doing it because it may have the size and the partition setup wrong >> otherwise. >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Sat, Apr 8, 2023 at 2:39 PM Corey Minyard <minyard(a)acm.org> wrote: >> >>> On Sat, Apr 08, 2023 at 02:19:29PM -0400, Chris Thompson wrote: >>> > I tried a simple example but I can't open a file. Is there a volume >>> name >>> > that I need to specify? I presume you don't need to create a >>> directory. >>> >>> "/" should be the volume name, but maybe you need two of them? I wasn't >>> sure from what the documentation said. >>> >>> If you can open "//test_file", then that's what it is. >>> >>> -corey >>> >>> > >>> > Here is the code, but the open fails with "No such file or directory" >>> > >>> > // TEST File System >>> > char *test_string = "This is data"; >>> > int32_t fp; >>> > printf("FS Test: Writing:\n"); >>> > fp = red_open("/test_file", RED_O_CREAT | RED_O_WRONLY); >>> > if (fp != -1) { >>> > printf("Writing string\n"); >>> > int32_t numOfBytesWritten = red_write(fp, test_string, >>> > strlen(test_string)); >>> > if (numOfBytesWritten == strlen(test_string)) { >>> > printf("Success\n"); >>> > } else { >>> > printf("Write returned: %d\n",numOfBytesWritten); >>> > if (numOfBytesWritten == -1) >>> > printf("Unable to write to file: %s\n", >>> > red_strerror(red_errno)); >>> > } >>> > int32_t rc = red_close(fp); >>> > if (rc != 0) { >>> > printf("Unable to close file: %s\n", >>> red_strerror(red_errno)); >>> > } >>> > >>> > } else { >>> > printf("Unable to open file: %s\n", red_strerror(red_errno)); >>> > } >>> > >>> > Any thoughts? >>> > >>> > 73 >>> > Chris >>> > >>> > On Fri, Apr 7, 2023 at 5:10 PM Burns Fisher (AMSAT) via pacsat-dev < >>> > pacsat-dev(a)amsat.org> wrote: >>> > >>> > > >I assumed that since this was ARM it was little endian. >>> > > >>> > > Yeah, I would have too. But apparently ARM can go either way. >>> Turns out >>> > > that for some reason the automotive world seems to standardize on big >>> > > endian. This has caused nothing but hassle on the TMS570 (the >>> STM32L is >>> > > little). >>> > > >>> > > >>> > > ----------------------------------------------------------- >>> > > >>> > > 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 >>> >> >> ----------------------------------------------------------- >> >> 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 > > ----------------------------------------------------------- > > 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

Re: Filesystem code
by Chris Thompson 08 Apr '23

08 Apr '23

Burns, I think the initMRAM() is there. I merged your branch in. I see the function call in ConsolTask() right after the SPInit() calls for the MRAMs. But I also see a lot of MRAM errors at boot. Error 19s and Error 20s... Corey, I tried //test_file and that did not work either. 73 Chris On Sat, Apr 8, 2023 at 2:54 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Chris, I assume that you did add the "initMRAM" near boot (right after the > SPI init). If not, you may have to do format the file system after doing > it because it may have the size and the partition setup wrong otherwise. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Sat, Apr 8, 2023 at 2:39 PM Corey Minyard <minyard(a)acm.org> wrote: > >> On Sat, Apr 08, 2023 at 02:19:29PM -0400, Chris Thompson wrote: >> > I tried a simple example but I can't open a file. Is there a volume >> name >> > that I need to specify? I presume you don't need to create a directory. >> >> "/" should be the volume name, but maybe you need two of them? I wasn't >> sure from what the documentation said. >> >> If you can open "//test_file", then that's what it is. >> >> -corey >> >> > >> > Here is the code, but the open fails with "No such file or directory" >> > >> > // TEST File System >> > char *test_string = "This is data"; >> > int32_t fp; >> > printf("FS Test: Writing:\n"); >> > fp = red_open("/test_file", RED_O_CREAT | RED_O_WRONLY); >> > if (fp != -1) { >> > printf("Writing string\n"); >> > int32_t numOfBytesWritten = red_write(fp, test_string, >> > strlen(test_string)); >> > if (numOfBytesWritten == strlen(test_string)) { >> > printf("Success\n"); >> > } else { >> > printf("Write returned: %d\n",numOfBytesWritten); >> > if (numOfBytesWritten == -1) >> > printf("Unable to write to file: %s\n", >> > red_strerror(red_errno)); >> > } >> > int32_t rc = red_close(fp); >> > if (rc != 0) { >> > printf("Unable to close file: %s\n", >> red_strerror(red_errno)); >> > } >> > >> > } else { >> > printf("Unable to open file: %s\n", red_strerror(red_errno)); >> > } >> > >> > Any thoughts? >> > >> > 73 >> > Chris >> > >> > On Fri, Apr 7, 2023 at 5:10 PM Burns Fisher (AMSAT) via pacsat-dev < >> > pacsat-dev(a)amsat.org> wrote: >> > >> > > >I assumed that since this was ARM it was little endian. >> > > >> > > Yeah, I would have too. But apparently ARM can go either way. Turns >> out >> > > that for some reason the automotive world seems to standardize on big >> > > endian. This has caused nothing but hassle on the TMS570 (the STM32L >> is >> > > little). >> > > >> > > >> > > ----------------------------------------------------------- >> > > >> > > 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 >> > > ----------------------------------------------------------- > > 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

Re: Filesystem code
by Chris Thompson 08 Apr '23

08 Apr '23

I tried a simple example but I can't open a file. Is there a volume name that I need to specify? I presume you don't need to create a directory. Here is the code, but the open fails with "No such file or directory" // TEST File System char *test_string = "This is data"; int32_t fp; printf("FS Test: Writing:\n"); fp = red_open("/test_file", RED_O_CREAT | RED_O_WRONLY); if (fp != -1) { printf("Writing string\n"); int32_t numOfBytesWritten = red_write(fp, test_string, strlen(test_string)); if (numOfBytesWritten == strlen(test_string)) { printf("Success\n"); } else { printf("Write returned: %d\n",numOfBytesWritten); if (numOfBytesWritten == -1) printf("Unable to write to file: %s\n", red_strerror(red_errno)); } int32_t rc = red_close(fp); if (rc != 0) { printf("Unable to close file: %s\n", red_strerror(red_errno)); } } else { printf("Unable to open file: %s\n", red_strerror(red_errno)); } Any thoughts? 73 Chris On Fri, Apr 7, 2023 at 5:10 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > >I assumed that since this was ARM it was little endian. > > Yeah, I would have too. But apparently ARM can go either way. Turns out > that for some reason the automotive world seems to standardize on big > endian. This has caused nothing but hassle on the TMS570 (the STM32L is > little). > > > ----------------------------------------------------------- > > 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

3 2

Re: Filesystem code
by Burns Fisher (AMSAT) 07 Apr '23

07 Apr '23

Jonathan, did I send you the extra Launchpad that I ended up with? In any case, do you want to give one to Corey? Corey, you may have to solder on some .1" header pins for Jim's board to have all the required connections. I know the headers are DNP around the outside where they are not used, but I'm not sure that all the inside ones are there either. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, Apr 7, 2023 at 12:30 PM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I have the filesystem code mostly ready. I changed the configuration > to use 256 byte block. It's available in the filesystem branch. > > So I will need a launchpad and a board with MRAM. My address is: > > 7406 Wheatfield Rd, Garland, TX 75044 > > Chris, you can test it if you like, too. I haven't written any tests > for anything yet, that needs to be added. > > There is code to automatically mount the filesystem on startup and > format the filesystem if it detects corruption. > > There are three new console commands: mount fs, unmount fs, and format fs. > > The commands are the normal POSIX commands with "red_" prefixed, > red_open(), red_close(), read_read(), etc. > > I need to write a README about how this is all set up. > > -corey > > ----------------------------------------------------------- > > 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 >

2 3

Re: Filesystem code
by Burns Fisher (AMSAT) 07 Apr '23

07 Apr '23

Ok, the initial MRAM errors (and I think actually a fs error that did not show) came because initMRAM has to be called way early in main before any calls are made to readMRAM (since otherwise "numberOfMRAMs" has not been initialized so getPartitionOffset fails. After I did that the fs was not correctly formatted anymore and format fs took a bit longer than it did before. But now it all seems well. Again, that is pushed up to the repo as BFFileSystem. Feel free to merge. That's probably it for today 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, Apr 7, 2023 at 4:42 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Confirmed. I have it compiled and running here too. Corey has fixed the > path and endian issue in the Filesystem branch. > > Well done! > > I will see if I can write a file, but that will likely be tomorrow. > > 73 > Chris > > On Fri, Apr 7, 2023 at 4:31 PM Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Corey et al, >> >> I pulled down the filesystem branch and have gotten it running on my >> LaunchPad with 2 512K MRAMs. >> >> First, thanks for cleaning up the MRAM code. As you might have guessed, >> the read/write was originally to choose between the MRAM and Flash memory >> on the STM32L processor. On the RTIHU, I just cut out the stuff for the >> flash. Looks like you have used the same basic scheme between the two >> partitions in the MRAM. I like it! >> >> I have had to make two (identical) changes to get it to compile, and one >> more to get it to run: >> >> 1) I'm not entirely sure why the "reliance-edge" and its "core" >> subfolder were setup with different properties than everything else (that's >> the little key badge means, I think, although I've never been able to get >> rid of it once it was there!). But in any case, the changed setup had a >> path that was specific to your machine so it could not find <string.h>. I >> changed it to ${CG_TOOL_ROOT) in both places. Now it compiles. >> >> 2) Formatting the file system failed with a not-very-useful error message >> (Invalid Argument). The problem is that REDCONF_ENDIAN_BIG needs to be >> defined to 1 in redconf.h. >> >> So now it formats and mounts ok. I have not tried anything else. >> >> I'll push what I have right now up on my own branch named >> "BFFileSystem". Then I want to see why there are some MRAM errors when it >> first boots. Probably some old code. >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Fri, Apr 7, 2023 at 12:40 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> >> wrote: >> >>> Jonathan, did I send you the extra Launchpad that I ended up with? In >>> any case, do you want to give one to Corey? Corey, you may have to solder >>> on some .1" header pins for Jim's board to have all the required >>> connections. I know the headers are DNP around the outside where they are >>> not used, but I'm not sure that all the inside ones are there either. >>> >>> >>> >>> 73, >>> >>> Burns Fisher, WB1FJ >>> *AMSAT(R) Engineering -- Flight Software* >>> >>> >>> On Fri, Apr 7, 2023 at 12:30 PM Corey Minyard via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> I have the filesystem code mostly ready. I changed the configuration >>>> to use 256 byte block. It's available in the filesystem branch. >>>> >>>> So I will need a launchpad and a board with MRAM. My address is: >>>> >>>> 7406 Wheatfield Rd, Garland, TX 75044 >>>> >>>> Chris, you can test it if you like, too. I haven't written any tests >>>> for anything yet, that needs to be added. >>>> >>>> There is code to automatically mount the filesystem on startup and >>>> format the filesystem if it detects corruption. >>>> >>>> There are three new console commands: mount fs, unmount fs, and format >>>> fs. >>>> >>>> The commands are the normal POSIX commands with "red_" prefixed, >>>> red_open(), red_close(), read_read(), etc. >>>> >>>> I need to write a README about how this is all set up. >>>> >>>> -corey >>>> >>>> ----------------------------------------------------------- >>>> >>>> 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 >>>> >>> >> ----------------------------------------------------------- >> >> 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 > > ----------------------------------------------------------- > > 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 >

2 1

Re: Filesystem code
by Chris Thompson 07 Apr '23

07 Apr '23

Confirmed. I have it compiled and running here too. Corey has fixed the path and endian issue in the Filesystem branch. Well done! I will see if I can write a file, but that will likely be tomorrow. 73 Chris On Fri, Apr 7, 2023 at 4:31 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Corey et al, > > I pulled down the filesystem branch and have gotten it running on my > LaunchPad with 2 512K MRAMs. > > First, thanks for cleaning up the MRAM code. As you might have guessed, > the read/write was originally to choose between the MRAM and Flash memory > on the STM32L processor. On the RTIHU, I just cut out the stuff for the > flash. Looks like you have used the same basic scheme between the two > partitions in the MRAM. I like it! > > I have had to make two (identical) changes to get it to compile, and one > more to get it to run: > > 1) I'm not entirely sure why the "reliance-edge" and its "core" subfolder > were setup with different properties than everything else (that's the > little key badge means, I think, although I've never been able to get rid > of it once it was there!). But in any case, the changed setup had a path > that was specific to your machine so it could not find <string.h>. I > changed it to ${CG_TOOL_ROOT) in both places. Now it compiles. > > 2) Formatting the file system failed with a not-very-useful error message > (Invalid Argument). The problem is that REDCONF_ENDIAN_BIG needs to be > defined to 1 in redconf.h. > > So now it formats and mounts ok. I have not tried anything else. > > I'll push what I have right now up on my own branch named "BFFileSystem". > Then I want to see why there are some MRAM errors when it first boots. > Probably some old code. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Fri, Apr 7, 2023 at 12:40 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> > wrote: > >> Jonathan, did I send you the extra Launchpad that I ended up with? In >> any case, do you want to give one to Corey? Corey, you may have to solder >> on some .1" header pins for Jim's board to have all the required >> connections. I know the headers are DNP around the outside where they are >> not used, but I'm not sure that all the inside ones are there either. >> >> >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Fri, Apr 7, 2023 at 12:30 PM Corey Minyard via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> I have the filesystem code mostly ready. I changed the configuration >>> to use 256 byte block. It's available in the filesystem branch. >>> >>> So I will need a launchpad and a board with MRAM. My address is: >>> >>> 7406 Wheatfield Rd, Garland, TX 75044 >>> >>> Chris, you can test it if you like, too. I haven't written any tests >>> for anything yet, that needs to be added. >>> >>> There is code to automatically mount the filesystem on startup and >>> format the filesystem if it detects corruption. >>> >>> There are three new console commands: mount fs, unmount fs, and format >>> fs. >>> >>> The commands are the normal POSIX commands with "red_" prefixed, >>> red_open(), red_close(), read_read(), etc. >>> >>> I need to write a README about how this is all set up. >>> >>> -corey >>> >>> ----------------------------------------------------------- >>> >>> 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 >>> >> > ----------------------------------------------------------- > > 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