New user images?
-
Would it be possible to have the build process (build for release) used for V2 and V3 firmware, and DWC always produce a V2 and V3 stand alone card image? In a consistent place?
"What goes on the card", or fixing cards, or similar, is a VERY common question. Sure would be nice to point people to "Format a card and put the entire content at this link on it".
-
its described in the documentation
https://duet3d.dozuki.com/Wiki/Firmware_Overview#Section_SD_card_structure
-
Described, yes. Imaged or zipped, no.
Remote (forum) supporting someone completely rebuilding a card is vastly different that having them unzip a single file onto a fresh card, and then put the output of the RRF configurator on it.
-
@Danal said in New user images?:
Described, yes. Imaged or zipped, no.
yes its linked there to
https://github.com/T3P3/Duet/blob/master/Duet2/SD Card Contents/SD_Card_Contents.zip -
AHA!!! You only have to hit me upside the head with a 2x4 a couple of times to get my attention.
THANK YOU!!!!
-
@Danal do you know if anyone tried putting the standalone config and dwc files for Duet3 onto the /boot partition of a RPI image and see if it is accepted by the Duet3 in standalone mode? (I would try but don't have a Duet3 with sd card socket). That would allow one unified image for Duet3 at least.
btw the zipped file above is outdated with DWC1 among other things.
-
@bearer said in New user images?:
@Danal do you know if anyone tried putting the standalone config and dwc files for Duet3 onto the /boot partition of a RPI image and see if it is accepted by the Duet3 in standalone mode? (I would try but don't have a Duet3 with sd card socket). That would allow one unified image for Duet3 at least.
btw the zipped file above is outdated with DWC1 among other things.
Yes, and it does work. The Stand Alone board doesn't care about other files, and/or other partitions.
Therefore, it is possible to have a "universal" card.
-
Interesting, hopefully Duet3d will pick up on that to avoid more situations like that other thread..
-
@bearer said in New user images?:
btw the zipped file above is outdated with DWC1 among other things.
And that's why I'd like a simple triggered script whenever firmware or DWC is built for "prod". And I do mean either... most recent one run wins... and pulls in the other ones "latest", etc.
It would make that other thread much simpler.
-
Fingers crossed for something like that being a fortunate side effect of putting all things duet under the new duet3d github
-
(On the other hand, selecting firmware and dwc as other files in the reprap configurator provides the correct links ans clear enough instructions, there will always be one or two that falls through the cracks)
-
Seems windows' urge to suggest formatting the linux partition can be an issue with using the same sd card for both stand alone and raspberry pi operation.
Might have a play with different partition types to see if that is avoidable or if its feasible to just remove the second parition from the partition table and recreate it on first boot if needed. (obviously it'd be better to tell windows to f¤"!% off and leave well enough alone, but..)
edit:
Changing the partition type to0(empty) seems to prevent windows from trying to display, mount and format the partition while allowing grub to boot linux based of the UUID of the ext4 partition as well as retain the device node.label: dos label-id: 0xfb28cfac device: /dev/mmcblk0 unit: sectors /dev/mmcblk0p1 : start= 8192, size= 524289, type=c /dev/mmcblk0p2 : start= 540672, size= 30575616, type=0
