cross-compiling the thing without VFT resolves the issue.
..
ELF-loader started on CPU: ARM Ltd. Cortex-A15 r2p4
paddr=[8200..8248841f]
ELF-loading image 'kernel'
paddr=[8000..8002]
vaddr=[f000..f002]
virt_entry=f000
ELF-loading image 'sel4test-driver'
Hi Alex,
> Regardless, seL4 does not support it.
ignore my last mail - just saw you pointed to the fact that sel4
doesn't support VFT.
But I am still wondering about cross compiling the project -
Is it enough to set CONFIG_KERNEL_CFLAGS and CONFIG_USER_CFLAGS ?
> The appropriate args should be
Hi Alex,
I've checked how a working Linux image looks like and it seems it is
compiled with
$ arm-cortexa15-linux-gnueabihf-readelf -A -n vmlinux
..
Tag_CPU_name: "7-A"
Tag_CPU_arch: v7
Tag_CPU_arch_profile: Application
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-2
Tag_FP_arch:
I attached the Lauterbach and it seems when executing elf_getMemoryBounds()
it jumps to invalid memory region when initializing
uint64_t mem_min = UINT64_MAX;
Disassembled it seems it happens when executing this instruction:
vmov.64 d16,0x
Does somebody has an idea whats going
Hello,
I am trying to integrate TI Keystone 2 platform to seL4.
What I have done so far is basically an initial port of the
Kernel/libs/elfloader/Platform components
and introducing a new keystone defconfig.
Relevant config parts about the setup:
CONFIG_ARCH_ARM_V7A=y
CONFIG_ARCH_ARM=y
