sel4Test development Tx1 platform
Hi All I able to build sel4Test driver for TX1 platform. but the final outputimage is not a executable image it shows as data format :~/sel4Test$ file images/sel4test-driver-image-arm-tx1.bin images/sel4test-driver-image-arm-tx1.bin: data used 'aarch64-linux-gnu-' toolchain for cross compilation. but in the kernel obj shows as 64 bit ARM aarch64 format. ~/sel4Test$ file build/kernel/kernel.o build/kernel/kernel.o: ELF 64-bit LSB relocatable, ARM aarch64, version 1 (SYSV), not stripped And cross checked in the tk1 platform the generated output file as exe file format. ~/sel4Test$ file images/sel4test-driver-image-arm-tk1 images/sel4test-driver-image-arm-tk1: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped Can you please someone help me to get final out image as executable format. Also share the procedure to load the sel4Test driver on TX1 board to verify the test. Thanks in advance Munees
Hi Muneeswaran, On the TX1, you can change the type of image that is output by the build process using the following commands: make configs/tx1_aarch64_debug_xml_defconfig make menuconfig Then, from the configuration menu, navigate through these sub-options: Tools --> Build Elfloader --> Boot image type And should be able to select "ELF boot image" from the options under that menuitem. Good luck, -- Kofi Doku Atuah Kernel engineer DATA61 | CSIRO ________________________________ From: Devel <devel-bounces@sel4.systems> on behalf of Muneeswaran Rajendran <m.rajendran@matellio.com> Sent: 07 October 2017 00:37 To: devel@sel4.systems Subject: [seL4] sel4Test development Tx1 platform Hi All I able to build sel4Test driver for TX1 platform. but the final outputimage is not a executable image it shows as data format :~/sel4Test$ file images/sel4test-driver-image-arm-tx1.bin images/sel4test-driver-image-arm-tx1.bin: data used 'aarch64-linux-gnu-' toolchain for cross compilation. but in the kernel obj shows as 64 bit ARM aarch64 format. ~/sel4Test$ file build/kernel/kernel.o build/kernel/kernel.o: ELF 64-bit LSB relocatable, ARM aarch64, version 1 (SYSV), not stripped And cross checked in the tk1 platform the generated output file as exe file format. ~/sel4Test$ file images/sel4test-driver-image-arm-tk1 images/sel4test-driver-image-arm-tk1: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped Can you please someone help me to get final out image as executable format. Also share the procedure to load the sel4Test driver on TX1 board to verify the test. Thanks in advance Munees
Hi Kofi, Thanks for valuable support to build elf kernel image and sel4 test application. Now able to build the kernel and sel4Test application for TX1 board. could you please share some write up or document to flash the sel4 kernel and run application on tx1 board Regards, Muneeswaran R On Tue, Oct 10, 2017 at 5:14 AM, <Kofidoku.Atuah@data61.csiro.au> wrote:
Hi Muneeswaran,
On the TX1, you can change the type of image that is output by the build process using the following commands:
make configs/tx1_aarch64_debug_xml_defconfig
make menuconfig
Then, from the configuration menu, navigate through these sub-options:
Tools --> Build Elfloader --> Boot image type
And should be able to select "ELF boot image" from the options under that menuitem. Good luck,
-- Kofi Doku Atuah Kernel engineer DATA61 | CSIRO
------------------------------ *From:* Devel <devel-bounces@sel4.systems> on behalf of Muneeswaran Rajendran <m.rajendran@matellio.com> *Sent:* 07 October 2017 00:37 *To:* devel@sel4.systems *Subject:* [seL4] sel4Test development Tx1 platform
Hi All
I able to build sel4Test driver for TX1 platform. but the final outputimage is not a executable image it shows as data format
:~/sel4Test$ file images/sel4test-driver-image-arm-tx1.bin images/sel4test-driver-image-arm-tx1.bin: data
used 'aarch64-linux-gnu-' toolchain for cross compilation.
but in the kernel obj shows as 64 bit ARM aarch64 format.
~/sel4Test$ file build/kernel/kernel.o build/kernel/kernel.o: ELF 64-bit LSB relocatable, ARM aarch64, version 1 (SYSV), not stripped
And cross checked in the tk1 platform the generated output file as exe file format.
~/sel4Test$ file images/sel4test-driver-image-arm-tk1 images/sel4test-driver-image-arm-tk1: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
Can you please someone help me to get final out image as executable format.
Also share the procedure to load the sel4Test driver on TX1 board to verify the test.
Thanks in advance Munees
_______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
Hi Muneeswaran, Well, about here is where we're (quickly) approaching the limits of my usefulness: I have never personally worked with the TX1 board, and I don't know how to flash a u-boot image onto it. If you're talking though, about trying to get an seL4 kernel image to run on the CPU, then that shouldn't require you to flash anything. Assuming there is already a working, viable u-boot installed on your TX1, you should be able to boot the seL4 kernel using fastboot, TFTP, or boot it from an SD card or USB flash drive. I cannot comment on which of these methods is available on your TX1 board, because again: I have no experience with the TX1 platform. But I'm pretty confident that you at least shouldn't have to flash anything to boot seL4 on your board *assuming* you already have u-boot flashed onto it. -- Kofi Doku Atuah Kernel engineer DATA61 | CSIRO
Hi Kofi, We are trying to bring the sel4 kernel on Tx1 board using SD card. The following step used to bring up sel4 kernel. 1. flash the kernel.elf as part of Root FS 2. stop the u-boot prompt and allow to boot from flashed elf image using #ext4load mmc 1 ${loadaddr} ${bootfile} but it crashed immediately with below coredump. Tegra210 (P2371-2180) # setenv bootfile kernel.elfTegra210 (P2371-2180) # ext4load mmc 1 ${loadaddr} ${bootfile}894203 bytes read in 182 ms (4.7 MiB/s)Tegra210 (P2371-2180) # bootelf ${loadaddr}# # Starting application at 0x00000000 ... "Synchronous Abort" handler, esr 0x02000000ELR: 0LR: ff135194x0 : 0000000000000001 x1 : 00000000fcc30e28x2 : 0000000000000006 x3 : 000000000000000fx4 : ffffffffffffffff x5 : 000000000000001cx6 : ffffffffffffffff x7 : 0000000000000000x8 : 0000000000000001 x9 : 0000000000000008x10: 000000000a200023 x11: 0000000000000002x12: 0000000000000002 x13: 0000000000000040x14: 0000000000000001 x15: 00000000ff12c0d0x16: 00000000ff12c3dc x17: 0000000000010000x18: 00000000fcc28df8 x19: 0000000000000000 Please share the steps followed to bring seL4 kernel on Tx1 board. Regards, Muneeswaran On Wed, Oct 11, 2017 at 10:11 AM, <Kofidoku.Atuah@data61.csiro.au> wrote:
Hi Muneeswaran,
Well, about here is where we're (quickly) approaching the limits of my usefulness: I have never personally worked with the TX1 board, and I don't know how to flash a u-boot image onto it.
If you're talking though, about trying to get an seL4 kernel image to run on the CPU, then that shouldn't require you to flash anything. Assuming there is already a working, viable u-boot installed on your TX1, you should be able to boot the seL4 kernel using fastboot, TFTP, or boot it from an SD card or USB flash drive. I cannot comment on which of these methods is available on your TX1 board, because again: I have no experience with the TX1 platform. But I'm pretty confident that you at least shouldn't have to flash anything to boot seL4 on your board *assuming* you already have u-boot flashed onto it.
-- Kofi Doku Atuah Kernel engineer DATA61 | CSIRO
_______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
Hi Muneeswaran, The steps that you are using are correct, but it looks like you are trying to boot the kernel without a user space image. Try booting a complete image file from the ./images/ directory of the project that you are using. - Alex On Wed, 2017-10-11 at 13:22 +0530, Muneeswaran Rajendran wrote:
Hi Kofi,
We are trying to bring the sel4 kernel on Tx1 board using SD card. The following step used to bring up sel4 kernel.
1. flash the kernel.elf as part of Root FS 2. stop the u-boot prompt and allow to boot from flashed elf image using #ext4load mmc 1 ${loadaddr} ${bootfile}
but it crashed immediately with below coredump.
Tegra210 (P2371-2180) # setenv bootfile kernel.elfTegra210 (P2371- 2180) # ext4load mmc 1 ${loadaddr} ${bootfile}894203 bytes read in 182 ms (4.7 MiB/s)Tegra210 (P2371-2180) # bootelf ${loadaddr}# # Starting application at 0x00000000 ... "Synchronous Abort" handler, esr 0x02000000ELR: 0LR: ff135194x0 : 0000000000000001 x1 : 00000000fcc30e28x2 : 0000000000000006 x3 : 000000000000000fx4 : ffffffffffffffff x5 : 000000000000001cx6 : ffffffffffffffff x7 : 0000000000000000x8 : 0000000000000001 x9 : 0000000000000008x10: 000000000a200023 x11: 0000000000000002x12: 0000000000000002 x13: 0000000000000040x14: 0000000000000001 x15: 00000000ff12c0d0x16: 00000000ff12c3dc x17: 0000000000010000x18: 00000000fcc28df8 x19: 0000000000000000
Please share the steps followed to bring seL4 kernel on Tx1 board.
Regards, Muneeswaran
On Wed, Oct 11, 2017 at 10:11 AM, <Kofidoku.Atuah@data61.csiro.au> wrote:
Hi Muneeswaran,
Well, about here is where we're (quickly) approaching the limits of my usefulness: I have never personally worked with the TX1 board, and I don't know how to flash a u-boot image onto it.
If you're talking though, about trying to get an seL4 kernel image to run on the CPU, then that shouldn't require you to flash anything. Assuming there is already a working, viable u- boot installed on your TX1, you should be able to boot the seL4 kernel using fastboot, TFTP, or boot it from an SD card or USB flash drive. I cannot comment on which of these methods is available on your TX1 board, because again: I have no experience with the TX1 platform. But I'm pretty confident that you at least shouldn't have to flash anything to boot seL4 on your board *assuming* you already have u-boot flashed onto it.
-- Kofi Doku Atuah Kernel engineer DATA61 | CSIRO
_______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
_______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
Hi Alex, We have used the following steps to boot sel4 userspace elf image on tx1 platform. The load address for sel4 kernel used as 0x80000000 which i got from linker.lds file. but still its crashed. I attached the tx1 kernel user space image. could you please check the attached image if any issue in the Tx1 platform. also share the sel4 log details which already running on Tx1 platform. Tegra210 (P2371-2180) # ext4load mmc 1 0x80000000 sel4test-driver-image-arm-tx1 4613056 bytes read in 357 ms (12.3 MiB/s) Tegra210 (P2371-2180) # bootelf 0x80000000 ## Starting application at 0x00000000 ... "Synchronous Abort" handler, esr 0x02000000 ELR: 0 LR: ff135194 x0 : 0000000000000001 x1 : 00000000fcc2c238 x2 : 0000000000000006 x3 : 000000000000000f x4 : ffffffffffffffff x5 : 000000000000001c x6 : ffffffffffffffff x7 : 0000000000000000 x8 : 0000000000000120 x9 : 0000000000000008 x10: 000000000a200023 x11: 0000000000000002 x12: 0000000000000002 x13: 0000000000000040 x14: 0000000000000001 x15: 00000000ff12c0d0 x16: 00000000ff12c3dc x17: 0000000000010000 x18: 00000000fcc28df8 x19: 0000000000000000 x20: 0000000000000001 x21: 00000000fcc2c238 x22: 0000000000000001 x23: 0000000000000001 x24: 00000000ff198b38 x25: 0000000000000000 x26: 0000000000000000 x27: 00000000fcc2bf70 x28: 0000000000000000 x29: 00000000fcc249f0 Regards, Munees On Thu, Oct 12, 2017 at 6:35 AM, <Alexander.Kroh@data61.csiro.au> wrote:
Hi Muneeswaran,
The steps that you are using are correct, but it looks like you are trying to boot the kernel without a user space image.
Try booting a complete image file from the ./images/ directory of the project that you are using.
- Alex
On Wed, 2017-10-11 at 13:22 +0530, Muneeswaran Rajendran wrote:
Hi Kofi,
We are trying to bring the sel4 kernel on Tx1 board using SD card. The following step used to bring up sel4 kernel.
1. flash the kernel.elf as part of Root FS 2. stop the u-boot prompt and allow to boot from flashed elf image using #ext4load mmc 1 ${loadaddr} ${bootfile}
but it crashed immediately with below coredump.
Tegra210 (P2371-2180) # setenv bootfile kernel.elfTegra210 (P2371- 2180) # ext4load mmc 1 ${loadaddr} ${bootfile}894203 bytes read in 182 ms (4.7 MiB/s)Tegra210 (P2371-2180) # bootelf ${loadaddr}# # Starting application at 0x00000000 ... "Synchronous Abort" handler, esr 0x02000000ELR: 0LR: ff135194x0 : 0000000000000001 x1 : 00000000fcc30e28x2 : 0000000000000006 x3 : 000000000000000fx4 : ffffffffffffffff x5 : 000000000000001cx6 : ffffffffffffffff x7 : 0000000000000000x8 : 0000000000000001 x9 : 0000000000000008x10: 000000000a200023 x11: 0000000000000002x12: 0000000000000002 x13: 0000000000000040x14: 0000000000000001 x15: 00000000ff12c0d0x16: 00000000ff12c3dc x17: 0000000000010000x18: 00000000fcc28df8 x19: 0000000000000000
Please share the steps followed to bring seL4 kernel on Tx1 board.
Regards, Muneeswaran
On Wed, Oct 11, 2017 at 10:11 AM, <Kofidoku.Atuah@data61.csiro.au> wrote:
Hi Muneeswaran,
Well, about here is where we're (quickly) approaching the limits of my usefulness: I have never personally worked with the TX1 board, and I don't know how to flash a u-boot image onto it.
If you're talking though, about trying to get an seL4 kernel image to run on the CPU, then that shouldn't require you to flash anything. Assuming there is already a working, viable u- boot installed on your TX1, you should be able to boot the seL4 kernel using fastboot, TFTP, or boot it from an SD card or USB flash drive. I cannot comment on which of these methods is available on your TX1 board, because again: I have no experience with the TX1 platform. But I'm pretty confident that you at least shouldn't have to flash anything to boot seL4 on your board *assuming* you already have u-boot flashed onto it.
-- Kofi Doku Atuah Kernel engineer DATA61 | CSIRO
_______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
_______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
participants (3)
-
Alexander.Kroh＠data61.csiro.au -
Kofidoku.Atuah＠data61.csiro.au -
Muneeswaran Rajendran