Hello,
I wrote a new timer driver for this timer device:
http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf
I am already able to run the seL4 testsuite successfully,
except the interrupt/timer tests.
It waits forever @ wait_for_timer_interrupt(env);
I've uploaded the driver temporary to:
https://github.com/wwladikw/devel/blob/master/timer.c
Any idea what could be wrong?
I am able to run the timer periodically or as oneshot.
The gic_390 interrupt driver in the kernel should also be compatible
with the gic_400, for my understanding, right?
The SoC I am using contains a Coretex A15.
Thanks a lot in advance!
Wladislav Wiebe
I am trying to boot CAmkES-ARM-VM and got problem in elfloader. I tested
Jetson-TK1 and TK1-SOM. The results are same. I've set
bootm_boot_mode=nonsec in u-boot and tracked registers in function
switch_to_hyp_mode().
1) Enter switch_to_hyp_mode(), after
asm volatile ("mrc p15, 0, %0, c1, c1, 0":"=r"(scr));
==>
scr == 0x100, in which NS==0, HCE==1, SCD==0, SIF==0
2) Then switch_to_hyp_mode() changes NS to 1, so scr==0x101
asm volatile ("mcr p15, 0, %0, c1, c1, 0"::"r"(scr));
3) switch_to_hyp_mode() changes cpsr to Hyp mode
asm volatile ("cps %0\n\t"
"isb\n"
::"I"(HYPERVISOR_MODE));
4) The final step, switch_to_hyp_mode() reads cpsr,
asm volatile ("mrs %0, cpsr":"=r"(scr));
==>
scr == 0x6000001da, in which cpsr.M==0x1a, cpsr.I==1, cpsr.F==1, cpsr.A==1
Finally, the process died here.
My questions are,
1) Are NS==0 and HCE==1 correct when entering switch_to_hyp_mode() ?
2) Is the final status (cpsr.F==cpsr.I==cpsr.A==1) expected?
3) Any other mistake I might make?
Yao
It seems to be necessary for me to use the debug output using a serial cable on UART0
u-boot seems to be waiting for a Ethernet or serial cable connection to finish boot process.
I don't have the serial cable so I just need some understanding that that is the case considering that I followed the rest of the instructions on the blog at https://research.csiro.au/tsblog/sel4-raspberry-pi-3/
, newbie question btw.
Hi,
Could you tell me why did you not implement domains in RT kernel version? Are there any difficulties? I'm going to add support of domains, and at the first sight I don't see any difficulties.
Hello,
https://wiki.sel4.systems/Hardware
On this seL4wiki hardware page I find the link of Zynq7000 turns grey, and the page says "This page does not exist yet. You can create a new empty page, or use one of the page templates."
So it means seL4 do not support zynq7000 any more?
And how can I run seL4/seL4test on zynq7000 board?
Thanks!
Hello,
I've just got my odroid-xu4 board and tried to port seL4test onto it, but met some problems that cannot procceed. Do you have any guide or tutorial for it step by step? I think I may have problem of initializing and partitioning of a new sd card(main problem?). And maybe something is wrong with the uboot or fastboot, but I'm not quite sure about that.
This is my fist time using this devel, don't know whether this message was sent correctly or not :)
Looking forward to get some help by you guys.
Thanks!
Wang
Hello,
I've just got my odroid-xu4 board and tried to port seL4test onto it, but met some problems that cannot procceed. Do you have any guide or tutorial for it step by step? I think I may have problem of initializing and partitioning of a new sd card(main problem?). And maybe something is wrong with the uboot or fastboot, but I'm not quite sure about that.
This is my fist time using this devel, don't know whether this message was sent correctly or not :)
Looking forward to get some help by you guys.
Thanks!
Wang
Based on the seL4 manual it sounds like IRQControl caps only support
one level of derivation. What is the reason for this restriction? We
encountered a case where we wanted to hand out an IRQControl for a
specific irq and then later revoke access, but we couldn't do it
because the IRQControl for a specific irq is already a derived
capability.
-Andrew
Hello,
I am using the i.mx6 to test a networking example that function in QEMU. To load the application, I am using the u-boot that comes pre-compiled on the micro-sd. I am able to dhcp to my tftpserver and grab the seL4 image, and when I run the "go 20000000" command, I get the following:
## Starting application at 0x20000000 ...
AP Kernel returned back to the elf-loader.
abort() called.
Looking through the code, that error is in non_boot_main, yet that function call is wrapped by
#ifdef CONFIG_SMP_ARM_MPCORE
Which is undefined. That makes me think that the main() in boot.c is not being accessed and the elfloader isn't being run properly.
Is this a u-boot issue, or is it that way I have everything setup? Is it a requirement to use the pre-compiled u-boot binary for the i.mx6?
Thanks,
Chris Guikema
