-
Notifications
You must be signed in to change notification settings - Fork 81
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
Reports file too large #6
Comments
Same issue using OSX here. |
did you use the "dfuload" tool to upload the firmware? https://github.com/gabonator/LA104/tree/master/resources/tutorial_building#flashing-and-first-run |
I know, but the very last part of that tutorial is about flashing the firmware. The installation notes from the main page are not very accurate. On OSX you need to use the dfuload tool to upload the firmware (at least in my case direct copy did not work) |
Thanks for the quick replies. I'll give that a go. If it works and I get a chance I'll help updating the readme :D |
that would be great, my head hurts when I am reading that outdated notes. |
Notes as I go along. GNU tool chaincan be downloaded from [here] (https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads/7-2018-q2-update) Inconsistencypath is modified to include the toolchain
but later this path is coded into one of the scripts
Flashingcp_la104.sh is located at system/os_host/
after flashing. turn the device off and on. It should now complain about missing shell.elf. I also had to unplug and re-plugin the usb port for the drive to remount. |
@gabonator thanks for your help so far. Can't build the shell right now. Any clues?
|
Also I think I can simplify your build process by dockerizing the build. once I get everything building...:) |
you need to build libraries first in system/os_library by running build.sh |
It seems this discussion provides enough information for flashing LA104. The information provided in readme could be misleading and a flashing guide in separate document should be added. Looking for volunteers :) |
I've tried to deploy this several times to my LA104 DFU v3.61D
Every time I do the copy fails at exactly 66%, the DFU disk disconnects and when it reconnects the system.hex has been renamed system.err.
If I then power cycle the device I get an image not found error
I did manage to re-flash with firmware from Miniware but i'd really like to work with yours. The same issue occurs for someone else running a custom firmware on the DSO here https://youtu.be/Y0BOBghLsGk
Any ideas
The text was updated successfully, but these errors were encountered: