Change MicroPython version for Calliope mini 3 to the current one.

[joernalraun]

The current used MicroPython version does not support the standard way to start BLE mode (triple reset) on Calliope mini 3.
If you update to the current version it will work:
(https://github.com/calliope-edu/micropython-calliope-mini-v3/tree/oct24-mini3)

[joernalraun]

I just bump this as people are flooding support because of this issue and it should be quick to implement...

[Cruiser79]

Hello @joernalraun

is this the same as this PR on the other repo OpenRoberta/ora-cc-rsc#15 ?
Than i am also interested in this fix.

[joernalraun]

This is the same Hex-file, yes! However, the link in this comment is pointing to the generated file from Calliope, the PR has the file already integrated in the lab (so even less work to do)... If you are one of the few how was able to host this on your own machine, you just can switch the Hex-file or merge this change to your current working branch. Please tell me, if there are any issues with it (though it should work well, as this is running for a while at python.calliope.cc).

[rbudde]

btw: we have wo different hex-binaries for the v3 in the ora-cc-rsc repo:

1. one in directory firmware (this is for the "factory reset" command
2. one in directory runtimeHex (this is the basis to put your program into)
   I'll prepare a commit that will change both to the new version today. I'll deploy this on one of out test servers, so it can be tested by everyone. I'll write a comment which I've taken later. Stay tuned :-)

[Cruiser79]

@rbudde nice to hear about that. Can you tell me, how an uninformed user like me can reach this test servers :-)

[rbudde]

@joernalraun I took your hex-file and put it into the directory runtimeHex. Then I downloaded a copy of the predefined program ("factory reset") into directory firmware.

I deployed this on dev3

• the v3 works as expected with usb from my laptop using chrome
• using the calliope mini app on my Android tablet and setting the editor to dev3
  • pairing works
  • uploading works
  • the program runs, BUT
  • when uploading the next time the pairing has to be repeated (then it works again)
  • resetting the v3 to factory default works (with bluetooth)
  • then the next program can be uploaded (i.e. the pairing is not lost in this case)
  • but then the pairing is lost and must be done again

There must be a difference i the pairing logic between the predefined program ("factory reset") and the hex-file to which the user program is attached to. Or?

I have no IOS device. @AHberta or @BeateJ can you test the v3 with your IOS devices with dev3?

@Cruiser79 all out test systems are public, but of course should be used for testing mainly :-):

• https://test.open-roberta.org/ is our nighly build

• https://dev.open-roberta.org/ is our snapshot system (updated after every commit to develop)

• https://dev3.open-roberta.org/ got our changes w.r.t. the Calliope V3

[joernalraun]

@rbudde great!
The behavior seems to be correct, since as of now radio and Bluetooth communication can't run in parallel on MicroPython and radio is always active, so you will need to manually wake up the Bluetooth communication by hitting 3x reset. The pairing has to be done only once, but the mode to wait for data has to be initiated. The factory program is no MicroPython program, so this works without the need to initiate the Bluetooth state (same in MakeCode etc.).