sudden crash, battery drain with ascii protocol Ip

[sjamthe]

I was testing ASCII Immediate protocol Is worked well, but when I tried Iw the motors started at 100, 200 and at 400 suddenly the motors stopped abruptly.

I noticed system was off so I tried to restart it but no luck. Checked voltage and it had suddenly dropped to 20V and dropping very fast.

No here are some observations

1. Even when power is turned off my right wheel is somewhat rigid but if I remove the yellow power cable to the wheel it turns ok when turned by hand.
2. When charger is connected battery doesn't charge (charger light stays green)
3. I am able to power of the microprocessor and use ascii protocol to to run some commands like ?, G, C etc. But as soon as I send any Immediate commands to turn motors the microprocessor powers off without power-off tune.

Questions?

1. Is my board fried? Why is it not charging or turning?
2. How can I test?
   The battery is getting 41V but still not charging. I will leave it on overnight and see.

thanks

[sjamthe]

The battery is getting 41V but charging slowly. I measured current going to the battery and it was 3mA only.
I replaced that board with my AT32 board and battery is charging.

What is limiting current on GB32 board ? Looking at schematic I see 6A10 diode but that looks ok.
The resistance between two charging terminals is about 33K which doesn't look bad.
Any ideas how to debug?

thanks

[sjamthe]

may be by battery is discharged 100% so not charging again. Not sure how that happened though.

[btsimonh]

it does sound like two of your FETs went short circuit - so shorting the battery . I've not had any kind of failure like this, so can't advise more :(.

[sjamthe]

Thanks for the pointers. Let me poke there and see which ones.

[p-h-a-i-l]

The protection circuit of the batter probably kicked in at one point, that's why you see the voltage dropping quickly. I think the battery protection resets by unplugging the load.

[sjamthe]

you are correct about the battery. Battery protection didn't reset but I played around with the BMS by removing it and putting back and that worked.

The battery is back up and I am able to go back to my AT32 board.
I wish I had code on AT32 that supports bipropellent-protocol (it doesn't for now)

[p-h-a-i-l]

Which repo are you using for AT32? Maybe you can merge both projects to get the best from both worlds :)

[sjamthe]

I forked off of TomTinkering code , Here is my git https://github.com/sjamthe/hoverboard-firmware-hack

Last I checked he was the only one with AT32 changes, Is there a more later repo I can start with?

I tried to merge but there are a lot of diffs and I was not successful in 1st attempt. I think UART is DMA in mine and uses IT in final repo, may be some mistake there.

[juodumas]

@sjamthe could you please share how you flashed your AT32 board? I wasn't able to and have an open issue here: cloidnerux/hoverboard-firmware-hack#3

[sjamthe]

@juodumas I modified openocd code to detect AT32 device id (code below).
Then take a look at my Makefile that I use to unlock and flash code.
make load #load's the flash
make unlock #unlocks it (You may have to try other commands to unlock if this doesn't work).

--- changes to openocd ----
diff --git a/src/flash/nor/stm32f1x.c b/src/flash/nor/stm32f1x.c
index cf10e374..41b41bda 100644
--- a/src/flash/nor/stm32f1x.c
+++ b/src/flash/nor/stm32f1x.c

        /* set page size, protection granularity and max flash size depending on family */
        switch (device_id & 0xfff) {
@@ -762,6 +763,12 @@ static int stm32x_probe(struct flash_bank *bank)
                stm32x_info->default_rdp = 0xAA;
                stm32x_info->can_load_options = true;
                break;
+       case 0x242: /* AT32F403 added by sjamthe */
+               LOG_WARNING("Found 0x700 for ATF32F403");
+               page_size = 2048;
+               stm32x_info->ppage_size = 2;
+               max_flash_size_in_kb = 512;
+               break;
        case 0x446: /* stm32f303xD/E */
                page_size = 2048;
                stm32x_info->ppage_size = 2;

[juodumas]

Thank you @sjamthe! Confirming that it works. Can you contribute this back to openocd?

After patching opencd master, this worked for me:

diff --git a/Makefile b/Makefile
index bb062f4..76a1a77 100644
--- a/Makefile
+++ b/Makefile
@@ -244,11 +244,15 @@ clean:
 flash:
        st-flash --reset write $(BUILD_DIR)/$(TARGET).bin 0x8000000

+flash-at32:
+       openocd -f interface/stlink-v2.cfg -f target/stm32f3x.cfg -c init -c "reset halt" -c "stm32f1x unlock 0" -c "flash write_image erase $(BUILD_DIR)/$(TARGET).hex 0 ihex" -c "shutdown"
 flash-jlink:
         JLink.exe -if swd -device Cortex-M4 -speed 4000 -SettingsFile .\JLinkSettings.ini -CommanderScript jlink-command.jlink

 unlock:
        openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg -c init -c "reset halt" -c "stm32f1x unlock 0"
+unlock-at32:
+       openocd -f interface/stlink-v2.cfg -f target/stm32f3x.cfg -c init -c "reset halt" -c "stm32f1x unlock 0"

 #empty target for MCU selection
 AT32: all

[Brnpimenta]

@sjamthe
could you describe the steps you take to flash and reprogram the AT32 + st link?
as begginer with this type of MU, I didn't understand pretty much all of the it, what software you used?
Really appreciate it!

[sjamthe]

Sorry, it has been more than an year since I played all this. I think I used stlink utilities running on my raspberry pi as well as macbook (when necessary) to load the MU. You need a stlink loader hardware. They are very cheap on Amazon/ebay but also break very easily. I must have lost at least 3-4

…

On Thu, Jun 3, 2021 at 5:07 PM Brnpimenta ***@***.***> wrote: @sjamthe <https://github.com/sjamthe> could you describe the steps you take to flash and reprogram the AT32 + st link? as begginer with this type of MU, I didn't understand pretty much all of the it, what software you used? Really appreciate it! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXUAJ5DJYCZYBGRP6ZAL43TRAKN5ANCNFSM4IHIYMSA> .

[Brnpimenta]

@sjamthe , thank you so much for your response!
I do have a st-link v2 to recognize/reprogram the hoverboard board with AT32 chip.
but I saw your comment that you changed the openocd in order to recognize the chip. Would be great if you describe the steps you took in order to detect the chip.