-
Notifications
You must be signed in to change notification settings - Fork 135
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
Update BOSSA to 1.9.1 #234
Comments
@galak I opened a PR that brings back the old commit: #235 There should be no problem upgrading to the latest version of BOSSA since the offset param is now handled by zephyrproject-rtos/zephyr#26510. |
Could we pick up shumatech/BOSSA/pull/78 as well? It fixes a re-enumeration issue when resetting. |
Oh, and this will add support for Windows machines as we can drop the stty reset trigger and use BOSSA's built-in reset support. |
@nzmichaelh is there a fix for shumatech/BOSSA#96 ? That was why we went back to 1.7. |
Hi @galak I'm not sure the one you bisected to is the cause or, at least, the only one. schumatech/BOSSA@dbdd088909c57bdf9aee191720bf6c6159217e22 made a breaking change. In 1.7 and 1.8 it would automatically detect the bootloader and add the offset, while in 1.9 you need to explicitly supply the I've tested on my machine with the Ubuntu supplied 1.9.1 and it works fine. Any thoughts on how else we can test? |
Also, if we go ahead, could we pick up the current HEAD schumatech/BOSSA@3532de82efd28fadbabc2b258d84dddf14298107 ? It fixes a race in re-enumeration which we'll otherwise have to work-around in runners/bossa.py. |
I think there was some issue flashing the Arduino 101 if I remember correctly. @nashif might also vaguely remember this. |
not 101, this was about Arduino Due I think :) |
@nzmichaelh do you know what the --offset should be for arduino_due. Trying to test that out w/top of tree BOSSA to make sure that works ok. |
@nzmichaelh a few different things:
|
re: exit code, I'll fix this. re: offset, I read up on the Due and it has a separate ATMEGA as an onboard programmer, and the flash is at offset 0x80000 which matches the Was this against an actual Due, or some other Arduino? I ask as if BOSSA detects the memory, then +512k would truly be invalid as most SAMDs have 256k of flash from address 0. |
(and you can see what BOSSA detected by adding a |
This was against an actual Due board.
|
Thanks.
Only the SAM3X is affected by this. All other BOSSA based boards in Zephyr have flash that start at zero |
Handled by commit e097bbd |
b20b0aa was the previous attempt. Rolling forward requires changes to the Zephyr side west command. Once that has landed, this bug will track updating the SDK.
The text was updated successfully, but these errors were encountered: