New build seems to have killed my Pyboard (now fixed)

The official pyboard running MicroPython.
This is the reference design and main target board for MicroPython.
You can buy one at the store.
Target audience: Users with a pyboard.
User avatar
dhylands
Posts: 3821
Joined: Mon Jan 06, 2014 6:08 pm
Location: Peachland, BC, Canada
Contact:

Re: New build seems to have killed my Pyboard (now fixed)

Post by dhylands » Wed Feb 03, 2016 5:27 pm

Other things to try would be to reinitialize the filesystem (hold USR button during boot - release when green and yellow LEDs are both on).

And reflashing new firmware.

User avatar
pythoncoder
Posts: 5956
Joined: Fri Jul 18, 2014 8:01 am
Location: UK
Contact:

Re: New build seems to have killed my Pyboard (now fixed)

Post by pythoncoder » Thu Feb 04, 2016 9:01 am

Thanks to a suggestion from another Linux expert it emerged that I'd become removed from the dialout group. This now seems to be fixed: I've flashed two pyboards from this laptop and can talk to both of them via rshell. I've no idea how this occurred.
Peter Hinch
Index to my micropython libraries.

User avatar
dhylands
Posts: 3821
Joined: Mon Jan 06, 2014 6:08 pm
Location: Peachland, BC, Canada
Contact:

Re: New build seems to have killed my Pyboard (now fixed)

Post by dhylands » Thu Feb 04, 2016 5:40 pm

I'll make a todo item to add better permissions reporting into pyboard.py and/or rshell

Iyassou
Posts: 42
Joined: Sun Jun 26, 2016 9:15 am

Re: New build seems to have killed my Pyboard (now fixed)

Post by Iyassou » Fri Jul 22, 2016 1:33 pm

I was having the same problem when I tried to update my Pyboard: the red, orange and blue LEDs were faintly lit and it was unresponsive.
Turns out I download firmware for the Pyboard and not the PYBLITE, the PYBLITE being the one I own :lol:
Thankfully I had made a backup of my previous firmware: I restored it, downloaded the correct firmware and the update went as smooth as butter.

Post Reply