-
Notifications
You must be signed in to change notification settings - Fork 43
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
Loading hex file from Linux #50
Comments
Hi, I use Linux, too. |
Hi @bobosch, Thank you for your quick reply. I would rather not have to install wine just for this if there is a simpler solution. UnifiedHosts did not work with java 17, I changed to 1.8 and then it started
select
I have not tried using it, as I don't know which options to select. |
The Unified Bootloader is unfortunately not compatible with the AN1310 bootloader, so this will not work. The windows bootloader can be found here: |
Thank you both for your replies. I could not make the AN1310 application running under I have instead compiled the program for Qt5 from the sources mentioned above, and the usb device is showing up (I have not yet attempted to load the hex file onto SmartEVSE). Follow steps 1-3 from the Readme.txt (or replace step 1 with installation of |
With wine you have to add a registry key (wine regedit) to |
I actually tried that as well, forgot to mention that. Unfortunately I already uninstalled wine after building the native Linux AN1310 application, so I can't double check that I entered exactly what you suggest. |
For anybody coming here: |
I'm on Linux.
I have compiled the project and now I need to load it.
The instructions here https://www.smartevse.nl/building-and-programming say "Start the AN1310 bootloader program in the /bootloader directory."
I cannot find any program called AN1310, and no bootloader directories related to mplab.
Should I use UnifiedHost-1.19.1 booloader from here https://www.microchip.com/en-us/tools-resources/develop/libraries/microchip-bootloaders/8-bit?
If so, then what are the correct settings?
Or something completely different?
The text was updated successfully, but these errors were encountered: