/sd gone

[smhodge]

I now have 2 pyboard v1.1's that /sd has vanished from: rshell gives a "cannot access /sd" message and sure enough code that used to boot just fine from the /sd card no longer does (the code is still there if I look at it with a PC).

I can copy copy to /flash with rshell and it will boot and run just fine from /flash, just no longer from /sd. I have done a mass erase and reloaded the firmware (1.12) but that did not solve the issue. Nor does using another, newly-formatted card.

It is possible this happened with a hardware power glitch on the motherboard the pyboard is mounted on. That said, is there a way to resurrect the /sd card access on the pyboard?

[pythoncoder]

What happens if you issue the following at the REPL:

Code: Select all

import os
os.listdir('/')  # should see ['flash', 'sd']
os.listdir('/sd')  # should produce a list of files on the SD card

If you don't get this result, and the SD card can be read and written when used on a PC, I would suspect a hardware issue.

[smhodge]

I only get 'flash' listed.

So by hardware issue do you mean (a) specifically with respect to the /sd card and (b) unfixable except by replacing the entire pyboard?

Thanks

[pythoncoder]

In six years' regular use of multiple Pyboards I've never seen that happen - if it's happened to two boards it's beyond coincidence. Something must be causing this.

The boards clearly aren't recognising the presence of the SD card. Aside from damaged or dirty SD connector contacts I suspect the Pyboards have been electrically damaged in some way. With electronic testgear the fault could doubtless be found, but in the absence of the necessary kit (and skills) replacing the boards is your only recourse.

[T-Wilko]

I now have 2 pyboard v1.1's that /sd has vanished from: rshell gives a "cannot access /sd" message and sure enough code that used to boot just fine from the /sd card no longer does (the code is still there if I look at it with a PC).

Perhaps best to post your code for mounting the sd here. May also be that you're using outdated code examples for mounting an sd to a pyboard, as there are plenty of dud examples floating about. (just encountered one myself with mounting an sd to a pyboard d-series, official docs code too)

[smhodge]

It happens whether using the rshell utility by dhylands or by simply having the code, including boot.py, on the sd card (which is known to work fine on other pyboards).

I'm pretty convinced it is a hardware issue. I recently modified my motherboard slightly and had it refabricated, and it's with 2 of these new refabricated boards that it happened. The prior versions of the motherboards worked just fine. Maybe the fabricator screwed up somehow, even though I thoroughly prechecked them for shorts, etc.

I've been over the modifications countless times and can't see how they would cause such catastrophic damage. Briefly, on one board, before total meltdown (so to speak) the 3V3 regulator on the pyboard was putting out 3.8 V.

At any rate, I've declared them to be demon boards and am doing a major redesign from scratch and having them refabricated.