2025-07-19 8:08 AM
I was trying to build a flight controller with this board. I was using rizacelik's repo for this project. At first, i was using the 3.0.1 firmware .hex file but then later wanted to switch to the newer 8.0.0 firmware so i flashed the newer .hex file (e.g , inav_8.0.0_STM32F411CE.hex) because the MPU6050 module wired correctly would hang my board for some odd reason. after the flash it didn't necessarily hang the board, but didn't get proper reads yet. the gyro was detected, but not the accelerometer.
I was tweaking all in the configuration tab and maybe the uart1 and usb in ports tab (i don't remember clearly what was my last action in the Inav program), then suddenly the board stopped working. i disconnected everything and came to see that the USB Type-C direct connection with my pc was not working anymore. i tried multiple other working cables, no clue. Then I used my ST-Link V2 programmer, and it connected the board. I used the Cube programmer to erase the chip memory and reflash the firmware, but still the virtual COM isn't working.
Can anyone please help me with this issue and help me get back to using the virtual com?
Thanks
(basic circuit idea that i was on)-
`` 3.7v Li-on battery + to ss14 diode to switch to L7805 5v regulator IN
regulatoe OUT to the breadboard mpu6050 vcc pin. MPU6050 SDA and SCL to stm32 B9 and B8 respectively
All GND were on a common ground
stm32 was conencted to the pc via type c (virtual com) directly to the pc``
2025-07-19 9:08 AM
Shouldn't reply to my own post, but smth very weird happened
i tried flashing the .hex file i was using, using the stlink v2 programme through the cube progrmamer. Although the usb type c virtual com isn't working by itelf, while the board is connected via the ST-Link V2 if i connect the usb, it suddenly works. i am able to see it in the inav configur as well. can anyone tell me why this is happening and is there any way i can revert to the old form where i could independently use the usb
no i didn't find any burning smells or visible hardware damages yet