topic How to reset Rapid IoT after multiple pairing in Rapid IoT

How to reset Rapid IoT after multiple pairing

cswiger — Wed, 26 Dec 2018 21:04:18 GMT

Looks like I made a mistake of pairing the Rapid IoT device with a phone (worked find), then deleting and pairing it with a tablet (worked fine), and now trying to go back to the phone. At this point neither can pair with the device - actually they START to, either will find it, provision, the device even DISPLAY THE CORRECT TIME briefly then resets and is never seen again. Have tried many times since with no luck, let battery drain, etc.

So the question is - how to reset it so I can pair with one phone and leave it there?

This in response to my request to return the kit to hackster.io - I have no problem logging into any nxp resource now.

"It looks like he is trying to pair multiple smartphone devices to the kit. This is not supported in the current OOB, only one smartphone can be provisioned with the UUID of the device. Regarding the account creation Idk the issue, is he experiencing issue with SSO login to rapid iot studio? He could post on NXP community if he needs helps. If he is experiencing hardware issue we should check on our log file of the part. For that we need the part number of the device. "

The part number is SLN-RPK-NODE and bluetooth M 00603700000AAFEF ID 410384939406069B

Re: How to reset Rapid IoT after multiple pairing

theophileleroy — Thu, 27 Dec 2018 10:38:35 GMT

As descriebed in the Quick start guide, reset procedure for rapid-iot is to push SW5 on the back of the kit with the tool included in the package.

If you mean reset default application binarys and bootloaders of the kit you can take a look at these how-to guide :

Recovering k64f & kw41z applications binaries

Recovering k64f & kw41z bootloaders binaries

You cal also try from online IDE to compile and download new binary of Out Of Box Demo and flash it to rapid-iot in usb-mass-storage mode (see this video to enter usb-mass-storage mode). This is another way to reset default OOB application.

Regards,

Re: How to reset Rapid IoT after multiple pairing

cswiger — Thu, 27 Dec 2018 14:30:00 GMT

Yes - have tried the reset button on the back - etc.

If I hold SW3 while resetting we get the mass storage mode OK - oddly there is not enough room for the file:

1010739 Dec 27 08:53 Rapid IoT Kit Out Of Box Demo.atmo < -- 1MB file

Filesystem Size Used Avail Use% Mounted on

/dev/sdb 892K 0 892K 0% /media/chuck/RPK < -- 900K storage

If I try one of the smaller ones like

18238 Dec 27 08:57 Rapid IoT Blinking an LED.atmo < -- 18K fits

and copy it on the storage it *does not* automatically reboot as stated in the video - when manually reset it goes back to the oob demo just as before.

What is interesting is when trying to provision it the app finds the device ok, BLE blinks a few times, IT ACTUALLY GETS THE CORRECT TIME shown on the display then RESETS, and can never attach and get data again. Like it is almost starting to work until the reset then never re-connects.

Also, another clue, I can re-provision the same device over and over, finds it again as a new kit and adds it to the list, resets and never connects again.

Re: How to reset Rapid IoT after multiple pairing

theophileleroy — Thu, 27 Dec 2018 15:56:38 GMT

You need to upload .bin and not .atmo file

The .atmo is a file to share project to someone. The file you need to load in usb-mass-storage is the binary file generated after compile & Program Firmeware:

Re: How to reset Rapid IoT after multiple pairing

cswiger — Thu, 27 Dec 2018 16:31:03 GMT

Thank you sir - reflashing a new build of OOB cured the BLE connect issue - it is now getting data from the device to the phone now.

Re: How to reset Rapid IoT after multiple pairing

frakman — Fri, 28 Dec 2018 04:28:53 GMT

Sorry to hijack this thread and if this is an obvious question.

What is the procedure to shutdown (i.e. power off) the device? I know that you push two buttons to enter programming mode and push SW5 and reset button to reset. However, I didn't see a shutdown method mentioned anywhere.