u-boot on custom T1024 board

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

u-boot on custom T1024 board

1,173 Views
rdk
Contributor I

Hi,

We have developed a custom board base on the T1024. The CPU boots from an SPI memory, the SPI is programmed with the following binaries :

  • u-boot 2016.09 binary @ offset 0x000000 of the SPI flash
  • fsl_fman_ucode_t1024_r1.0_106_4_18 binary @ offset 0x1100000 of the SPI flash
  • iram_Type_A_T1024_r1.0.bin binary @ offset 0x130000 of the SPI flash.

The RAM memory is soldered on the board, it is DDR3L (MT41K256M16) chip. We have implemented 4 chip to have 2GB of memory. Since we did not implement any SPD eeprom I have put a static configuration in board/freescale/t102xrdb/ddr.c and I have update the include/configs/T102xRDB.h with CONFIG_SYS_DDR_RAW_TIMING in order for the static configuration to be taken into account.

The RCW has the following value:

0810000a 00000000 00000000 00000000

2d000002 00008112 58115000 21000000

00000000 00000000 00000000 00035000

00000000 49260a08 00000000 00000006

On the IFC we have 2 components, a NAND flash used as mass storage for the Linux os and an FPGA for custom logic implementation.

When starting the CPU correctly loads the RCW and starts the first stage boot loader. Then the second stage boot loader is loaded into RAM. U-boot crashes when the second stage. Here under is the traces of the crash :

SPI boot...
WARNING: Calling __hwconfig without a buffer and before environment is ready
WARNING: Calling __hwconfig without a buffer and before environment is ready
WARNING: Calling __hwconfig without a buffer and before environment is ready
Loading second stage boot loader .................................................................................................Bad trap at PC: 30000004, SR: 21200, vector=800
NIP: 30000004 XER: 00000000 LR: FFFE4A98 REGS: 00000110 TRAP: 0800 DAR: 00000000
MSR: 00021200 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00

GPR00: FFFE4A78 00000200 FFFC8000 300BFFFF 000BFFFF FFFCB150 FFFCB150 FFFCB140  
GPR08: 00000000 30000000 30000000 FFFD7FC0 FFFE39FC 00008000 00000000 0C000000  
GPR16: 00000000 08000000 000E0000 04000000 08028000 00000000 00000000 24000000  
GPR24: 00000000 00000000 00008000 08000000 00102000 FFFCB100 FFFE8E9C 00102000  
Call backtrace:  
FFFF0000 00001000 00002000 FFFF0040 00000000  
Exception in kernel pc 30000004 signal 0
### ERROR ### Please RESET the board ###

I have two questions : 

- How can I analysed the above stack trace in order to know where the problem could be ?

- Since we do not have any NOR memory on our board how can remove it from t1024rdb sources code ?

Thanks in advance,

Renaud De Koninck

Labels (1)
0 Kudos
2 Replies

1,106 Views
rdk
Contributor I

Hi,

Thanks for the reply and the CONFIG_SYS_NO_FLASH tips.

Unfortunately I do not have access to a Codewarior environment neither jtag probe.

Anyway after days of reads and tries we finally got a result with a functional u-boot.

For the sake of history this post was the key to start up our board https://community.nxp.com/message/658620?commentID=658620#comment-658620 

Renaud De Koninck

0 Kudos

1,106 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Renaud De Koninck,

1. You could use CodeWarrior to debug your u-boot on the custom board, please refer to section "10. Debugging U-Boot from SPI/SD/MMC for e500mc" in CodeWarrior U-Boot Debugging .

2. Please define macro CONFIG_SYS_NO_FLASH in include/configs/T102xRDB.h.

Thanks,

Yiping

0 Kudos