<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Synchronous Abort handler in Embedded Software and Tools Clinic</title>
    <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/Synchronous-Abort-handler/m-p/1416713#M244</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I load fsl-image-auto .sdcard file onto SDcard. Added u-boot.bin to uboot partition. Im using bootloader from platform software integration packet and loading u-boot to address 0x34090000 with reset handler address set to 0x340a0000. u-boot.bin successfully loads to RAM, and I can see it starts in console. But I get following error and board just resets and always same console output:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;U-Boot 2020.04+g6286902c94 (Nov 17 2021 - 08:47:30 +0000)

CPU: NXP S32G274A rev. 2.1.0
Reset cause: Power-On Reset
Model: NXP S32G2XX
Board:  NXP S32G274A-RDB
DRAM:  3.5 GiB
"Synchronous Abort" handler, esr 0x96000010
elr: 00000000340d8f78 lr : 00000000340d8f64 (reloc)
elr: 00000000fff6ff78 lr : 00000000fff6ff64
x0 : 0000000000000001 x1 : 0000000000000042
x2 : 00000000ffffffff x3 : 0000000000000002
x4 : 00000000fff700f0 x5 : 00000000ffffffff
x6 : 0000000000000021 x7 : 0000000000000000
x8 : 00000000ffd34f40 x9 : 000000000000000c
x10: 00000000fff9b818 x11: 00000000ffd2d32c
x12: 0000000000002a80 x13: 00000000ffd2d38c
x14: 00000000ffd2d5b8 x15: 0000000000000001
x16: 00000000fff7c068 x17: 00000000000000ff
x18: 00000000ffd32dd8 x19: 0000000000000000
x20: 00000000fff9f9d4 x21: 0000000000000000
x22: 0000000000000002 x23: 0000000000000021
x24: 00000000ffd37e60 x25: 00000000fffa81a9
x26: 0000000000000042 x27: 0000000000000002
x28: 00000000402dc000 x29: 00000000ffd2d310

Code: b9407fe0 1ad52363 93407c76 340006e0 (387c6ac0)
Resetting CPU ...

resetting ...&lt;/LI-CODE&gt;&lt;P&gt;Im using S32G274A RDB2 board. Linux BSP is v31.&lt;/P&gt;</description>
    <pubDate>Mon, 21 Feb 2022 10:27:34 GMT</pubDate>
    <dc:creator>st_ra</dc:creator>
    <dc:date>2022-02-21T10:27:34Z</dc:date>
    <item>
      <title>Synchronous Abort handler</title>
      <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/Synchronous-Abort-handler/m-p/1416713#M244</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I load fsl-image-auto .sdcard file onto SDcard. Added u-boot.bin to uboot partition. Im using bootloader from platform software integration packet and loading u-boot to address 0x34090000 with reset handler address set to 0x340a0000. u-boot.bin successfully loads to RAM, and I can see it starts in console. But I get following error and board just resets and always same console output:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;U-Boot 2020.04+g6286902c94 (Nov 17 2021 - 08:47:30 +0000)

CPU: NXP S32G274A rev. 2.1.0
Reset cause: Power-On Reset
Model: NXP S32G2XX
Board:  NXP S32G274A-RDB
DRAM:  3.5 GiB
"Synchronous Abort" handler, esr 0x96000010
elr: 00000000340d8f78 lr : 00000000340d8f64 (reloc)
elr: 00000000fff6ff78 lr : 00000000fff6ff64
x0 : 0000000000000001 x1 : 0000000000000042
x2 : 00000000ffffffff x3 : 0000000000000002
x4 : 00000000fff700f0 x5 : 00000000ffffffff
x6 : 0000000000000021 x7 : 0000000000000000
x8 : 00000000ffd34f40 x9 : 000000000000000c
x10: 00000000fff9b818 x11: 00000000ffd2d32c
x12: 0000000000002a80 x13: 00000000ffd2d38c
x14: 00000000ffd2d5b8 x15: 0000000000000001
x16: 00000000fff7c068 x17: 00000000000000ff
x18: 00000000ffd32dd8 x19: 0000000000000000
x20: 00000000fff9f9d4 x21: 0000000000000000
x22: 0000000000000002 x23: 0000000000000021
x24: 00000000ffd37e60 x25: 00000000fffa81a9
x26: 0000000000000042 x27: 0000000000000002
x28: 00000000402dc000 x29: 00000000ffd2d310

