-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
does not work on mv DSO203, HW: 2.81, SYS 1.64, Upgrade V3.45C #10
Comments
Meanwhile I got it to work with one of the hints from one of the project fork. HE did a workaround and splited the app1.hex into three *.bin files with each *.addr file. With that partitioned update, it worked. |
281logo.zip |
@MotoMaxis thanks, I'll try it (but I guess I have tried already files with that name). This works with the Wildcat 6.5 fiirmware? I have the DSO203 with 2.71HW. Currently it works, but has no logo (black background) |
As far as I you you should be using WC5.6 for hw2.72 and older. WC6.5 is for hw2.8x. |
For hw2.72 logo's home is at 0x0803D800. This should work. |
Got same problem with w6.4 update to w6.5. |
If you are loading .bin file, you first must copy over .adr file for it which turns to .set, after copy .bin file. |
I did. Files in USB are: |
Share the files or link, I will check. |
Thanks a lot, i use this tutorial(https://github.com/MotoMaxis/DS203-DSOQuad/tree/master/WildcatV6.5/install_info) and provided *.adr *.bin to install. |
Issue solved. By using |
Hope this repository and thread is still active/alive. I have tried to upgrade my device with Wildcat 6.5, but it seem that it does not work for whatever reason. When I copy the 6.5 hex file, the drive disconnect in the middle of the copy. After reboot, it got stock with the boot screen showing the Wildcat 6.5 version text but does nothing further. Also the file is not renamed and the directory is empty.
I also lost my logo.
Any hints? And can anybod provide my with the original log? I cant find it elsewhere and most links are dead.
The text was updated successfully, but these errors were encountered: