Sockoo
10 µW
I bought a package with a qs180 and a 72850 encoder far driver controller. Sadly the cpu died after only a few hours of use. I went into a fairly deep dive on this and ended up identifying that the 3.3v to ground bus for the cpu was shorted. After trying a bunch of things i removed the cpu and found out that was the issue. i ordered a bunch of parts and flashed a new matching cpu and installed it back onto the board. I am having some issues still getting it working.
After testing I still get to connection to the cpu in the app. I tested what i could with the controller together, there is now power and ground on the cpu on all legs there should be. I eventually decided that the header on the board should work for stlink programming the cpu. So I soldered some headers on there. It does work and interestingly it power the bluetooth adapter as well so I first read the cpu to make sure i could talk to it and that the process of soldering it on didn't damage it. I am not a professional air solderer. It looks good and its readable and writeable. So eventually i tried loading some 841200 firmware from the forum onto it and nothing different happened. I then found a large repository or files including many versions of firmware on the forum in this thread while i read the whole thing. Nanjing far driver controllers
I realized eventually that 841200.hex file and my 72850.bin file i got from the place i bought my setup from cannot be run in the stm32 st-link utility. But there were some ones in the files in that thread that do run. So I tried them and i now have clicks coming from the speaker!!! Very Exciting!!! So i get 6 clicks, they arent proper beeps but it will just click 6 times forever if i power it from the stlink. I cannot connect to the bluetooth still sadly. I did look at some of the files and do compairs and it seems the file structure over all is somewhat different. My motor is an encoder motor as well so without knowing if the other firmwares are, its possible the firmware just wont work cause of that.
The question i have now is, If i am directly flashing a raw cpu/mcu will that even work using the firmware files around on the forums and that i got from the vendor that are for use in the app? Is it possible I need some other simple code to preload on the cpu to get the uart to work so i can connect with the app then flash the firmware through that?
Has anyone successfully replaced a fried cpu on fardriver controller? What trick am i missing here. It has good power and ground which makes me think i should be getting farther than i am. What can I try next.
After testing I still get to connection to the cpu in the app. I tested what i could with the controller together, there is now power and ground on the cpu on all legs there should be. I eventually decided that the header on the board should work for stlink programming the cpu. So I soldered some headers on there. It does work and interestingly it power the bluetooth adapter as well so I first read the cpu to make sure i could talk to it and that the process of soldering it on didn't damage it. I am not a professional air solderer. It looks good and its readable and writeable. So eventually i tried loading some 841200 firmware from the forum onto it and nothing different happened. I then found a large repository or files including many versions of firmware on the forum in this thread while i read the whole thing. Nanjing far driver controllers
I realized eventually that 841200.hex file and my 72850.bin file i got from the place i bought my setup from cannot be run in the stm32 st-link utility. But there were some ones in the files in that thread that do run. So I tried them and i now have clicks coming from the speaker!!! Very Exciting!!! So i get 6 clicks, they arent proper beeps but it will just click 6 times forever if i power it from the stlink. I cannot connect to the bluetooth still sadly. I did look at some of the files and do compairs and it seems the file structure over all is somewhat different. My motor is an encoder motor as well so without knowing if the other firmwares are, its possible the firmware just wont work cause of that.
The question i have now is, If i am directly flashing a raw cpu/mcu will that even work using the firmware files around on the forums and that i got from the vendor that are for use in the app? Is it possible I need some other simple code to preload on the cpu to get the uart to work so i can connect with the app then flash the firmware through that?
Has anyone successfully replaced a fried cpu on fardriver controller? What trick am i missing here. It has good power and ground which makes me think i should be getting farther than i am. What can I try next.
