Ok. And I confirmed that the two that a former volunteer gave me back are HERE. I did not give them to you.
73,
Burns Fisher, WB1FJ
AMSAT(R) Engineering -- Flight Software
On Fri, Apr 7, 2023 at 2:21 PM Jonathan Brandenburg via pacsat-dev <pacsat-dev@amsat.org> wrote:
I have confirmed I have it... Now, how
to best get it to Corey... I can ship it from Addison post office,
I can get it to Bill soon (if Corey is going to see Bill at a club
meeting or something), or Corey can pick it up in Addison.
Thoughts?
Jonathan
On 4/7/2023 11:41 AM, Burns Fisher
(AMSAT) via pacsat-dev 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@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.