New firmware 0.9.6.b1 and Pymakr v1.0.0.b7 released + new complete docs

  • I have the same issue - new firmare and new Pymakr :

    Pycom console:
    Connecting to a Pycom device...
    Error while communicating with the Pycom device! (click to attempt to reconnect)
    Connecting to a Pycom device...

  • @livius, @AgriKinetics, I confirm the report. I bricked a LoPy using Windows. Thanks for the report. In the meantime you can downgrade to previous version if needed

    Edit: fixed, see note on initial post of this thread

  • @abilio Windows 7, standard update method, G23 to GND, USB - cannot do a safe boot now either.

  • @livius, can you tell me which OS are you using?

  • @abilio
    by updater tool and wire between GND and G23
    2 WiPy2
    one on expansion board second by UART/USB converter

    P.S. one have green RGB led solid
    second nothing on RGB led
    WiPy without Expansion board is clear - without any my code
    only upgraded previously to 9.5 and now to 9.6

  • @AgriKinetics, @livius, can I ask what upgrade method did you use?

  • The same as @livius my two LoPy hang completely after a successful update of the 0.9.6.b1 firmware. Sometimes on reboot I get a solid Blue light from the heartbeat LED.

    I have tried the safe boot (G28 and 3.3v) but, never get the orange flashing light. So now the LOPy is useless and I can't do anything at all. Pymakr says .."connected" then fails immediately.

    Not sure where to go from here, but, another week another fail!

  • after "succesfull" update WiPy2.0
    all my WiPy2 hang totally at start
    tested on two WiPy2.0 one on Expansion board second without

    ets Jun  8 2016 00:22:57
    rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
    ets Jun  8 2016 00:22:57
    rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
    configsip: 0, SPIWP:0x00
    mode:QIO, clock div:2
    ho 0 tail 12 room 4
    entry 0x4009f1f0

    above never end

Log in to reply

Pycom on Twitter