Hi Parvaneh, > I am trying to have my own seL4 demo on Sabre Lite board. > I am using this command to create the image file: > ../init-build.sh -DPLATFORM=sabre -DCROSS_COMPILER_PREFIX=arm-linux- > gnueabi- -DCAMKES_APP=adder > > ... > > ELF-loader started on CPU: ARM Ltd. Cortex-A9 r2p10 > paddr=[10598000..1080a037] > No DTB passed in from boot loader. > Looking for DTB in CPIO archive...found at 1069c064. > Loaded DTB from 1069c064. > paddr=[10038000..10042fff] > ELF-loading image 'kernel' > paddr=[10000000..10037fff] > vaddr=[e0000000..e0037fff] > virt_entry=e0000000 > ELF-loading image 'capdl-loader' > paddr=[10043000..1019bfff] > vaddr=[10000..168fff] > virt_entry=188dc > ELF loader relocated, continuing boot... > Enabling MMU and paging > > It seems It does not go to kernel-image entry point and bootstrap the > kernel! > Is there any thing that I need to perform on board?
The last message "Jumping to kernel-image entry point..." gets printed if the kernel's virtual mapping doesn't overlap with the UART device's register mapping, but this is usually fine most of the time. It could be that the serial output is being buffered? The other reason why you don't receive serial output could be because the build is configured in release mode. Running the 'init-build.sh' command in a build directory that was configured to be in release mode will also result in the new build being in release mode. The adder application doesn't include a serial driver CAmkES component, so there is no serial output on release mode. The recommendations are just basic smoke tests, and if there are still problems after this, we'll be happy to help. Sincerely, Damon _______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
