Re: Having trouble with code upload... XCode

Posted by saabstutz on Dec 28, 2016; 2:47pm
URL: http://bluesaab-forum.90.s1.nabble.com/Having-trouble-with-code-upload-XCode-tp879p890.html

It was working fine, but I was having a few issues like the steering wheel controls not working when starting the car with the headunit already in CDC mode. Wanted to update to stay with the latest version. I did fix the release configuration.

Tried the RN52-BT-PRG. I am seeing the "CMD" thing, so RN52 is woken up. With "D" command, got the following output:

CMD
*** Settings ***
BTA=000666535201
BTAC=NotConnected
BTName=Sven
Authen=2
COD=200420
DiscoveryMask=06
ConnectionMask=06
PinCode=1234
AudioConfig=0002
AudioRoute=ANALOG
CodecsEnabled=00
AudioCodec=Unknown
ExtFeatures=0084

For some reason it has some extra stuff in that Settings section (see BTAC, AudioConfig, AudioRoute, AudioCodec, CodecsEnabled). It also has it's bluetooth name not as the name I set it to (Sven) but as it's normalized name (BlueSaab-5201). Don't know if it matters, but thought I'd mention it.

When I'm using the RN52-BT-PRG, I can get the RN52 to respond by resetting it/doing the configuration found on your wiki page. I've got the flashing lights! When I unplug it and plug it back in, I'm still getting the flashing lights! Yay!

Here's the weird thing. When I put the CDC software back on the module (as opposed to the RN52-BT-PRG) the RN52 stays in discoverable mode. When I unplug it, and plug it back in, no flashing lights and not discoverable. So seems like the CDC code is getting in the way of the RN52 booting up in discoverable mode? That doesn't seem right since that's one of the configs in the RN52-BT-PRG. When I send the "V" command it refuses to go into discoverable mode. Will report back with more tinkering.