AnsweredAssumed Answered

Ramdisk Deployment from Flash error

Question asked by leon liu on Apr 13, 2020
Latest reply on Apr 30, 2020 by Yiping Wang

 Hi:

   I get a new t2080rdb board which is made by our company.Follow the steps in the manual,I boot it from tftp,is ok.

But when I use the same images boot from nor flash same wrong happen. I dont no why,there is my log and configuration whith the environment:

setenv and tftp images:

=> setenv ramargs 'setenv bootargs root=/dev/ram rw console=ttyS0,115200'      
=> setenv bootcmd 'run ramargs;bootm 0xe8020000 0xe9300000 0xe8800000' 

=>saveenv

 

=> tftp 100000 uImage

..............

=>tftp 2000000 fsl-image-core-t2080rdb-64b.ext2.gz.u-boot

...............

=>tftp c00000 uImage-t2080rdb.dtb

................

=>boot

error log:

Boot page (4K)000 at 0x3ffff000                                                
## Booting kernel from Legacy Image at e8020000 ...                            
   Image Name:   Linux-4.1.35-rt41                                             
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)                  
   Data Size:    5107672 Bytes = 4.9 MiB                                       
   Load Address: 00000000                                                      
   Entry Point:  00000000                                                      
   Verifying Checksum ... OK                                                   
## Loading init Ramdisk from Legacy Image at e9300000 ...                      
   Image Name:   fsl-image-core-t2080rdb-64b-2019                              
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)                 
   Data Size:    33203007 Bytes = 31.7 MiB                                     
   Load Address: 00000000                                                      
   Entry Point:  00000000                                                      
   Verifying Checksum ... OK                                                   
## Flattened Device Tree blob at e8800000                                      
   Booting using the fdt blob at 0xe8800000                                    
   Uncompressing Kernel Image ... OK                                           
   Loading Device Tree to 03fe3000, end 03fff2c0 ... OK                        
Boot page (4K)000 at 0x3ffff000                         

.

.

.

.

.

Trying to unpack rootfs image as initramfs...                                  
Unable to handle kernel paging request for data at address 0xc0000000e9300040  
Faulting instruction address: 0xc000000000aabf64                               
Oops: Kernel access of bad area, sig: 11 [#1]                                  
SMP NR_CPUS=24 CoreNet Generic                                                 
Modules linked in:                                                             
CPU: 4 PID: 1 Comm: swapper/0 Not tainted 4.1.35-rt41 #1                       
task: c000000034064b10 ti: c000000034068000 task.ti: c000000034068000          
NIP: c000000000aabf64 LR: c000000000aabef8 CTR: c00000000001ec10               
REGS: c00000003406b830 TRAP: 0300   Not tainted  (4.1.35-rt41)                 
MSR: 0000000080029000 <CE,EE,ME>  CR: 24adbe24  XER: 20000000                  
DEAR: c0000000e9300040 ESR: 0000000000000000 SOFTE: 1                          
GPR00: c000000000aabef8 c00000003406bab0 c000000000c13a00 c000000034aee000     
GPR04: c00000003fd899b8 0000000000000001 c000000000cd3a00 000000003f286000     
GPR08: 0000000000000010 0000000000000000 0000000000000000 0000000000000020     
GPR12: 0000000048adbe44 c00000003fff5b00 c0000000000021d0 0000000000000000     
GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000     
GPR20: 0000000000000000 0000000000000000 0000000000000000 c000000000b74740     
GPR24: c0000000e9300040 0000000001faa33f c000000000aed348 0000000000000000     
GPR28: c000000000af9d40 c000000000aed238 c000000000aed238 c000000000c348f0     
NIP [c000000000aabf64] .unpack_to_rootfs+0xe4/0x2e0                            
LR [c000000000aabef8] .unpack_to_rootfs+0x78/0x2e0                             
Call Trace:                                                                    
[c00000003406bab0] [c000000000aabef8] .unpack_to_rootfs+0x78/0x2e0 (unreliable)
[c00000003406bb70] [c000000000aac344] .populate_rootfs+0x88/0x154              
[c00000003406bc00] [c000000000001980] .do_one_initcall+0xb8/0x230              
[c00000003406bcf0] [c000000000aa8e28] .kernel_init_freeable+0x190/0x26c        
[c00000003406bdb0] [c0000000000021ec] .kernel_init+0x1c/0xe30                  
[c00000003406be30] [c000000000000998] .ret_from_kernel_thread+0x58/0xc0        
Instruction dump:                                                              
39400000 f93e0020 915e0028 7fddf378 f93e0000 3b600000 3b5e0110 e93e0000        
2fa90000 409e014c 2fb90000 419e0144 <89380000> ebfd0020 2b890030 40be0028      
---[ end trace 3d554be113db4815 ]---                                           
                                                                               
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b        
                                                                               
Rebooting in 180 seconds..         

 

Any body know why?

 

 

Outcomes