Re: BlueSaab Amp pcb!

Posted by Seth on Dec 15, 2016; 1:25pm
URL: http://bluesaab-forum.90.s1.nabble.com/BlueSaab-Amp-pcb-tp737p872.html

Don't beat yourself up too bad over the bad rn52 code; it's nobody's fault but Microchip because their documentation, while quite complete vs anything else, STILL SUCKS. It lacks many things, such as all LED flashing mode codes, and problems like you just mentioned (reboot while pwren pin low), as well as another problem we found; if the A0 pin on rn52 is held high, the module can't be powered on.

Eventually we'll figure out all the quirks, and then the EOL the module :-P

On Thu, Dec 15, 2016 at 7:28 AM, sbt [via BlueSaab Forum] <[hidden email]> wrote:

sbt wrote

There are some robustness issues with Tim Otto's code in the RN52driver parseCmdResponse code that manifest themselves with truncated or otherwise invalid responses from the RN52, such as when changing baud or rebooting. If the RN52 stops sending new characters when the parser is waiting for more to complete an expected response, the system effectively ends up in an infinite loop (but it won't trigger the watchdog, since the loop() still executes).

Clarification: further work shows that while issues listed above are real, the root cause is sending the R,1 reboot command while PWREN pin is low. This prevents the reboot and the module becomes unresponsive after that. Having fixed that, I can now fully programme the RN52 on startup without relying on the separate RN52-BT-PRG sketch.

Now looking at some data mode concerns.

---

If you reply to this email, your message will be added to the discussion below:

http://bluesaab-forum.2349123.n4.nabble.com/BlueSaab-Amp-pcb-tp737p871.html

To start a new topic under Hardware, email [hidden email]
To unsubscribe from Hardware, click here.
NAML