MicroPython Forum (Archive)

I think i've tinkerd a bit too much :-]
I had a script that reads out a DHT22 temperature sensor and sends it to a website. That worked fine for some time.
But the wipy stopped to read out the sensor. (the wipy was running wireless and attached to a lipo battery via the expansion board, most of the time the wipy in sleep modus).
I've wanted to see what was going on and attached it to the usb.
I've tried to ad some extra debug code, but after a reboot the heart beat led stays on.
I've tried to reinstall the os, booting in debug mode. But this does not help.
via uart I can see it is ready, but there is no prompt. in ftp I have access, but can't get to /flash
Could my beloved wipy have died?

André

Hi,

could it be that you by mistake attached the Wipy 180deg. turned to the expansion port?
This is a known problem. It basically kills part of the wipy board since it feeds 5V to only 3.3V tolerant pins.
So what you get is a wipy which always boots into safe-mode and can't be told to boot into normal mode anymore.
There is a way to overcome the now dead pins. But afaik, it requires a programmer and modification of the code.

No, the board was never the wrong way in the expansion board, the wipy is in the expansion board for a long time now and has never left the board. The error started after I tried to load new code on the board.
The code was basicly the same as the one who was running for weeks, but with extra print statements for debugging. No changes to pins.

Hi andrethemac,

Can you try booting in safe boot mode? That should at least get you a working REPL and FTP server...

Cheers,
Daniel

Hi Dani
I've tried that.
I let the unit boot into stage 3 of the safeboot (the factory settings).
I can log in but with ftp I get an 550 error when trying to cd to /flash
with telnet repl I don't get a prompt.
even tried to reinstall the mcuimg.bin (couple of times) but it does not help.
tia
André

My WiPy has got into the same state. It behaves in this way in any of the safe boot modes (including factory boot):

* heartbeat LED goes to always-on about 3 or 4 seconds after removing the pullup on pin 28.
* WiPy responds to ping.
* Telnet reports successful login, but no Python prompt appears.
* FTP succeeds, but cannot cd /flash.

In FTP, ls responds with

227 (192,168,177,1,7,232)
150
drw-rw-r-- 1 root root 0 Jan 1 00:00 flash
226

Just before this happened, we had been running an application that did a lot of file writes to a file in /flash. We then updated some of our application python files. Could this have corrupted something in the filesystem or in the system flash so badly that the WiPy cannot boot normally?

The WiPy had WiPy v1.2.0. Previously we had used WiPy v1.1.1

Stephen Irons

[quote="andrethemac"]Hi Dani
I've tried that.
I let the unit boot into stage 3 of the safeboot (the factory settings).
I can log in but with ftp I get an 550 error when trying to cd to /flash
with telnet repl I don't get a prompt.
even tried to reinstall the mcuimg.bin (couple of times) but it does not help.
tia
André[/quote]

Hi,

I ran into the same issue / same behavior as described by Stephen. WiPy seams not to be able to access the flash from FTP, REPL is dead etc.

Also before the WiPi bricked itself, I was running a script which was writing data to flash.

So the question is: is my WiPy dead for ever or is there a chance to make it recover from this issue (without JTAG, since I don't have one for that MCU).

Regards,
Stefan