How to reset Bean+?

[IndyBob67]

Thanks for the update.

Race conditions can be a real bugger to find and worse to fix!

I don't have a lot of led activity in my set up. Just a Blink of the blue 5 times with a duration of 1 second to indicate setup complete.

When you do have the fix, will it fix existing dead/bricked Bean+'s?

[swstack]

Yes, we fully expect Bean+'s in the field to be recovered with this fix. The code is going through reviews now and we should have a new release out sometime tomorrow...of course I only incriminate myself by saying stuff like that

[IndyBob67]

@swstack

Incriminating yourself at lets us know if we can expect it in a small number of days, weeks or months.

Understand a bit my self but hate it when software companies wont even give a guess.

[swstack]

Hello Everyone!

New CLI Loader release w/ New Bean/Bean+ Firmware. I created a new pinned thread.

CLI Loader v0.5.2 + NEW Bean and Bean+ Firmware

Hi all, We have a new version of the CLI Loader available v0.5.2. This version includes the latest release of the Bean and Bean+ firmware v201609290000. Important: For those of you experiencing sketch upload failures, commonly referred to as "bricked" ... Please follow these steps: Update CLI Loader to 0.5.2 Program your Bean/Bean+ firmware using the program_firmware command. Power cycle Bean/Bean+ Use Bean like normal...should no longer fail to upload sketches. Release notes below: v…

@IndyBob67 @baglan @Matt_Ritchie @webxl

[tbm]

HI @IndyBob67,

Was this

2016-09-24T04:01:49.794Z INFO Sketch upload started!
2016-09-24T04:01:56.539Z ERROR Bean sketch upload error!
Sub state: 12
Blocks sent: 0
Bytes sent: 0
2016-09-24T04:01:56.590Z ERROR Bean sketch upload error!
Sub state: 12
Blocks sent: 0
Bytes sent: 0

ever resolved? I have a Bean+ exhibiting the same error with Sub state 12. No idea how to resolve, after following the reset protocol.

[IndyBob67]

@tbm Have you gotten the v0.5.2 version of the bean-sdk yet? It fixes this.

just

npm install -g bean-sdk

After that,
bean program_firmware -a myBeanAddress
Should get you back in the game.

[tbm]

@IndyBob67 indeed I have, and still stuck in sub-state 12. I'm guessing this Bean is now dead in the water.

[IndyBob67]

You did get the firmware updated didn't you? I know, dumb question...but I've done dumber things myself.

[tbm]

I definitely did, and the question's not dumb at all - gotta cover all bases at this point.

[baglan]

On the good news side, after the firmware update and scrapping all the old infrastructure (Arduino IDE and Bean Loader) and installing it all again AND switching to CLI loader, my Bean+ was reprogrammed successfully.

Thanks to the PunchThrough team for the update and good luck to people still having the issues.

[ha39000]

I seem to be in the same boat with my Bean+. I can connect still from the iOS LightBlue app, and the Bean Loader app always wants to update the firmware every time I try to upload a sketch from the app.

[tbm]

@ha39000 what are your results with the CLI, if you're able to try with that?

[ha39000]

2016-10-26T02:45:56.489Z INFO No longer scanning...
2016-10-26T02:45:56.491Z INFO State transition: null -> STATE_INACTIVE
2016-10-26T02:45:56.492Z INFO Beginning sketch upload of sketch: beanbean
2016-10-26T02:45:56.492Z INFO State transition: STATE_INACTIVE -> STATE_AWAIT_READY
2016-10-26T02:45:56.492Z INFO Sketch upload started!
2016-10-26T02:46:03.255Z ERROR Bean sketch upload error!
Sub state: 12
Blocks sent: 0
Bytes sent: 0
2016-10-26T02:46:03.257Z ERROR Bean sketch upload error!
Sub state: 12
Blocks sent: 0
Bytes sent: 0

[tbm]

@ha39000 that looks bad. Assuming you've performed the sacred rituals, including the timing hack (use --oops, and reset the bean right as you hit enter), your Bean is suffering from the same issue one of mine had. Contact PTD directly and see if they can arrange a replacement.

[PunchThrough]

Hello @ha3900,
Where you able to resolve this? If not, try updating your CLI loader and flashing the latest firmware. This newest firmware should resolve this issue.

Thanks.

[crigger]

I will try this over the weekend and let you know how it goes.

[PunchThrough]

Just released CLI Loader v0.6 minutes ago ... should contain the latest greatest firmware that will hopefully save the Bean. Program firmware using program_firmware command ... then try to program a new sketch via program_sketch ... also you can try the timing hack using the --oops argument described here:

https://punchthrough.com/bean/docs/guides/help/reprogram/

[crigger]

I have been trying to reprogram the bean but no matter what I do CLI hangs on connecting to bean.. I think this is due to the pairing pin issue (I set up a pairing pin on the bean and can't remember it an now have a bean I can't use).

I have tried using the --oops argument, updating the firmware, even just blinking the led and I get nowhere.

Here is a screenshot of my commands and the returns I got: https://cdn.pbrd.co/images/1fDabL7GN.png

You can see it just keeps freezing anytime it goes to connect to the bean. It sees it's there but cannot connect..

I was in contact with a member of the bean team who said he would see if he would replicate this and find a solution and if not they would ship out a new bean. That was on Nov 2nd. I have sent a number of emails since then and gotten no reply...

Any suggestions before I just count my loss on this?

[crigger]

WOW! I just heard back from someone on Hackster.io who keyed me into connecting the 3.3v to the * jumper on the board for a reset. This worked like a charm!!

More info here: http://beantalk.punchthrough.com/t/reset-bluetooth-pairing-pin/3921/2

[wuilbert]

I have read and tried your advice in this post. I have 4 Bean+ and one of them can not be found by CLI loader nor by the app. I don't know what sketch it had last. Suggestions?