Post
Topic
Board Group buys
Re: [CLOSED] Bitmine CoinCraft A1 28nm chip distribution / DIY support
by
silver71
on 28/02/2014, 14:58:13 UTC
The base files for building the OpenEmbedded/Yocto-based rpi image will also be committed soon so that everybody willing to develop forks based on it is very welcome to do so (and share back)  Smiley
Is there any possibility for SD-card to be accessible from the front/back, in case change/new yacto-image or improvements are to be deployed, so that rig/desk can remain hashing with old SD-image and new-one is prepared offline, and just cards swapped and rig/desk restarted. I think this will improve overall reliability of the machines and make rigs/desks ready for future improvements and it also saves time, in case SD-card is damaged.

Stuff like this might be very handy, and will not violate warranty in case of SD-card malfunction. Blockchain file will grow more and more in the future, so one day, user might need to insert biger SD-card, and if it's unaccessable from the outside, it might make problems.

a) what is the advantage of having a secondary SD card slot over flashing the new FW image to your miner's primary SD card once you are done creating it?
b) the SD-card is almost read-only, i.e. only configuration changes are written, everything else goes into memory mapped temp file systems - with that, risk of wearing out the SD card is minimal
c) the FW image is tiny (like 30-50MB) and won't grow significantly in the future; the blockchain is not stored on the SD (for what?), so the smallest SD-card available is still orders of magnitude too big for the FW - we won't run into space issues

Extension was not intented to be used as 2ns SDcard, but as primary, just accessible from chasis, just because nobody knows what will happen in 12-18 months...so why not if that's not too complicated ?