Skip to content

GitLab

Switch branch/tag
  1. 26 Mar, 2021 2 commits
    • Nishanth Menon's avatar
      plat: ti: k3: platform_def.h: Define the correct number of max table entries · c9f887d8
      Nishanth Menon authored 
      

Since we are using static xlat tables, we need to account for exact
count of table entries we are actually using.
peripherals usart, gic, gtc, sec_proxy_rt, scfg and data account for 6 entries
and are constant, however, we also need to account for:
bl31 full range, codebase, ro_data as additional 3 region

With USE_COHERENT_MEM we do add in 1 extra region as well.

This implies that we will have upto 9 or 10 regions based on
USE_COHERENT_MEM usage. Vs we currently define 8 regions.

This gets exposed with DEBUG=1 and assert checks trigger, which for some
reason completely escaped testing previously.

ASSERT: lib/xlat_tables_v2/xlat_tables_core.c:97
BACKTRACE: START: assert
Signed-off-by: default avatarNishanth Menon <nm@ti.com>
Change-Id: I962cdfc779b4eb3b914fe1c46023d50bc289e6bc
      c9f887d8
    • Nishanth Menon's avatar
      plat: ti: k3: board: lite: Increase SRAM size to account for additional table · 2fb5312f
      Nishanth Menon authored 
      

We actually have additional table entries than what we accounted for in
our size. MAX_XLAT_TABLES is 8, but really we could be using upto 10
depending on the platform. So, we need an extra 8K space in.

This gets exposed with DEBUG=1 and assert checks trigger, which for some
reason completely escaped testing previously.

ASSERT: lib/xlat_tables_v2/xlat_tables_core.c:97
BACKTRACE: START: assert
Signed-off-by: default avatarNishanth Menon <nm@ti.com>
Change-Id: I5c5d04440ef1fccfaf2317066f3abbc0ec645903
      2fb5312f
  3. 25 Mar, 2021 4 commits
  5. 24 Mar, 2021 34 commits