Hello,
thanks for hints, meanwhile i managed as per below (valid ONLY for 510 revI):
1) source correct firmware
i used
CRX10NC4814i101003-1-cs.bin
from Github->
Bafang_M500_M600/Firmwares/Official/Motor/m510/Rev_I at main · OpenSourceEBike/Bafang_M500_M600
make sure you save raw version, file size should be 89242 bytes
CRX10NC4814i101003-1-cs.bin
2) verify the firmware is for your platform
notepad-> open-> Options (hex)
First byte 90 (88 M500,89 M600, 90 M510), second byte 67(revI). RevE use bytes89,45 (means the fw is based on M600 and 3.2 controller? Just theory).
3) install BEEST 1.23 (tried other 1.16,1.18,1.21,1.30,1.31 beta), update Drivers
4) bike-> disconnect battery, reconnect batery, turn key ON. connect with BEST HMI turn on. connect USB to PC
5) in BESST login (use python hack), go to Update. BEST is connected (green), but no serial key.
Be sure, you put into SN value "RC" otherwise you cannot flash. This SN cannot be empty!
Click Get file from local, enter fw name (short preferred, but above #1 works).
6. click Update. FW is transferred to BEST TOOL. then it beep.
7. disconnect BEST from bike, reconnect (or press reset on BEST- does not work for me). Upload from BEST to bike must start. If you get error 30, repeat steps 6-7 multiple times (for me 3-4 times).
when upload to bike is finished, long press RESET on BEST and you are back on track.
I think i am off for today upgrades (Bafang sucks...) , but can somebody recommend good fw for revI?
Currently i have
CRX10NC4814i101003-1-cs-28-2230-boot3-0-20220517161110-48v-M510.bin
Also another question, can be controller from M600 used in 510?
View attachment 97753
View attachment 97754
View attachment 97755
@
Kyokushin i suggest to make some housecleaning in Github folder, so its more undestandable for normal humans. Specially folder M510 is currently mess.
I suggest to:
1) add specific step-by step plan how to find which version user is having
2) more descriptive numbering of fw releases with description
3) summary of current issues per each motor branch and our bigger pains...
Lets start with some small survey, who is using which version of motor/which firmware and what are his/her current plus/minus strong/pains...
then we can summarize and let the ball roll to bafang. At least before we change to opensource controller