-
Notifications
You must be signed in to change notification settings - Fork 109
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
tockloader: failing to load libtock-rs apps #521
Comments
There is a mismatch between the address ranges the app was compiled for and the address ranges supported by the kernel you are running. The reason this works with libtock-c is because libtock-c apps support PIC (note that all 3 boards you listed are ARM-based), and can therefore be placed at any address. The address ranges that Unfortunately the address ranges for apps can change with kernel version (as the kernel itself grows and shrinks), so you may end up needing to manually pass the address ranges via environment variables. Check the comments in the file I linked above for instructions. |
Thanks! that was it, sent a PR that fixes this for the nrf52840 based boards. I can get a single app to work. But not more than one at a time, even if they are manually compiled for the next available flash address and loaded (with tockloader) they will not execute. See below, only blink is running.
I did see #28 is there any progress on this? What still needs to be done? |
Woops, Turns out I had to change the RAM address too to, suppose there was an overlap but silently failed...should this not be caught somewhere? I have multiple apps working now.
Serial
|
Issue
When loading the example apps (blink, console etc...) from libtock-rs with tockloader. I see the following error. The particular error below is for the gpio example from libtock-rs loading into the
nano33ble
, so built withnrf52840
platform withmake nrf52840 EXAMPLE=gpio
. Thentockloader install
. The nanoble33 was in bootloader mode prior to running the below command, I tried without this aswell...same issue.I have tried on 3 different nRF boards, nrf52DK/Particle Boron/Nano33BLE. What's likely the culprit here?
Note that libtock-c apps seems to work as intended, I have been manually loading them with
tockloader install *.tab
for thenano33ble
, and the app being loaded with the process console/tockloader.The text was updated successfully, but these errors were encountered: