MicroPython Forum (Archive)

I have a pyboard that the SD part of it is toast, I think. Not the card itself but probably the driver or reader or something. At any rate I decided to check it out again so I did a full (not quick) format of a 16GB card and a mass erase/firmware re-install (v1.12 on a v1.1 pyboard) and then opened ...

I just did some more tests. I does not matter if I use close() or not, or if I use mode='a+b', 'w+b' or 'r+b'. In all cases it finds the file on /flash just fine but it opens it with a file length of 0 and thus new writes to it over-write the old contents. BUT, in all cases, the same code lines work...

I don't have a problem writing the data. If I let my code run after it has opened the now new file it writes new data just fine. The problem is I can't get to first base with the "open append" function: it just trashes the old existing file and starts a new one. BUT if i run the same code in the REP...

I am trying to open an existing file stored on /flash for appending & reading. It is a binary data file created with a prior run of my code. I can do it just fine from the REPL with the following code: --------------------------- filePath = '/flash/cos.log' file = open(filePath,'a+b') from uos impor...

I tried 2, 16 and 32 GB cards, all formatted FAT. They all work in other pyboards.

Is it robust enough to survive inserting after the board is powered on, even though it might not work until it's done properly?

Brand-new, out-of-the-box, pyboard v1.1. Connected to it with rshell to see if it was alive and well. It was except, once again, no /sd. Unlike round 1 (months ago) no code had been loaded onto it. The rshell message is the same: "cannot access /sd". I tried full erase & reloading firmware (and upgr...

Ah, got it! Thanks

I an using an external USR switch connected to X17. On an early version of my motherboard I simply put another circuit in parallel with the one on the pyboard v1.1 schematic, complete with 4.7K resistor in series. I could use both the pyboard USR switch and the external switch to trigger the callbac...

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 o...

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