Issues Flashing V6.1 Bootloader and Firmware

[Seth]

This is all still assuming that no magic smoke was released from the chip by using 5v on VCC pin...

On Tue, Jun 9, 2020 at 19:33 Karlis [via BlueSaab Forum] <[hidden email]> wrote:

You won't see anything until BlueSaab firmware is loaded onto the module. Here's how it goes:

- There's a distinction between UART1 and UART2 pins.
- UART1 is used exclusively to flash firmware onto STM32 as that's the interface STM32 bootloader is listening to out of the box.
- UART2 pins Rx and Tx are used for debugging. That's where you should see a welcome message once you successfully flash the firmware onto STM32.

So you would need to:

1. Power on the module and do the button sequence to push it into DFU mode.
2. Use UART1 to flash BlueSaab firmware onto module.
3. Power down the module.
4. Connect UART2 Rx pin to Tx pin of your FTDI cable.
5. Connect UART2 Tx pin to Rx pin of your FTDI cable.
6. Connect any GND pin on the module to the GND pin of your FTDI cable.
7. Open serial connection using PuTTY at 115299 8 data bits; no parity; one stop bit.

You should now see a message (you might need to hit RESET button again):
"BlueSaab"
"Hardware version: 6.1"
"Firmware version: 6.1.1"

2001 9-5 SE V6; 2006 9-5 Wagon; iOS; BlueSaab version = "latest and greatest" :)

---

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

http://bluesaab-forum.2349123.n4.nabble.com/Issues-Flashing-V6-1-Bootloader-and-Firmware-tp1625p1645.html

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

... [show rest of quote]

[QuickLime]

Sorry I missed this! Somehow I must have missed the email and I hadn't double checked the thread. Okay, I'm going to try ordering a new FTDI cable and give it another shot. Hopefully it'll work out alright! I'll definitely be back to ask for help if not

[QuickLime]

Okay, so I have a new cable now and I found out that I had accidentally flipped D2 and D3, resoldered them and now power appears to be good from the FTDI cable. Now, when I connect the FTDI cable to UART1, I hold Boot0, press Reset quickly, and then release Boot0. After doing this I hit next in the STM flash loader demo program, it waits a bit and then tells me "Cannot get available commands, Please, Try to change Echo selection, Reset your device then try again..."

I've tried all the different Echo settings, for example when I set Echo to listen then it's getting no response from the target. So, I figure that something is happening since I can reliably reproduce different error messages... Any ideas? I also have a full set of components that I'm working on soldering up. Hopefully that one works and maybe I can troubleshoot my first one haha.

[QuickLime]

Alright, a bit more than 2 hours later and I have one almost totally soldered up (minus a few connector headers I haven't put on yet). Now, when I plug it into FTDI, I get the solid red power LED and a blue/red flashing LED1. I didn't get this on the last one, so maybe I fried something...

Anyway, when I do the boot/reset button combo nothing happens, and the ST flash loader just says that it has no response from the target. Any ideas? Thanks, feeling more confident in it now though, eventually I'll get one working!