Forum > Windows

SD card low level read

<< < (4/5) > >>


--- Quote from: PascalDragon on June 21, 2022, 09:29:43 am ---Perhaps after initializing the SD card is stuck in SPI mode and can't be brought back into SD mode (though judging from the SD card spec the card should allow this with each power up sequence).


Again, it does not matter if the SD card is formatted with FAT or not. If the whole disk is not available in disk management then something else went wrong.

--- End quote ---

I've not seen a device get "stuck" like that, but there's always the possibility that it could be forced if the embedded RISCOS wrote something to one of the engineering/configuration pages.

Noting I think the most likely thing is that RISCOS has wiped the partition and initialised a single (SDFS?) filesystem, in which case there's a real possibility that either an external (USB-connected?) interface box refuses to recognise it ** or that the OS (or more specifically, a desktop environment) won't attempt to auto-mount it without manual intervention. In any event, if OP isn't going to tell us what he's doing then he's the one that's stuck.

** That might sound improbable, but SD-Cards are now a subsystem in their own right with their own engineering tradition: e.g. preferred partitioning and filesystem layout to put the FAT onto more-robust storage than is used for the data area. Taking that sort of thing into account, even though I've not seen an interface box present a card as other than a linear sector image (at least to the standard storage APIs, it's entirely reasonable that something of comparatively recent manufacture could get confused if its attempt at clever device management were stymied by a non-standard layout (i.e. no partition table etc.).



--- Quote from: MarkMLl on June 20, 2022, 11:25:14 am ---Does the /device/ appear as e.g. /dev/sdb when plugged in? Note that I'm not talking about the /filesystem/ here, or about individual /files/ on the filesystem.

--- End quote ---

Sorry, been busy for a few days with work.

I'm not using Linux, but I need to support it. I've only heard rumours that there is a RISC OS driver for Linux (or, more specifically, ADFS).

Under macOS, a RPi bootable RPi card (and disc image) has a FAT16 partition which macOS can mount. But, the RISC OS partition appears red and unmountable. Looking at the hex dump of the image I can see the RISC OS partition, as expected (in fact, it appears to be interleaved with the FAT16 partition). So I just need to be able to access an SD card in the same way as an image file.

I'm going to fire up my RPi next, booting into RISC OS, and format an SD card as ADFS, then see what macOS makes of it.

Note that the OP, although it sounds like he has the same issue as myself, is not trying to access a RISC OS partition.

Just did a quick Internet search for "ADFS driver for Linux" and found that you can, or at least you could, read ADFS (RISC OS) images under Linux natively, but only as read-only. However, I don't know Linux well and only have it installed inside a VirtualBox for compiling Lazarus projects (which I can now do in macOS without bothering to fire up Linux).

Assume that the number of people who know RISCOS here is minimal, and that it is at best only peripherally relevant since you're not being asked to produce a program to run on it.

Get yourself a spare PC, stick e.g. Ubuntu on it- NOT in a VM- and then by and large we'll be able to talk you through enough to work out roughly what's going on.


I've had another look at found this, which should do the job for what I'm after:
But only appears to be for Windows. I also need to work out how to get a list of all devices and partitions. Again, there is a post that shows that, but, again, only for Windows (32 bit), although there is talk of using Linux - guess I could do trial and error and enumerate the disc number and partition number until it errors out.


[0] Message Index

[#] Next page

[*] Previous page

Go to full version