[riot-notifications] [RIOT-OS/RIOT] jlink: handle flashing at IMAGE_OFFSET (#11200)

danpetry notifications at github.com
Mon Mar 18 11:39:14 CET 2019


- Handling of flashing address is now similar to that in openocd,
  except FLASH_ADDR is not automatically determined

### Contribution description

Currently, the IMAGE_OFFSET variable isn't handled in jlink.sh. riotboot.mk is currently the only place where this variable is exported. So, this is needed for riotboot to flash properly using jlink. It is a non-destructive change for everything else.

The contribution attempts to ensure that the flashing address handling in jlink.sh remains the same for all other modules - i.e., it doesn't break anything. Further PRs will clean up the wider handling of the FLASH_ADDR and IMAGE_OFFSET variables.


### Testing procedure

Testing should cover all boards which use jlink and where riotboot is either currently supported or support is under development.
- [ ] tests/riotboot with nrf52dk

Needed for:
https://github.com/RIOT-OS/RIOT/pull/11126
You can view, comment on, or merge this pull request online at:

  https://github.com/RIOT-OS/RIOT/pull/11200

-- Commit Summary --

  * jlink: handle flashing at IMAGE_OFFSET

-- File Changes --

    M dist/tools/jlink/jlink.sh (9)

-- Patch Links --

https://github.com/RIOT-OS/RIOT/pull/11200.patch
https://github.com/RIOT-OS/RIOT/pull/11200.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11200
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190318/3843066f/attachment-0001.html>


More information about the notifications mailing list