- pacsat-dev - mailman.amsat.org

Re: Filesystem code
by Jonathan Brandenburg 08 Apr '23

08 Apr '23

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(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/pacsat-dev@amsat.org > 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 athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org -- Jonathan Brandenburg, KF5IDY

1 0

Re: Filesystem code
by Jonathan Brandenburg (KF5IDY) 08 Apr '23

08 Apr '23

I don’t quite remember what my stock looks like but happy to allocate another to PACSAT. Jonathan Sent from my iPhone On Apr 7, 2023, at 11:41 AM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org> 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<mailto: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. -corey ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto: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(a)amsat.org<mailto: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(a)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(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

Well done Corey. I will see if I can get it to compile here and try to flash the chip. 73 Chris 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/pacsat-dev@amsat.org > 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

Filesystem code
by Corey Minyard 08 Apr '23

08 Apr '23

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

1 1

Re: Test
by Jim McCullers 08 Apr '23

08 Apr '23

GOT IT! 73 Jim This is sent from my gmail account. Can someone respond if they get this? -corey ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Test
by Chris Thompson 08 Apr '23

08 Apr '23

Received! 73 Chris On Fri, Apr 7, 2023 at 12:09 PM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > This is sent from my gmail account. > > Can someone respond if they get this? > > -corey > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(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

Test
by Corey Minyard 08 Apr '23

08 Apr '23

This is sent from my gmail account. Can someone respond if they get this? -corey

1 0

Re: PC-104 "Standard"
by Bob Stricklin 07 Apr '23

07 Apr '23

Jonathan, Thanks for your email on this topic. These connectors mainly eat up a lot of board space. Reducing the pin count to something more realistic should befit all. Every pin you have in a connector is a potential reliability issue. Reliability in the actual connection interface and in the increase of complexity of the electrical design. Each pin with routed signals requires more effort to rout signals on the PCB. These connectors are adding mass to one side of the CubeSat moving the center of gravity. This will effect the orbital dynamics and stabilization systems. Some AMSAT designs use multiple bus systems, RS232, I2C, CAN, IO signals. These busses require different interface chips, power voltages, power consumption, firmware, and user knowledge. Reducing to a single communication bus system would reduce pin count, chip count, power needs and improve reliability. The connector systems marketed are not all equal. If a 104 pin standard is used then there should also be a specification for which connector are to be used. This will define the pin size, plating layers - nickel gold, socket sizes and pin hardness. I suggest using the pin size that is soldered in place. If the press pin socket pins/holes are used then they should be soldered after assembly. During prototype and production of flight hardware these connectors are difficult to work with. Each board/connector will have to be disassembly and reassembly many times. We need Battery voltage, and an I2C (2 pins) possibly a signal ground, and possible a hard reset signal. Bob > On Apr 7, 2023, at 9:26 AM, Jonathan Brandenburg via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Following up on last night's conversation... > > When there is talk about CubeSats using the PC-104 standard, what that really means is the use of the PC-104 form factor in terms of board size, mounting hole placement, and the 2x2x26 connector. CubeSats don't adhere to any of the signalling or protocol aspects of PC-104 standards (including additional connectors defined in the PC-104 standard). > > There hasn't been any standards body define this form factor for Cubesats (as far as I know) so I imagine it just sort of grew organically from the first university satellites looking around for something to copy and noticed the small form-factor computer. > > As correctly noted, CubeSats don't standardize the use of the pins in the PC-104 connector but it seems like component manufacturers looked around to see how others had been using pins and followed suit. Thus if PACSAT is using I2C, power, and ground pins there will be little conflict. What I've seen is CubeSat component manufacturers offer an option sheet that allows the customer to select from a set of options. Along the lines of "put I2C pins here or there or do not connect" kind of options. > > I hear the comments about how "This a large connector!" and "How many pins are really needed?" and "How are they used by different components?" All that is true. At same time it's also true that if somebody is adding a component to their CubeSat it will most likely expecting boards with the PC-104 form factor. AMSAT is an exception but even then we had to partially adapt our boards to the PC-104 form factor for use by non-AMSAT organizations. > > When I'm at CubeSat Developers Workshop later this month, I'll do a survey. While I will see at least one university eschew the PC-104 form factor (because they're developing ALL the components in-house and prefer a plug-in-slot configuration because it simplifies assembly a lot) I expect most will have purchased the bus (including structure, C&DH, EPS, and any ADCS) which will be in the PC-104 form factor. But I could be surprised and the tide may be turning. > > Comments? > > Jonathan > > -- > Jonathan Brandenburg, KF5IDY > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq… > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…

1 0

Re: PC-104 "Standard"
by Jonathan Brandenburg 07 Apr '23

07 Apr '23

On 4/7/2023 9:45 AM, Burns Fisher (AMSAT) via pacsat-dev wrote: > I'd be interested if those who use PC104 actually use them throughout > the satellite (i.e. they use them like Fox/Golf uses the QxN > connectors where most of the signals pass through). Also what board > spacing where these connectors are used if there is anything typical. > (I think Eric said there were choices for the PC-104 connectors). I'll include these questions in my survey... it would be interesting to know the prevalence of ribbon cables for sure. Jonathan -- Jonathan Brandenburg, KF5IDY

1 0

Re: PC-104 "Standard"
by Burns Fisher (AMSAT) 07 Apr '23

07 Apr '23

I'd be interested if those who use PC104 actually use them throughout the satellite (i.e. they use them like Fox/Golf uses the QxN connectors where most of the signals pass through). Also what board spacing where these connectors are used if there is anything typical. (I think Eric said there were choices for the PC-104 connectors). 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, Apr 7, 2023 at 10:26 AM Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Following up on last night's conversation... > > When there is talk about CubeSats using the PC-104 standard, what that > really means is the use of the PC-104 form factor in terms of board > size, mounting hole placement, and the 2x2x26 connector. CubeSats don't > adhere to any of the signalling or protocol aspects of PC-104 standards > (including additional connectors defined in the PC-104 standard). > > There hasn't been any standards body define this form factor for > Cubesats (as far as I know) so I imagine it just sort of grew > organically from the first university satellites looking around for > something to copy and noticed the small form-factor computer. > > As correctly noted, CubeSats don't standardize the use of the pins in > the PC-104 connector but it seems like component manufacturers looked > around to see how others had been using pins and followed suit. Thus if > PACSAT is using I2C, power, and ground pins there will be little > conflict. What I've seen is CubeSat component manufacturers offer an > option sheet that allows the customer to select from a set of options. > Along the lines of "put I2C pins here or there or do not connect" kind > of options. > > I hear the comments about how "This a large connector!" and "How many > pins are really needed?" and "How are they used by different > components?" All that is true. At same time it's also true that if > somebody is adding a component to their CubeSat it will most likely > expecting boards with the PC-104 form factor. AMSAT is an exception but > even then we had to partially adapt our boards to the PC-104 form factor > for use by non-AMSAT organizations. > > When I'm at CubeSat Developers Workshop later this month, I'll do a > survey. While I will see at least one university eschew the PC-104 form > factor (because they're developing ALL the components in-house and > prefer a plug-in-slot configuration because it simplifies assembly a > lot) I expect most will have purchased the bus (including structure, > C&DH, EPS, and any ADCS) which will be in the PC-104 form factor. But I > could be surprised and the tide may be turning. > > Comments? > > Jonathan > > -- > Jonathan Brandenburg, KF5IDY > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0