So close yet so far....

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

So close yet so far....

00Vig
Hello all --

I have a 2000 9-3.  I built HW version 5.5 and am trying to use SW 4.1.  It seems I keep getting a little closer to having a working device, but cannot reach the finish line.
- Couldn't load the bootloader.  Eventually killed my 328P but replaced it with one from a Nano (that already had a bootloader installed).  Could be the old version 328P bootloader.  Don't know if that could be causing the next set of issues.
- Loaded the 4.1 software via IDE.  Serial monitor was stuck at "Configuring RN52..."
- Bridged GPIO7 and ground, which got me to "RN52 Configuration Completed!"

Where I'm at now:
-Plugging in board to any power source (CDC connector, USB, ISP) gets a solid red power LED
-Plugging into USB gets me a brief flash of the Rx and Tx LEDs, then nothing more.
-Plugging into the car gets me a dim flickering of CAN1 LED, nothing from CAN2
-I have never seen any activity from the blue or red LEDs at any stage in the build.

My car came with a CDC and I also retrofitted a NAV system from a 2005 9-5.  Those items work correctly together.  Replacing my CDC with the Bluesaab is the same result as simply unplugging the CDC.

I've checked for solder bridges numerous times. I have the correct voltages at all of the places on the board and on the chips I can find to check.  I'm just out of ideas!  Some new ideas on where to check would be great.  Also, I believe I saw reference to one of the prominent project participants being located in the San Francisco Bay Area.  If you read this, would you be willing to take a look at my board if I mail it to you?

Thanks in advance!  
Reply | Threaded
Open this post in threaded view
|

Re: So close yet so far....

homerisback
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...
01' 9.3 SE Conv - AS3 - Nexus 5 Android M 6.0.1 - BlueSaab v4.2 + Amp - Latest CDC repo.
Reply | Threaded
Open this post in threaded view
|

Re: So close yet so far....

00Vig
Thanks for the feedback.  I couldn’t upload the CDC code thru USB... I got an error like “not in sync” or similar.  However, I was able to upload the code via ISP using a Sparkfun Pocket AVR Programmer that Karlis mentioned in a few of his posts (he recommended them for boot loader, but it worked for the CDC code, too).
-The board gets 5v thru the ISP and the regulator handles conversion to 3.3v properly.  
-When plugged into USB, my computer (Windows 10) shows a serial converter and a new com port.  No trackball, though I do recall seeing something like that before I had the correct FTDI drivers.
-Perhaps my RN52 is damaged — I did get it quite hot while soldering.  But I do get the “configuration completed!” message in the serial monitor window.  Is that message actually generated by a response from the RN52?
-Confirmed LEDs are inserted correctly.  Also, the RN52 is not broadcasting as discoverable.
-Also concerned that my car doesn’t recognize the bluesaab when it is plugged in, so it seems there’s more wrong than a possibly dead RN52.

Feeling like I’ve run out of ideas.  Perhaps I’ve managed to taint this board in an unusual way.  Rather than starting over and rebuilding this 5.5 board I should probably start over with the v6.0.  Alternatively, if there’s someone in the Bay Area that’s familiar with these things and willing to take a look, I’d be happy to drop my device in the mail.  I’m in Walnut Creek.
Reply | Threaded
Open this post in threaded view
|

Re: So close yet so far....

Karlis
Administrator
00Vig, DM.
2001 9-5 SE V6; 2006 9-5 Wagon; iOS; BlueSaab version = "latest and greatest" :)