openmv3 serial port hangs up

lehuijie

openmv3 serial port hangs up [Copy link]

I bought an mv3 during a promotion some time ago, and I've been playing with it for a while. While playing with the mv3, I accidentally clicked the upgrade button, and the firmware crashed, and the mv3 serial port didn't show anything. But fortunately, it was just a firmware crash, and the hardware wasn't damaged, so I just had to re-download the firmware. I used the dfu method, and just found the firmware.dfu firmware and burned it in. I tried the BootLoader and openmv firmware, but they couldn't save it. To enter DFU, you need to connect the boot and 3.3v. For specific burning methods, you can refer to the Wuzhi documentation or official documentation.

RCSN

1. It is not the firmware that is down, but the internal flash as a file system is damaged. You can use an SD card to mount it as a file system, and it will be normal. 2. The internal flash as a file system itself shortens the life of the flash. The file system needs to provide sectors as indexes, and the file index itself is constantly changing, and the sector is constantly being written. The conservative life of STM32 is only 10,000 times. 3. There is no CDC and MSC, because the file system initialization is stuck during initialization.

RCSN

In addition, openmv's BootLoader.dfu(bin) and openmv.dfu(bin) can be said to be IAP and APP. Firmware.dfu(bin) is a complete firmware, which is equivalent to merging the above two firmwares together, that is, BootLoader+openmv(IAP+APP). BootLoader.dfu can be used to burn in advance during source code debugging. The interrupt vector address of the official source code is in the APP area, so the debugging must first burn the bootloader as a jump. Of course, you can also not use this bootloader and directly redirect the interrupt vector address to the base address of Flash, which is 0x8000000