-
Notifications
You must be signed in to change notification settings - Fork 128
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
"Unsupported device selected" error with loader strings #159
Comments
Hmm, on further testing, turns out that flashing doesn't actually work with the above workaround. I have to run jlink.exec_command('DEVICE_SelectLoader BankAddr=0x60000000 Loader=QSPI') before calling connect(). Maybe connect() could be updated to parse out the loader string and pass it via DEVICE_SelectLoader? Also, discovered that on this device, you have to call |
I imagine we could parse what is after the
Thoughts? |
Hmm, I think it might be possible to have a loader string with multiple banks and loaders for them? I'm not sure what the syntax would look like though. Maybe you'd end up with something like:
The parser would have to handle this too. And we'd need to find an example of a real loader string like this to be sure. |
I encountered the same problem during the development using the board with ExitOnError 1 r loadfile "/tmp/build/zephyr/zephyr.hex" g writeDP 1 0 readDP 1 q Is there any PR that adds support for this? |
There is no PR yet that adds this support, unfortunately. |
I've been testing a chip that requires a loader string as part of the device argument. For example, on the command line, I'd pass
-Device MIMXRT1062xxx5B?BankAddr=0x60000000&Loader=QSPI
. However, when I try the corresponding code in pylink:it dies with an "Unsupported device selected" exception from JLink.get_device_index(). It looks like this is because get_device_index() expects an un-adorned string, e.g. "MIMXRT1062xxx5B".
As a workaround, I figured out that if I change the
connect()
implementation to pass only the part of chip_name before the '?' character to get_device_index(), everything works. The loader string correctly gets passed via code after that, and I can flash and run code.The text was updated successfully, but these errors were encountered: