You are reading a single comment by @Gordon and its replies. Click here to read the full conversation.
  • The crc32 warnings shouldn't be a problem - unfortunately it looks like the actual error message never got printed, but most likely it was a Bluetooth-related error. What type of computer are you using (Mac/PC/etc)?

    Did this just happen once, or have you tried it multiple times and you get the same error each time? Even though the Puck isn't working now, the upload process won't touch the bootloader, so it isn't 'bricked' - a successful flash will fix everything.

    When you start the Puck up holding the button down, does the green LED light up brightly, or is it reasonably dim? This sort of error could just be down to having a flat battery.

    While you say it's new Puck, very occasionally it seems the batteries do have issues - or if you started the Puck up, ran some code that used a lot of power and then left it overnight, that could have flattened it quickly as well.

    If you have an Android or Apple phone, maybe you could try using the NRF Connect app instead? http://www.espruino.com/Puck.js#firmware­-updates

    While the IDE version is definitely more convenient, the NRF Connect app is a very tried and tested method that I think most people use.

About

Avatar for Gordon @Gordon started