Shawn Nematbakhsh 5ea69a7b3b coderam: Don't assume that RO/RW images reside at start of code memory ...

RO/RW images may reside at an offset to the start of code memory,
defined at the chip-level by CONFIG_R*_MEM_OFF.

BUG=chrome-os-partner:38103
TEST=Manual on Cyan. Verify sysjump works correctly in both directions.
BRANCH=None

Change-Id: I54c5f20335a5646d49afcc8d3fa2eb90ca9349d0
Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/274434
Reviewed-by: Divya Jyothi <divya.jyothi@intel.com>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Tested-by: Divya Jyothi <divya.jyothi@intel.com>
Reviewed-by: Mulin Chao <mlchao@nuvoton.com>
Tested-by: Mulin Chao <mlchao@nuvoton.com>

2015-06-13 07:12:38 +00:00

..

cortex-m

coderam: Don't assume that RO/RW images reside at start of code memory

2015-06-13 07:12:38 +00:00

cortex-m0

core: Assert if task_get_current() cannot return a valid task ID

2015-06-12 22:21:15 +00:00

host

core: add task_wait_event_mask() function to other cores

2015-06-11 02:57:45 +00:00

nds32

core: Assert if task_get_current() cannot return a valid task ID

2015-06-12 22:21:15 +00:00