Posted by
homerisback on
Jan 09, 2017; 11:33am
URL: http://bluesaab-forum.90.s1.nabble.com/CAN-and-bluetooth-issues-tp540p914.html
Hi,
To avoid a new thread, I feed this one with a RN52 issue.
I have a v3.3 module that has been working well for a short time and now it behaves strangely.
I suspect a faulty RN52 because :
- at power up, it goes discoverable and connects to a phone
- music starts playing for more or less 30 seconds and then, it seems that RN52 goes to sleep. BT leds go off and nothing happens if I don't recycle power or reboot RN52 in CMD mode.
* I tested it with various revs of the CDC code, ending with the latest one available on Github, no change.
* I tested it in CMD mode with Atmega328 removed (as RN52 can connect & play music in that mode as well), no change.
* I did a factory reset of RN52, then reboot ; tested it on factory config, no change
* I updated it with the suggested parameters from here, no change
* While in CMD mode, I thought about an intermittent power loss but as the RN52 goes in that kind of "sleep mode", it keeps responding to terminal commands and I can reboot it from here, so it still is under power.
* I spammed the "Q" command and at once, it goes from 040D (connected and playing) to 0000 (disconnected). It never ever goes back to discoverable.
* I checked the "autosleep delai" parameter which is at 0 (not activated).
Is anyone here has a better idea to submit for further testing ? I think I'll have to switch to a brand new RN52 (damn desoldering work to expect

), maybe it has been damaged...
01' 9.3 SE Conv - AS3 - Nexus 5 Android M 6.0.1 - BlueSaab v4.2 + Amp - Latest CDC repo.