Re: BlueSaab 6.1 - No "BlueSaab" Bluetooth device available after power up

Posted by Seth on Sep 24, 2019; 11:37am
URL: http://bluesaab-forum.90.s1.nabble.com/BlueSaab-6-1-No-BlueSaab-Bluetooth-device-available-after-power-up-tp1492p1530.html

So it just clicked with me this morning rereading your post; if you applied 5v to EXT pin, that means you hit the stm32 with 5v, but it’s not 5v tolerant.....I would suspect ic damage at this point...and probably with the RN52 as well.......

You might wanna but replacements for both chips unfortunately :-/

On Mon, Sep 23, 2019 at 19:11 czabel [via BlueSaab Forum] <[hidden email]> wrote:

Yeah, of course - and hey, the more things I find, the better my How To document will be later!

To be clear, I first applied the 5V from the FTDI cable to the EXT VCC pin, because I wasn't paying attention. I then switched to the FTDI header's VCC connection and verified that the LDO is operating as expected, but nothing showed up on the oscillator. Perhaps that's due to just being on the edge of operation, and the scope lead broke things. You're right about that having an effect, but even if it was loading the circuit enough it wouldn't be periodic like that, nothing on the scope should be running at 1kHz...

Alright, swapped probes to a higher impedance option, and got this:


It may not be pretty, but I feel fairly confident the oscillator is working as intended.

At this point I'm leaning strongly toward the "I cooked my STM32" option, but I still don't understand how that would still allow the programming to occur, but not regular operation. Bizarre.

Seth, you're right - the oscillator will be the first thing to swap out - but I'll buy both to avoid waiting for another shipment, and I'm getting multiples this time... :)

---

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

http://bluesaab-forum.2349123.n4.nabble.com/BlueSaab-6-1-No-BlueSaab-Bluetooth-device-available-after-power-up-tp1492p1529.html

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