Code: b9407fe0 1ad52363 93407c76 340006e0 (387c6ac0)
Resetting CPU ...

resetting ...&lt;/LI-CODE&gt;&lt;P&gt;Im using S32G274A RDB2 board. Linux BSP is v31.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Feb 2022 10:27:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Embedded-Software-and-Tools/Synchronous-Abort-handler/m-p/1416713#M244</guid>
      <dc:creator>st_ra</dc:creator>
      <dc:date>2022-02-21T10:27:34Z</dc:date>
    </item>
    <item>
      <title>Re: Synchronous Abort handler</title>
      <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/Synchronous-Abort-handler/m-p/1417514#M246</link>
      <description>&lt;P&gt;Found problem, had to add I2C3 and I2C4 to xRDC peripherals for A53.&lt;/P&gt;&lt;P&gt;Now Im faced with new issue, M7 core running fine, but linux gets stuck here:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[    4.036637] Waiting for root device /dev/mmcblk0p2...
[   11.067250] mmc0: Timeout waiting for hardware cmd interrupt.
[   11.067258] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[   11.067264] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00000002
[   11.067270] mmc0: sdhci: Blk size:  0x00000200 | Blk cnt:  0x00000001
[   11.067276] mmc0: sdhci: Argument:  0x00000c00 | Trn mode: 0x00000000
[   11.067282] mmc0: sdhci: Present:   0x01fd8009 | Host ctl: 0x00000001
[   11.067287] mmc0: sdhci: Power:     0x00000000 | Blk gap:  0x00000080
[   11.067292] mmc0: sdhci: Wake-up:   0x00000008 | Clock:    0x000020ff
[   11.067298] mmc0: sdhci: Timeout:   0x0000008c | Int stat: 0x00018000
[   11.067303] mmc0: sdhci: Int enab:  0x007f1003 | Sig enab: 0x007f1003
[   11.067308] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000502
[   11.067314] mmc0: sdhci: Caps:      0x07eb0000 | Caps_1:   0x8000b407
[   11.067319] mmc0: sdhci: Cmd:       0x0000341a | Max curr: 0x00ffffff
[   11.067325] mmc0: sdhci: Resp[0]:   0x00000b00 | Resp[1]:  0x0073677f
[   11.067330] mmc0: sdhci: Resp[2]:   0x325b5900 | Resp[3]:  0x00400e00
[   11.067336] mmc0: sdhci: Host ctl2: 0x00000000
[   11.067340] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[   11.067345] mmc0: sdhci-esdhc-imx: ========= ESDHC IMX DEBUG STATUS DUMP =========
[   11.067350] mmc0: sdhci-esdhc-imx: cmd debug status:  0x2100
[   11.067355] mmc0: sdhci-esdhc-imx: data debug status:  0x2200
[   11.067360] mmc0: sdhci-esdhc-imx: trans debug status:  0x2300
[   11.067366] mmc0: sdhci-esdhc-imx: dma debug status:  0x2400
[   11.067372] mmc0: sdhci-esdhc-imx: adma debug status:  0x2500
[   11.067379] mmc0: sdhci-esdhc-imx: fifo debug status:  0x2680
[   11.067385] mmc0: sdhci-esdhc-imx: async fifo debug status:  0x2750
[   11.067391] mmc0: sdhci: ============================================&lt;/LI-CODE&gt;&lt;P&gt;Any idea what could be problem? This does not happen when M7 application is not running.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Feb 2022 13:27:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Embedded-Software-and-Tools/Synchronous-Abort-handler/m-p/1417514#M246</guid>
      <dc:creator>st_ra</dc:creator>
      <dc:date>2022-02-22T13:27:55Z</dc:date>
    </item>
  </channel>
</rss>

