Re: It enters CDC mode, but doesn't show up in BlueTooth
Posted by
homerisback on
May 15, 2016; 5:33pm
URL: http://bluesaab-forum.90.s1.nabble.com/It-enters-CDC-mode-but-doesn-t-show-up-in-BlueTooth-tp331p342.html
Hi guys,
While struggling to communicate in CMD mode with RN52's, I finally went into the hardware way and jumpered GPIO7 and GND to force 9600 baud comms.
Meanwhile, I checked on Github the version available and downloaded the May 2016 revision of CDC v2.1
I uploaded it into the my left two 328's and........ RN52 refused to start, on both modules, since 328 is on the BlueSAAB module, when 328 is removed from the board, RN52 starts properly with external power (i.e. FTDI cable)

From there, I checked the changes made in the code and removed the PWREN related lines and reverted to previous way of starting RN52 chip => it works flawlessly in car. So, from now, I can say that the PWREN mod affects the PCBs < v3.3
Could I suggest to revert back to previous v2.1 - March 2016 for PCB < 3.3 ? This should solve Pilkerton's issue.
I noticed bluetooth odd behaviour with that version as well, I'll report this in software section.
01' 9.3 SE Conv - AS3 - Nexus 5 Android M 6.0.1 - BlueSaab v4.2 + Amp - Latest CDC repo.