Re: So close yet so far....

Posted by homerisback on Feb 25, 2019; 8:51am
URL: http://bluesaab-forum.90.s1.nabble.com/So-close-yet-so-far-tp1367p1368.html

Hello,

Where I'm at now:
-Plugging in board to any power source (CDC connector, USB, ISP) gets a solid red power LED => OK nice start !
-Plugging into USB gets me a brief flash of the Rx and Tx LEDs, then nothing more. => OK while not uploading any firmware into 328P.
-Plugging into the car gets me a dim flickering of CAN1 LED, nothing from CAN2 => OK. CAN2 is very weak and flashes very rarely.
-I have never seen any activity from the blue or red LEDs at any stage in the build. => not OK, that could be either :
1- LEDs are soldered upside down but BlueSaab would be discoverable by a phone (I don't really believe to this possibility)
2- RN52 doesn't start at all, maybe firmware is corrupted.

When connected with USB, under IDE, going into Serial monitor makes the 328P restart the configuration process and you should see "Configuring RN52..." then "RN52 configuration completed!" after a short while.
If not, configuration don't go to its end and RN52 won't start.

I had an issue under Windows7 with USB, it sometimes uncorrectly detected a Trackball which prevented me from uploading anything via USB. Deactivating it (NOT uninstalling it) in devices properties, solved USB communications...
328P bootloader must be burned via ISP header and nothing else. Input voltage in ISP shouldn't be 3V3 but 5V (no burn risk, it goes into voltage regulator), because if input voltage is too close to output voltage, the regulator won't be able to give a steady clean 3V3 to power the whole module...