DUDU7 LATEST MCU FIRMWARE.

Bettman66

surfer63

Bettman66
Vielen Dank. Das moment von Starten des upgrades und die reboot dauert länger als bei mir. Ich drucke auf der soft-taste and innerhalb eine Sekunde reboot der (/die/das? 🙂 ) DuDu.

One question: Which USB-port do you use? One of the USB-A ports or the USB-C port?

@DUDU-Meng: In the movie from Bettman66 you see that he is doing the same thing that I do, but then from USB-stick (which I already tried and started with). The difference in his movie is that it takes 1-2 seconds before his unit reboots. In my case it reboots immediately.

surfer63

I tried all different ways. From usb-stick via the other upgrade, from internal memory via the other upgrade, and the old-fashioned way by putting the lsec6318update plus Stm32ud.bin on a usb-stick and let the unit detect a firmware upgrade and reboot.
None of them worked. Off course, I downloaded the .7z again and tried with the new one. Same result, meaning no result.

DUDU-Meng

surfer63
Have you tried using another USB flash drive to upgrade it?
I have a USB flash drive that has the same problem when upgrading the system or a certain file. I clearly put in a new file, but after the upgrade, it is still the old one.
This problem does not occur when using other USB flash drives.

surfer63

DUDU-Meng Have you tried using another USB flash drive to upgrade it?

Thanks for replying.
You are missing the point. In the movie I used the bin file directly from internal memory.
And again, like I mentioned multiple times before: I downloaded the Stm32ud.bin from my server onto my unit and started the MCU upgrade from OTA-update -> "other firmware" -> "MCU firmware" .
I did not use a USB-stick or SD-card at all. Just to make sure that there could not be any errors from faulty USB sticks or SD-cards.

Next to that: Before using it directly from internal memory, I used a USB-stick and an SD-card in an SD-card reader. Both were checked for cleanlyness, dirty bit and corruption and were OK. That didn't work.

DUDU-Meng

surfer63 I have never encountered this problem before, so I really don't know how to solve it. Let's ask @yaoxilong to help us figure it out.

surfer63

DUDU-Meng
I finally succeeded and now did the complete MCU and Bluetooth firmweare in one go (I was a bit fed up after all the failures and decided to do both MCU and BT firmware upgrade in one go).
I formatted another SD-card and put the latest lsec6318update, the Stm32ud.bin and the latest Bluetooth firmware blinkfile.bin (from CQ134_20250705_7870.7z) on it.
I connected that one to USB-C and let the system determine (again) the new firmware. So it found the firmware and rebooted twice. The second time it started to install the MCU firmware and the Bluetooth firmware.
I wanted to record a video with my phone, but the photo app crashed ! (Murphy's law I suppose. I never experienced that before).
Sorry for the bad resized photo. (I wanted to see if the photo app worked again 🙂 and used the automatic removal of reflections)

The strange thing is that it says "unknown canbus version". I can't remember having seen that before and the Canbus info and SWC simply works nicely.

EDIT: Sorry. Must be due to the MCU upgrade. Like said, SWC functioned, but I had to reconfigure my RZC (Raise) canbox again for my car.

EDIT 2: I now suddenly see that the Bluetooth version is 2025-07-05, but what is that date of Jul 30 2025 behind it? I did the upgrade today 18 August. Is that de Android version of the Blink Bluetooth stack?

gismo

DUDU-Meng ok so I've done the MCU update as well now and it just seems a bit hit and miss frankly:

I've only used this method:

Download the 7z linked above, directly onto the internal memory of the device
Unpacked the archive onto the device.
Used OTA-App/Other/MCU update (old status 2023) to select .bin and start update.
On first try, the unit rebooted directly and I was greeted by the old MCU version, so not successful.
I just tried the same again (no new download or unpacking, so same file) and this second time it needed a bit more time between hitting start and doing the reboot. This time the update was successful...

So the issue seems to be the updater. I didn't get any error messages (first try), nor progress nor success messages (second try).

Canbus/SWC was a bit shaky after the update. Worked after another reboot. Guess a reset would be good but had no pin in the car...

Edit: Version info added

Prior to updating

After updating (also updated BT firmware OTA, no issues there)

Bettman66

surfer63
I placed the USB-C port in the glasses compartment with an extension cable and performed the update using a USB-C stick.
I also have the same problem with the CANbus adapter; it's not always recognized. The steering wheel controls stopped working in the car once. I'll have to keep an eye on that, as it hasn't happened again since.

edit: Bluetooth is a different Version

surfer63

Bettman66
I downloaded the latest Bluetooth firmware which was 2025-07-05, but yours is 2025-08-07, so even newer. Where did you get that one?

Bettman66

surfer63
OTA Update

surfer63

Bettman66 OTA Update

And it starts all over again.
Although not really necessary, I used OTA upgrade-> other upgrade, and downloaded the new BT firmware 20250807 and tapped "Start update". It tells me not to use the unit and finishes after 1-2 minutes. But no BT firmware upgrade. The version is still the same. I rebooted and did it all over again. Still no BT firmware upgrade installed.

@DUDU-Meng : Can you please check if the OTA upgrade is broken in version 250812?
Everything I did via OTA upgrade on 250812 is failing.

Mikescotland

MCU: 2024.01.24 17:12:03 DUDUAUTO_53_L7870_N32P48F64_3G_E60_V:1.0
What MCU update for mine please?

surfer63

Mikescotland
The one from dudu_meng many posts above in this thread.
https://drive.google.com/open?id=1cW55TPYC9NhSTNWbSk0HiN9wfoRCDDe_&usp=drive_fs

Note though that we are talking about MCU firmware AND a separate BT firmware upgrade.

Bettman66

surfer63
the OTA app version on both radios is 1.001118, but it may be different for you.

edit:

surfer63

My version is also 1.001118, but it still could be some underlying reason

surfer63

It is getting stranger and stranger. I wanted to do another try at the Bluetooth firmware.
This is what the MCU firmware screen tells me (and now with proper screenshots from the unit)

Then I go to the Bluetooth upgrade screen and I see this.

Previously it mentioned the Bluetooth version. Now it mentions "unknown MCU firmware Version".

@DUDU-Meng : I really consider this a serious bug and another indication that the OTA updater is buggy.
From the screenshots you see my MCU version being 2025-07-15. My current Bluetooth version is 2025-07-05 (although not mentioned anymore) and my OTA update binary is version 1.001118.

DUDU-Meng

surfer63 You can try again. The server's Bluetooth firmware has now been updated to 250819.

surfer63

DUDU-Meng

I first updated my normal firmware to 250820 (other users: this is beta, not generally available).
My MCU firmware is still at the latest 2025.07.15
Then I updated my BT firmware to 2025-08-19. This was succesful. As far as I can remember, I now got for the first time a progress with increasing percentage. Before I only saw "Do not use your unit while firmware upgrade is taking place", or something like that. And sometimes I did not see this at all.

Anyway, currently the OTA updater functioned and I am now on the latest MCU and BT firmware and so far it functions fine.

Slavus

surfer63 What is normal firmware 250820? Is this MCU version? Where can i find it?

surfer63

Slavus What is normal firmware 250820? Is this MCU version? Where can i find it?

Normal firmware is what FYT and Dudu and all resellers call firmware, which is a new version of the software being the kernel and applications for your unit.
That is different from the MCU, Bluetooth and CANbus firmware.
See below from the default OTA-updater screen.

The soft-button "Other update" leads you to the MCU, Bluetooth and CANbus firmware upgrades.

« Previous Page