Bricked it! (What next?)



  • So, I was playing around with my first app, and as happens sometimes, I messed up somewhere. My device is now non-responsive.

    Ok, no problem, right? This thing's got to have a reset button somewhere. Oh, there it is! And there are the instructions on how to reset it back to the bootloader.

    But, I have followed the instructions 6 or more times now, and the device is still - for all intents and purposes - dead.

    I even peeled off the back of the case just to make sure I was really depressing the reset switch. No love.

    Occasionally, tantalizingly, monoprog detects it as available and running an app:

    Mono device running app detected.
    

    but then I can't successfully make install:

    Resetting Mono device to start bootloader
    Programming Mono device with hallowelt.elf...........
    Mono device not detected on USB ports.
    No connection to Mono device.
    make: *** [install] Error 2
    

    Worse, after another attempted reset, monoprog goes back to not seeing the device at all.

    Thoughts?

    Thanks!



  • Are doing normals resets (just pressing the reset button), or are you resetting-to-bootloader?

    You reset-to-bootloader by holding the user switch and toggling the reset button. See: http://developer.openmono.com/en/latest/tutorials/resetting_mono.html#force-load-bootloader

    I hope this does the trick for you.



  • @stoffera tried both; results per my original note above. I'm guessing I need to worry.



  • @pktm you should not worry. You cannot brick mono with software. The bootloader is protected from modification by the memory configuration. Whenever you reset Mono the bootloader will run.

    Set Mono into bootloader and check the USB connection. On Windows use Device Manager to see if Mono is present. On Mac open Spotlight (the search tool) and open the app System Profiler, see the USB section in left column. Mono identifies itself as PSoC3 Bootloader.

    If no PSoC3 Bootloader appears, check that your USB cable is working and can provide power. If you indeed see the device, try to detect it with monoprog:

    $ monomake monoprog -d
    


  • @stoffera It's not showing up in System Profiler, nor via monomake monoprog -d.

    What can I try next, please?

    Thanks!



  • @stoffera So I really did brick it then?


  • administrators

    @pktm @stoffera (our mac specialist) is on holiday, he will be back late next week.



  • Couple of ideas. My mono identifies itself as "mono serial port" in the USB configuration, no PSoC3. Also, I usually need to "make install" or "monomake monoprog -p" a couple of times before it recognises the device, until that happens I get the same error as you (Mono device not detected on USB ports, No connection to Mono device.) - so have you tried just issuing the command a few times?

    -- maz



  • @maz Yep, sure have. But, I'll try again tomorrow and report back.



  • Exact same thing has happened to me. I disappointed that there isn't a reply to follow-up with this.

    To clarify, I've tried the recommended sequence to put the mono into bootloader mode without success - all I get is blank dark screen.



  • Just an update, I was able to download code to the unit. Turns out it did go into bootloader mode (it's just that there's no indication of that on the LCD, so I didn't know). As well, I bet that many times I was trying the unit had timed out and gone to sleep - this too probably prevented me from detecting the unit.



  • @rhofer said in Bricked it! (What next?):

    Just an update, I was able to download code to the unit. Turns out it did go into bootloader mode (it's just that there's no indication of that on the LCD, so I didn't know). As well, I bet that many times I was trying the unit had timed out and gone to sleep - this too probably prevented me from detecting the unit.

    What operating system you are using? On Debian I have a serious bug that if Mono is connected to computer for few minutes total, Debian runs out of /dev/ttyACM## devices and then Mono can't be detected anymore until computer is restarted (original thread)



  • @rhofer I am glad you were able to resolve the issue. I get that it is not visible to the naked eye, that mono is in bootloader. We wanted to keep the bootloader as small as possible, taking up a minimal amount of flash memory. Therefore it does not talk to the display or any other peripheral. It presents itself as a HID on the USB port.

    @malaire I have found the source of the issue on Debian, it the modem manager service that keeps resetting Mono by pulling the DTR low on all serial devices. I will post an more informative reply, in your original post.


Log in to reply