Boot failure after compiling the kernel

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.1.10844
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Hi Sir
About (Compiling the Kernel (NVIDIA DRIVE OS Linux) | NVIDIA Docs)

We compiled the kernel according to this doc without any modifications, and Orin started normally after compiling and using sdkmanager to flash the target,target can start normally

But modify a little something,eg. turn on the CONFIG_KPROBE_EVENTS option, compile and flash it and it won’t boot up. The boot log stops here:

pl:[I]: Loading DTB image
pl:[I]: BCH SHA512 digest verification successful
pl:[I]: PVIT entry found and SHA is matching
pl:[I]: Ignoring Reserved Memory value 0x0
pl:[I]: Added mpidr: 0x10000 to  cpu-0 node in FDT
pl:[I]: Added mpidr: 0x10100 to  cpu-1 node in FDT
pl:[I]: Added mpidr: 0x10200 to  cpu-2 node in FDT
pl:[I]: Added mpidr: 0x10300 to  cpu-3 node in FDT
pl:[I]: Added mpidr: 0x20000 to  cpu-4 node in FDT
pl:[I]: Added mpidr: 0x20100 to  cpu-5 node in FDT
pl:[I]: Added mpidr: 0x20200 to  cpu-6 node in FDT
pl:[I]: Added mpidr: 0x20300 to  cpu-7 node in FDT
pl:[I]: Added mpidr: 0x100 to  cpu-8 node in FDT
pl:[I]: Added mpidr: 0x200 to  cpu-9 node in FDT
pl:[I]: Added mpidr: 0x0 to  cpu-10 node in FDT
pl:[I]: Added mpidr: 0x300 to  cpu-11 node in FDT
pl:[I]: CARVEOUT_FSI_CPU_NS base(0x7fe17d0000) size(0x1000000)
pl:[I]: total mac_address 10
pl:[E]: Unable to find /smmu-static-mapping node : FDT_ERR_NOTFOUND
pl:[E]: Function: set_prop_print_err(0xff001525c) Error: FileNotFound (0x30013)
pl:[I]: Kernel Cmdline: aurixfw=AFW root=/dev/vblkdev0p1 ip=off loglevel=3 usr_fs=/dev/vblkdev1:/mnt/persistent/metadata usr_fs2=/dev/vblkdev3:/mnt/persistent/data ufs_fs=/dev/vblkdev2 gpt rootwait rw g0
pl:[I]: jumping to kernel at 0x80200000 (virtual 0x80000000)


Fatal programming error:
  Unknown System Register Emulation: 0x623008e2
�����Error Report to CcplexApp failed 
fatal error no data cpu:0 err:-4 
fatal error no data cpu:1 err:-4 
fatal error no data cpu:2 err:-4 
fatal error no data cpu:3 err:-4 
fatal error cpu:4
fatal error no data cpu:5 err:-4 
fatal error no data cpu:6 err:-4 
fatal error no data cpu:7 err:-4 
fatal error no data cpu:8 err:-4 
fatal error no data cpu:9 err:-4 
fatal error no data cpu:10 err:-4 
fatal error no data cpu:11 err:-4 
process non fatal 

Time taken from Error Reporting to SEH: 1181800 microseconds
DemoApp: ErrCode-0x1116000 ReptrId-0x7953 ErrAttr-0x20
EPS TimeStamp: 0x6e6b6e55
process qm error 
E2E is initialized
========INFO: w/o TCM translation in App==========

SRAM(0x510890c0)->SRAM(0x51089280)
callback called:
DMA transfer verified

SRAM(0x510890c0)->BTCM(0x40400)
callback called:
DMA transfer verified

SRAM->BTCM->SRAM:(0x510890c0->0x40400->0x51089280)
DMA transfer verified for 0x510890c0 & 0x51089280
SHA3_256 test success!
SHA3_512 test success!
SHA3_384 test success!
AES-CMAC GENERATE/VERIFY test success!
ED25519 SIGN GENERATE/VERIFY test success!
ED25519 PreHash SIGN GENERATE/VERIFY test success!
CBC ENCRYPT/DECRYPT test success!
GCM ENCRYPT/DECRYPT test success!
GMAC GENERATE/VERIFY test success!
KEY GENERATE test success!
RAND test success!
KEY EXCHANGE test success!
SHA1 test success!
SHA224 test success!
SHA384 test success!
SHA512_224 test success!
SHA512_256 test success!
SHA3_224 test success!
SHA Async test success!
RSA test success!
KEY COPY test success!

CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.7.1 | VT102 | Offline | ttyACM0                                                                     

I have three questions:
1.Do I have to use the Bootburn tool to flash after compiling the kernel?Does sdkmanager call Bootburn?
2.My device is p3710-0010, what command should I use to flash the kernel with Bootburn tool?
3.What causes the system boot log to stop here?What I should do?

Thanks very much!

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

Dear @zhangjm,
Could you share complete details of modification, compile and flash steps?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.