<?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>LayerscapeのトピックRe: LS1043A Custom Board Bring up  using ATF</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1043A-Custom-Board-Bring-up-using-ATF/m-p/1757355#M13649</link>
    <description>&lt;P&gt;Please refer to document&amp;nbsp;&lt;A href="https://community.nxp.com/t5/Layerscape-Knowledge-Base/Debugging-ATF-and-u-boot-with-CodeWarrior-for-ARMv8/ta-p/1684233" target="_blank"&gt;https://community.nxp.com/t5/Layerscape-Knowledge-Base/Debugging-ATF-and-u-boot-with-CodeWarrior-for-ARMv8/ta-p/1684233&lt;/A&gt;&amp;nbsp;to debug atf and u-boot with CodeWarrior.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Probably the "Inspect(attaching to the running target)" will help the customer. Please refer to the Inspect icon marked red in attached file inspect.png. After click this icon, CodeWarrior will attach to the target board, not affect the software running on the target board.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Then the disassembly code which the target board is executing will be captured and displayed in CodeWarrior IDE, please refer to the attached file disassemble.png.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I consider you could use "Inspect" button to get the address where the system stuck.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Then use the above document to debug BL31 or u-boot.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 15 Nov 2023 06:45:58 GMT</pubDate>
    <dc:creator>yipingwang</dc:creator>
    <dc:date>2023-11-15T06:45:58Z</dc:date>
    <item>
      <title>LS1043A Custom Board Bring up  using ATF</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043A-Custom-Board-Bring-up-using-ATF/m-p/1755844#M13623</link>
      <description>&lt;P&gt;Hi Expert,&lt;BR /&gt;we built bl2_nor.pbl and fip.bin using ATF firmware for ls1043a custom Board LS1043AXE8QQB.&lt;BR /&gt;On power on the Serial port putty log is stopping near BL33 (i.e U-boot). I am sharing the log.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;INFO: SMMU Cache Unlocking is Configured.&lt;BR /&gt;INFO: SoC workaround for Errata A008850 Early-Phase was applied&lt;BR /&gt;INFO: SoC workaround for Errata A009660 was applied&lt;BR /&gt;INFO: SoC workaround for Errata A010539 was applied&lt;BR /&gt;INFO: RCW BOOT SRC is IFC NOR&lt;BR /&gt;INFO: SoC workaround for DDR Errata A009942 was applied&lt;BR /&gt;INFO: platform clock 400000000&lt;BR /&gt;INFO: DDR PLL1 1600000000&lt;BR /&gt;INFO: DDR PLL2 400000000&lt;BR /&gt;in ddr_init file befoer dram_init 1600000000&lt;BR /&gt;in ddr.c file dram_init&lt;BR /&gt;in ddr.c file before board_static_ddr&lt;BR /&gt;INFO: Time before programming controller 6 ms&lt;BR /&gt;INFO: Program controller registers&lt;BR /&gt;in ddrc.c ,ddrc_set_regs for mod_bnds 0&lt;BR /&gt;in ddrc.c ,after ddr cs config&lt;BR /&gt;in ddrc.c ,after ddr timing and dqmap config&lt;BR /&gt;in ddrc.c ,after sdram_mode_16config&lt;BR /&gt;in ddrc.c 1ERRATA_DDR_A009663 regs-&amp;gt;interval&lt;BR /&gt;in ddrc.c ,after wrlvl_cntl&lt;BR /&gt;in ddrc.c ,after init_ext_addr&lt;BR /&gt;in ddrc.c ,get_ddrc_version 0x50102&lt;BR /&gt;in ddrc.c ,debug 0x0&lt;BR /&gt;in ddrc.c ,after address decoding mod_bnds&lt;BR /&gt;in ddrc.c ,A009942 debug[28] 0x70006f&lt;BR /&gt;sdram_cfg bus_width 2&lt;BR /&gt;timeout using bus_width&amp;amp; total_mem_per_ctrl_adj64 , 1&lt;BR /&gt;INFO: total size 1 GB&lt;BR /&gt;INFO: Need to wait up to 640 ms&lt;BR /&gt;ddr bus width 0x2, sdram_cfg[0] 0x450c0000 ,temp 0x1&lt;BR /&gt;INFO: Reading debug[9] as 0x1a001b00&lt;BR /&gt;INFO: Reading debug[10] as 0x1e001f00&lt;BR /&gt;INFO: cpo_min 0x1a&lt;BR /&gt;INFO: cpo_max 0x1f&lt;BR /&gt;INFO: debug[28] 0x700046&lt;BR /&gt;INFO: Optimal cpo_sample 0x43&lt;BR /&gt;INFO: Found : 0x2&lt;BR /&gt;INFO: get_ddrc_version : 0x50102&lt;BR /&gt;INFO: Running built-in self test ...&lt;BR /&gt;INFO: Wait up to 1600 ms&lt;BR /&gt;INFO: Timer remains 115&lt;BR /&gt;NOTICE: Build-in self test passed&lt;BR /&gt;INFO: *0x1080000 = 0x3f&lt;BR /&gt;INFO: *0x1080080 = 0x80040312&lt;BR /&gt;INFO: *0x1080100 = 0x10c1000&lt;BR /&gt;INFO: *0x1080104 = 0x91550018&lt;BR /&gt;INFO: *0x1080108 = 0xbbb48c42&lt;BR /&gt;INFO: *0x108010c = 0x48c111&lt;BR /&gt;INFO: *0x1080110 = 0xc50c0000&lt;BR /&gt;INFO: *0x1080114 = 0x401100&lt;BR /&gt;INFO: *0x1080118 = 0x3010210&lt;BR /&gt;INFO: *0x1080120 = 0x600041f&lt;BR /&gt;INFO: *0x1080124 = 0x18600618&lt;BR /&gt;INFO: *0x1080128 = 0xdeadbeef&lt;BR /&gt;INFO: *0x1080130 = 0x3000000&lt;BR /&gt;INFO: *0x1080160 = 0x2&lt;BR /&gt;INFO: *0x1080164 = 0x3401400&lt;BR /&gt;INFO: *0x108016c = 0x13300000&lt;BR /&gt;INFO: *0x1080170 = 0x8a090705&lt;BR /&gt;INFO: *0x1080174 = 0xc675f607&lt;BR /&gt;INFO: *0x1080190 = 0x7090807&lt;BR /&gt;INFO: *0x1080194 = 0x7070707&lt;BR /&gt;INFO: *0x1080220 = 0x500&lt;BR /&gt;INFO: *0x1080224 = 0x4000000&lt;BR /&gt;INFO: *0x1080250 = 0x2115600&lt;BR /&gt;INFO: *0x1080280 = 0xeed7ee12&lt;BR /&gt;INFO: *0x1080284 = 0x11281121&lt;BR /&gt;INFO: *0x1080288 = 0xffffff02&lt;BR /&gt;INFO: *0x108028c = 0xff&lt;BR /&gt;INFO: *0x1080290 = 0xffff0001&lt;BR /&gt;INFO: *0x1080400 = 0x5b656240&lt;BR /&gt;INFO: *0x1080404 = 0xa95d8000&lt;BR /&gt;INFO: *0x1080b20 = 0x8080&lt;BR /&gt;INFO: *0x1080b24 = 0x80000000&lt;BR /&gt;INFO: *0x1080b28 = 0x80040000&lt;BR /&gt;INFO: *0x1080b2c = 0xa181&lt;BR /&gt;INFO: *0x1080bf8 = 0x20501&lt;BR /&gt;INFO: *0x1080bfc = 0x200&lt;BR /&gt;INFO: *0x1080d00 = 0x60000&lt;BR /&gt;INFO: *0x1080d20 = 0xffffffff&lt;BR /&gt;INFO: *0x1080d28 = 0xaaaaaaaa&lt;BR /&gt;INFO: *0x1080d2c = 0x55555555&lt;BR /&gt;INFO: *0x1080d30 = 0xcccccccc&lt;BR /&gt;INFO: *0x1080d34 = 0x33333333&lt;BR /&gt;INFO: *0x1080d38 = 0x12345678&lt;BR /&gt;INFO: *0x1080d3c = 0xabcdef01&lt;BR /&gt;INFO: *0x1080d40 = 0xaa55aa55&lt;BR /&gt;INFO: *0x1080d44 = 0x55aa55aa&lt;BR /&gt;INFO: *0x1080f04 = 0x2&lt;BR /&gt;INFO: *0x1080f08 = 0xb&lt;BR /&gt;INFO: *0x1080f0c = 0x14000c20&lt;BR /&gt;INFO: *0x1080f24 = 0x1a001b00&lt;BR /&gt;INFO: *0x1080f28 = 0x1e001f00&lt;BR /&gt;INFO: *0x1080f34 = 0x3000&lt;BR /&gt;INFO: *0x1080f48 = 0x1&lt;BR /&gt;INFO: *0x1080f4c = 0xd4000000&lt;BR /&gt;INFO: *0x1080f50 = 0xd000d00&lt;BR /&gt;INFO: *0x1080f54 = 0xf000f00&lt;BR /&gt;INFO: *0x1080f58 = 0xe000e00&lt;BR /&gt;INFO: *0x1080f5c = 0xe000e00&lt;BR /&gt;INFO: *0x1080f60 = 0xe000000&lt;BR /&gt;INFO: *0x1080f70 = 0x700046&lt;BR /&gt;INFO: *0x1080f9c = 0x13001400&lt;BR /&gt;INFO: *0x1080fa0 = 0x13001300&lt;BR /&gt;INFO: *0x1080fa4 = 0x1000100&lt;BR /&gt;INFO: *0x1080fa8 = 0x1000100&lt;BR /&gt;INFO: *0x1080fac = 0x1000000&lt;BR /&gt;INFO: *0x1080fb0 = 0x3&lt;BR /&gt;INFO: *0x1080fb4 = 0xf0e0d0f&lt;BR /&gt;INFO: *0x1080fb8 = 0xe0e0e0d&lt;BR /&gt;INFO: *0x1080fbc = 0xf0e0e11&lt;BR /&gt;INFO: *0x1080fc0 = 0xf0f0f0e&lt;BR /&gt;INFO: *0x1080fc4 = 0xf0e0d0f&lt;BR /&gt;INFO: *0x1080fc8 = 0xe0e0e0d&lt;BR /&gt;INFO: *0x1080fcc = 0xf0f0e10&lt;BR /&gt;INFO: *0x1080fd0 = 0xe0e0f0f&lt;BR /&gt;INFO: *0x1080fd4 = 0xf0f0f0f&lt;BR /&gt;INFO: *0x1080fd8 = 0xf0f0f0f&lt;BR /&gt;INFO: *0x1080fdc = 0xf0f0f0f&lt;BR /&gt;INFO: *0x1080fe0 = 0xf0f0f0f&lt;BR /&gt;INFO: *0x1080fe4 = 0xf0f0f0f&lt;BR /&gt;INFO: *0x1080fe8 = 0xf0f0f0f&lt;BR /&gt;INFO: *0x1080fec = 0xf0f0f0f&lt;BR /&gt;INFO: *0x1080ff0 = 0xf0f0f0f&lt;BR /&gt;INFO: *0x1080ff4 = 0xf0f0f0f&lt;BR /&gt;INFO: *0x1080ff8 = 0xf0f0f0f&lt;/P&gt;&lt;P&gt;NOTICE: 1 GB DDR4, 32-bit, CL=11, ECC off&lt;BR /&gt;INFO: Time used by DDR driver 1003 ms&lt;BR /&gt;INFO: SoC workaround for Errata A008850 Post-Phase was applied&lt;BR /&gt;INFO: RCW BOOT SRC is IFC NOR&lt;BR /&gt;NOTICE: BL2: v2.6(release):lf-5.15.71-2.2.0-0-g3c1583ba0-dirty&lt;BR /&gt;NOTICE: BL2: Built : 11:00:38, Nov 21 2022&lt;BR /&gt;INFO: BL2: Doing platform setup&lt;BR /&gt;INFO: BL2: bl2_plat_handle_pre_image_load&lt;BR /&gt;INFO: BL2: bl2_plat_handle_pre_image_load&lt;BR /&gt;INFO: BL2: Loading image id 3&lt;BR /&gt;INFO: Loading image id=3 at address 0xbbe00000&lt;BR /&gt;INFO: Image id=3 loaded: 0xbbe00000 - 0xbbe0e62d&lt;BR /&gt;INFO: BL2: bl2_plat_handle_pre_image_load&lt;BR /&gt;INFO: BL2: bl2_plat_handle_pre_image_load&lt;BR /&gt;INFO: BL2: Loading image id 5&lt;BR /&gt;INFO: Loading image id=5 at address 0x82000000&lt;BR /&gt;INFO: Image id=5 loaded: 0x82000000 - 0x8209db98&lt;BR /&gt;NOTICE: BL2: Booting BL31&lt;BR /&gt;INFO: Entry point address = 0xbbe00000&lt;BR /&gt;INFO: SPSR = 0x3cd&lt;BR /&gt;NOTICE: BL31: v2.6(release):lf-5.15.71-2.2.0-0-g3c1583ba0-dirty&lt;BR /&gt;NOTICE: BL31: Built : 11:00:38, Nov 21 2022&lt;BR /&gt;NOTICE: Welcome to ls1043ardb BL31 Phase&lt;BR /&gt;INFO: ARM GICv2 driver initialized&lt;BR /&gt;INFO: BL31: Initializing runtime services&lt;BR /&gt;INFO: BL31: Preparing for EL3 exit to normal world&lt;BR /&gt;INFO: Entry point address = 0x82000000&lt;BR /&gt;INFO: SPSR = 0x3c9&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here it Entering in to&amp;nbsp;&amp;nbsp;Entry point address = 0x82000000 but it's not accessing&amp;nbsp; BL33( i.e u-boot).&lt;/P&gt;&lt;P&gt;What might be the Problem we are not Understanding whether TF-A build Problem or U-boot problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 11 Nov 2023 11:35:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043A-Custom-Board-Bring-up-using-ATF/m-p/1755844#M13623</guid>
      <dc:creator>perumandlasairam1064</dc:creator>
      <dc:date>2023-11-11T11:35:26Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043A Custom Board Bring up  using ATF</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043A-Custom-Board-Bring-up-using-ATF/m-p/1757355#M13649</link>
      <description>&lt;P&gt;Please refer to document&amp;nbsp;&lt;A href="https://community.nxp.com/t5/Layerscape-Knowledge-Base/Debugging-ATF-and-u-boot-with-CodeWarrior-for-ARMv8/ta-p/1684233" target="_blank"&gt;https://community.nxp.com/t5/Layerscape-Knowledge-Base/Debugging-ATF-and-u-boot-with-CodeWarrior-for-ARMv8/ta-p/1684233&lt;/A&gt;&amp;nbsp;to debug atf and u-boot with CodeWarrior.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Probably the "Inspect(attaching to the running target)" will help the customer. Please refer to the Inspect icon marked red in attached file inspect.png. After click this icon, CodeWarrior will attach to the target board, not affect the software running on the target board.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Then the disassembly code which the target board is executing will be captured and displayed in CodeWarrior IDE, please refer to the attached file disassemble.png.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I consider you could use "Inspect" button to get the address where the system stuck.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Then use the above document to debug BL31 or u-boot.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 06:45:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043A-Custom-Board-Bring-up-using-ATF/m-p/1757355#M13649</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-11-15T06:45:58Z</dc:date>
    </item>
  </channel>
</rss>

