Actions
Forum Thread Details
  • State Verified Answer
  • Replies 15 replies
  • Answers 4 answers
  • Subscribers 18 subscribers
  • Views 1887 views
  • Users 0 members are here
Related

Bluetooth basic problem with the micro:bit

neilk

I've recently received my micro:bit and worked through most of the projects in 's blog - great start.

 

I'm keen to code on my Android tablet and smartphone and then use bluetooth to flash the .hex file to the micro:bit, but I'm not having any success.

 

I've downloaded the SAMSUNG app to both my phone and my tablet and after a lot of fiddling around, I can pair both devices to the micro:bit. I'm sure youngsters will get very very frustrated with this process!! I failed so many times to even start the pairing process that I found and downloaded a ble checker to both my phone and tablet - yes they both support ble - but not all phones/tablets do & that could be a problem for some users.

 

However, before I can flash the .hex file across, I have to connect to the micro:bit. Both the phone and the tablet repeatedly refuse to connect to the micro:bit, so I am stymied.

Parents
  • 0

    Hi.

     

    We would love to hear about your work around. How you get it to sync everytime.

     

    After we transfered our first Python, the bluetooth sync functionality is gone. The pairing functionality was also gone until we made a block editor program and transfered it by cable. Even though the pairing now works again, we can't transfere programs by Bluetooth.

     

    It seems like the block editor always includes the Bluetooth functionality, where as the python editor doesn't. Is it enough to import the radio module in a python program to the sync functionality back?

     

    Please tell us your work around :-)

     

    /Henrik

  • 0 in reply to henrikbirkholm

    Hi

     

    Hello Henrik

     

    Unforunately, installing a MicroPython script ALWAYS destroys the bluetooth pairing ability and the "workround" (courtesy of Joe Finney, Lancaster University) will NOT work with any MicroPython script, I'm afraid.

     

    See here: https://support.microbit.org/support/solutions/articles/19000026073-how-to-re-instate-bluetooth-after-previously-using-micropython

     

    The "workround" is designed to allow flashing (Pairing/synchronising/bonding should work anyway!) with a PXT compliled .Hex file that does not have the Bluetooth module loaded. It shouldn't be necessary with a .Hex file compiled with any other Blocks style editor.

     

    Here is Joe Finney's "workround", which will enable you to flash a .Hex file from the Samsung App:

     

    1. Flash micro:bit with a PXT compiled .HEX file that does not have Bluetooth enabled.
    2. Pair micro:bit with phone.
    3. Start Samsung micro:bit App
    4. Put micro:bit back into pairing mode.
    5. DO NOT try to CONNECT to micro:bit from Samsung App - it won't
    6. Go straight to FLASH from Samsung App - it should work!

     

    I hope this helps.

     

    Neil

     

    Edited 07 November 2018 and marked as Correct Answer

  • 0 in reply to neilk

    Very clever - Neil. This worked for me - I was getting the "GATT ERROR" but following your workaround in exactly the given order enable me to upload some previous compiled code for driving a model car from an Andoid bluetooth app.

    Tony

  • 0 in reply to tony1tf

    Hi

     

    Glad it worked for you! - Your project sounds interesting; are you writing it up anywhere?

     

    Neil

  • 0 in reply to neilk

    Neil,

     

    Geez!  Someone at embed - the people who wrote the firmware - must have a PhD from the Microsoft School of Obscurity - that has to be the absolute ugliest work-around I have ever seen!  I cannot imagine a less obvious way to do something. . . .

     

    I will have to try this myself though I give total respect and props to you for posting your detailed instructions - other postings allude to this but don't go into the detail you did.

     

    Suggestion:

    Would you please change the "correct answer" designation to point at the posting where you provided Henrik with the detailed list of instructions?  This should be what people look for when searching this article.

     

    Thanks!

     

    Jim "JR"

Reply
  • 0 in reply to neilk

    Neil,

     

    Geez!  Someone at embed - the people who wrote the firmware - must have a PhD from the Microsoft School of Obscurity - that has to be the absolute ugliest work-around I have ever seen!  I cannot imagine a less obvious way to do something. . . .

     

    I will have to try this myself though I give total respect and props to you for posting your detailed instructions - other postings allude to this but don't go into the detail you did.

     

    Suggestion:

    Would you please change the "correct answer" designation to point at the posting where you provided Henrik with the detailed list of instructions?  This should be what people look for when searching this article.

     

    Thanks!

     

    Jim "JR"

Children