Maker X Bluetooth module cant load Firmware.??

[Ace_FNC]

Hallo guy,

i’ve just finished my build but can’t get my Bluetooth Module to work. I already tried updating the Firmware of my VESC ( Maker X Go-FOC DVB6) and flipping TX and RX 100 times. Also i tried every kind of settings but when i try connecting the divice it timed out or showed me can’ load Firmware. These are my settings →

[Ace_FNC]

This is the bluetooth module im using. MakerX Bluetooth Module suitable for all series of VESC

[hasaarin]

Why are you loading firmware. Should work OOB

[jaykup]

If I had to guess, the bluetooth module is either faulty or doesn’t have firmware on it.

You can try to flash it manually

NRF51822 Flashing / Setup in Windows using a STLink V2

NOTE: You can use your VESC to do this whole think a lot easier. See video below: https://www.youtube.com/watch?v=PFFiVxFHDM4 How to do it the hard way: After some issues getting mine setup and working I thought I’d post a guide of how I did it. Please do double check pins with what your board/programmer lists as they could vary Also there is a guide here if you want to follow Vedders guide:

Vedders Guide:

<a href="https://github.com/vedderb/nrf51_vesc/blob/master/README.md" re…

Process is the same for the NRF51 and NRF52 chipsets, but the firmware is different. Just verify which chip it has and load the right firmware

[glyphiks]

I’ve had a maker bluetooth power on but be unresponsive. One out ofmaybe 30-40… but it definitely happened.

[Ace_FNC]

Ok thanks already expected it. I’ll give you a update when i tried it with the new firmware.

[Ace_FNC]

I get this error every time i want to connect the SWD. Idk if i can’t over the usb port but i don’t have any other left on this VESC.

[OleksiiF]

Had the same issue with same Bluetooth - swd flashing did not helped. Nothing hepled

[jaykup]

It’s hard to tell from the pictures, but it looks like you are plugging the BLE module’s TX/RX wires into the hall sensor port? (circled in red in your pic). I assume this is because you are trying to program it, and if you previously tried connecting it to the COMM port with all the right wiring, then here is how to properly connect it to the SWD port.

You will need to connect the 3.3v, GND, SWDIO and SWDCLK connections on the bluetooth module, to the same pins on the ESC for the SWD programming to work. That module only has 4 wires, so the SWD connections must be pads on the module somewhere that you can solder wires onto. Something like this:

On the ESC, the SWD port is under the aluminum cover.

Once programmed successfully, you can hook it up like normal on the COMM port

5v → 5v
GND → GND
TX → RX
RX → TX

[Ace_FNC]

Whoops marked the wrong port those are for the hall sensors. I connected the BT module to the port right next to the marked 1. But i will flash the dongle with another VESC where i dont have to remove the cover and after flashing the right firmware i’ll try to use it on this VESC. I’ll update when i finish flashing.

[Ace_FNC]

@YUTW123 Is this an known issue. Im not the only one who’s having trouble installing your dongel. You also dont have a download link for the firmware of this dongle just those of the VSEC.

[YUTW123]

RE-Download the firmware should solve the problem. It is recommended to use jlink downloader, if using VESCTOOL to download. You need to check “Verify during download”

[Ace_FNC]

Hello Jaykup,

I upgraded the firmware successfully. But nothing has changed. Are there any other solutions i can try?

[jaykup]

Based on the screenshot it appears as though you updated the firmware on the ST-LINK not on the bluetooth module?

These are the steps I’ve followed to load the firmware onto bluetooth modules in the past

@Morpheus

Download these:

• OpenOCD Windows Programmer: https://gnutoolchains.com/arm-eabi/openocd/
• STLink V2 drivers: https://www.st.com/en/development-tools/stsw-link009.html
• Vedders NRF51822 github repo: https://github.com/vedderb/nrf51_vesc

@Morpheus

Steps:

1. Download needed files.

2. Install STLink drivers.

3. Unzip the OpenOCD files & Vedders NRF51 repo.

4. Copy “openocd.cfg” from the NRF51 repo to the OpenOCD “bin” directory (same dir as openocd.exe)

5. Copy the relevant nrf51 hex from the NRF51 repo (under “nrf51_vesc-master\build_all” dir) to the OpenOCD “bin” directory. For me I used “nrf51_vesc_ble_16k_16m_rx11_tx9_led3.bin” as that matched the NRF module I bought (link below).

6. Wire up the STLinkV2 to the NRF51 module; see this for pin assignment:
   

7. Open up a Command Prompt window and browse to the OpenOCD bin folder (or type cmd.exe into the address bar of Windows Explorer if you are already in that folder to open a Cmd prompt already at that folder).

8. Run this command (Change the name of the .bin file to whichever firmware you are using:
   openocd -f openocd.cfg -c “init” -c “halt” -c “nrf51 mass_erase” -c “program nrf51_vesc_ble_16k_16m_rx11_tx9_led3.bin verify reset exit”
   a. You should see an output something like this:

Hopefully @YUTW123 can let you know which firmware version to use

[2rill]

Did you get to fix it?
I have a similar issue