https://community.nxp.com/t5/S32K/s32K144-SRAM-U-problem/m-p/1233927#M9945 <P>Hi, It should be a problem but it is needed to check address ranges as sketched below as SRAM_L extends downwards, SRAM_U extends upwards:</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="davidtosenovjan_0-1613822429411.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/137633iD889715EF57E6751/image-size/medium?v=v2&amp;px=400" role="button" title="davidtosenovjan_0-1613822429411.png" alt="davidtosenovjan_0-1613822429411.png" /></span></P> <P>Another point is that address ranges must be defined separately in the linker command file as misaligned access it not allowed on the&nbsp; 0x2000_0000 boundary. Check your linker command file.</P> Sat, 20 Feb 2021 12:09:19 GMT davidtosenovjan 2021-02-20T12:09:19Z https://community.nxp.com/t5/S32K/s32K144-SRAM-U-problem/m-p/1233513#M9932 <P>Using the s32K144 chip, during debugging, there is a problem that the ram exceeds 32K and the compilation fails,</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="leonchan_0-1613726674618.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/137574i94B9F691B15E4194/image-size/medium?v=v2&amp;px=400" role="button" title="leonchan_0-1613726674618.png" alt="leonchan_0-1613726674618.png" /></span></P><P>According to the specification, the ram of S32K144 is composed of SRAM_L(32K)+SRAM_U(28K)+4K, can I only use SRAM_L when developing?</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="leonchan_1-1613726721377.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/137575iFC85DC39CC02EF33/image-size/medium?v=v2&amp;px=400" role="button" title="leonchan_1-1613726721377.png" alt="leonchan_1-1613726721377.png" /></span></P><P>&nbsp;</P><P><BR />How can I use the SRAM_U (28K) area. Are there any relevant examples? Thank you!</P> Fri, 19 Feb 2021 09:26:04 GMT https://community.nxp.com/t5/S32K/s32K144-SRAM-U-problem/m-p/1233513#M9932 leonchan 2021-02-19T09:26:04Z https://community.nxp.com/t5/S32K/s32K144-SRAM-U-problem/m-p/1233927#M9945 <P>Hi, It should be a problem but it is needed to check address ranges as sketched below as SRAM_L extends downwards, SRAM_U extends upwards:</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="davidtosenovjan_0-1613822429411.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/137633iD889715EF57E6751/image-size/medium?v=v2&amp;px=400" role="button" title="davidtosenovjan_0-1613822429411.png" alt="davidtosenovjan_0-1613822429411.png" /></span></P> <P>Another point is that address ranges must be defined separately in the linker command file as misaligned access it not allowed on the&nbsp; 0x2000_0000 boundary. Check your linker command file.</P> Sat, 20 Feb 2021 12:09:19 GMT https://community.nxp.com/t5/S32K/s32K144-SRAM-U-problem/m-p/1233927#M9945 davidtosenovjan 2021-02-20T12:09:19Z https://community.nxp.com/t5/S32K/s32K144-SRAM-U-problem/m-p/1234186#M9957 <P>Hi:</P><P>&nbsp;This is&nbsp; linkfile,IAR Workbench,SDK3.00</P> Mon, 22 Feb 2021 07:31:58 GMT https://community.nxp.com/t5/S32K/s32K144-SRAM-U-problem/m-p/1234186#M9957 leonchan 2021-02-22T07:31:58Z https://community.nxp.com/t5/S32K/s32K144-SRAM-U-problem/m-p/1235572#M9987 <P>Although I don't see basically anything wrong, I would rather refer to IAR support as I don't have any experience with that compiler.</P> Wed, 24 Feb 2021 08:03:06 GMT https://community.nxp.com/t5/S32K/s32K144-SRAM-U-problem/m-p/1235572#M9987 davidtosenovjan 2021-02-24T08:03:06Z