2170205_en-US

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

2170205_en-US

2170205_en-US

T2080 Custom board booting from SPI NOR flash

Trying to boot the custom T2080 board from the SPI NOR flash

I was able to load the custom RCW bin file into the Serial NOR flash using the Flash Programmer in the CW IDE but not able to read the RCW words in the CCSR_RCWSR registers(for confirmation) after the board is powered on with the SPI boot mode.

Can anyone help, how to boot the board using SPI NOR flash?

Thank you..

Re: T2080 Custom board booting from SPI NOR flash

You need to port u-boot source code.

Would you please create a new thread to address your new problem?

Re: T2080 Custom board booting from SPI NOR flash

Hi,


We have loaded the u-boot-with-spl-pbl.bin generated by modifying the RCW words with our custom RCW words in QorIQ SDKv2.0, getting error as "Failed to reset the Target(T2080 core not responding)" and no uart console messages

what is the offset address to load the file in SPI NOR flash??

is it the right way to directly load the u-boot-with-spl-pbl.bin file of T2080RDB with just RCW changes??  if no, what are the major modifications to be done in the u-boot source to boot the device from the SPI NOR flash...please guide



Regards,

Priya

Re: T2080 Custom board booting from SPI NOR flashWe configured the RCW words according to our custom board specifications with the help of T2080 reference manual. Now we are able to execute the given commands successfully without any error.

Thanks a lot for the support.
Re: T2080 Custom board booting from SPI NOR flash

Please refer to the following RCW which I dump from pre-built SPI u-boot image.

00000000: aa55 aa55 010e 0100 1207 001b 1500 0000 .U.U............
00000010: 0000 0000 0000 0000 6615 0002 0000 0000 ........f.......
00000020: e810 4000 c100 0000 0080 0000 0000 0000 ..@.............
00000030: 0000 0000 0003 07fc 0000 0000 0000 0000 ................
00000040: 0000 0000 0000 0004 0901 0000 0020 0400 ............. ..

Re: T2080 Custom board booting from SPI NOR flash

Please refer to "Figure 4-1. Power-on reset sequence" in T2080RM, please check whether you waveform is the same as it. If no, it means there is problem with the content of your RCW. Because as you mentioned you can read the RCW status registers which is getting reflected according to the RCW words loaded into it.

Please modify your RCW based on the following RCW of T2080RDB.

#For T2080 v1.1

#SerDes=0x66_0x15, Core:1800MHz, DDR:1600MT/s

#1206001b 15000000 00000000 00000000


#SerDes=0x66_0x15, Core:1800MHz, DDR:1867MT/s

1207001b 15000000 00000000 00000000

66150002 00000000 58104000 c1000000

00800000 00000000 00000000 000307fc

00000000 00000000 00000000 00000004

Re: T2080 Custom board booting from SPI NOR flash

In Hard-coded RCW mode, we are able to execute the CCS commands successfully without any error.

And in SPI boot mode, PORESET_B de-assertion, HRESET_B is de-assertion is happening and the ASLEEP signal is also low but still getting the error as "T2080: Core not responding" in CCS

Can you please say what might be the reasons for it??

Re: T2080 Custom board booting from SPI NOR flash

When you power on in SPI boot mode, the RCW (Reset Configuration Words) should be fetched automatically by the PBL (Pre-Boot Loader) from your SPI NOR. If you don’t see the expected values in CCSR_RCWSR, a few common issues are worth checking:

  1. RCW alignment & size – Make sure the RCW binary is placed at the correct offset in SPI NOR (usually address 0x00000000 for boot). Any misalignment will cause the PBL to fall back or hang.

  2. SPI configuration straps – Verify your board’s reset configuration pins/straps are actually set for SPI NOR boot. If they default to another boot source, the RCW won’t be read from NOR.

  3. RCW validity – Double-check the endianness and CRC. An invalid RCW image will be ignored, and the device may not update CCSR_RCWSR.

  4. Clock/voltage stability – The T2080 is sensitive to clock and reset timing during PBL fetch. If the oscillator or power rails are not stable before RCW fetch, the read may fail.

In practice, a good test is to dump the contents of your SPI NOR via JTAG/CodeWarrior and confirm the RCW words at offset 0x0 match your expectations. If they do, then the problem is likely with boot mode straps or RCW validity rather than flash programming itself.

I had a very similar issue on a custom board and documented the debugging steps in more detail here:  — walking through placement, strap checks, and validation. Might help you compare against your setup.

Re: T2080 Custom board booting from SPI NOR flash

Please configure your custom board as hard-coded RCW mode, and check whether you could execute the CCS commands successfully.

If yes, please configure your custom board booting from SPI NOR flash, and check the following.

After PORESET_B de-assertion, HRESET_B is de-asserted (indicating RCW is loaded successfully) and ASLEEP signal should be low (indicating PBI is loaded successfully).

Re: T2080 Custom board booting from SPI NOR flash

Configured the target board to SPI boot mode and while executing the given commands in ccs getting error as "T2080: Core not responding" 

Now I'm able to read the RCW status registers which is getting reflected according to the RCW words loaded into it.

error.png

The rcw words loaded are
00000000: aa55aa55 010e0100 0a08000c 0c000000
00000010: 00000000 00000000 1c190000 0053ac00
00000020: 58045000 41000000 00300000 00000000
00000030: 00000000 00000000 00000000 5280000d
00000040: 00000000 00000001 08138040 65e0e49c

Kindly verify the RCW words to resolve the error

Re: T2080 Custom board booting from SPI NOR flash

Please configure the target board boot from SPI NOR flash.

Then open CCS from C:\Freescale\CW_PA_v10.5.1\PA\ccs\ccs\bin\ccs.exe and type the following commands to do verification.

% delete all

% config cc cwtap

% ccs::config_chain t2080

% ccs::reset_to_debug

If there is error returned, it means there is problem with your RCW, you need to refine the RCW configuration.

タグ(1)
評価なし
バージョン履歴
最終更新日:
‎11-21-2025 06:34 AM
更新者: