Re: It enters CDC mode, but doesn't show up in BlueTooth

Posted by Karlis on
URL: http://bluesaab-forum.90.s1.nabble.com/It-enters-CDC-mode-but-doesn-t-show-up-in-BlueTooth-tp331p336.html

Let's look at what RN52 is actually doing. When you power up the module, which of the LEDs light up and in what fashion? Is it the blue one only blinking with ~1sec interval? If so, the module is in "connectable" state (which means it's looking for a "known" device). If both BT1 and BT2 LEDs are flashing alternatively, that means the RN52 is in "discoverable" mode. That means it's ready to pair and should broadcast itself (you should see it in Bluetooth settings of your phone).

As Seth mentioned earlier, there might be a mismatch of serial baudrates. By default (factory setting) RN52 is configured to accept comms @ 115200bps. After a lot of testing we determined that this baudrate is causing issues (curved signals as opposed to nice squared ones). So the baudrate setting on RN52 has to be changed to 9600bps. One way of doing this is to short two pins on the bottom of the PCB. Once that is done, you should be able to upload the latest v2.1 code to the board, switch over to CDC mode on IHU and by holding SEEK+ button on IHU push the RN52 into discoverable mode.

Hope this helps.