Hi,

On 08/09/2018 06:35 PM, Giovani Gracioli wrote:
> Thanks Ralf.
> 
> I updated to the latest version, 0.9.1, and the original problem is gone.

Great.

> 
> Then I got an unhandled data write:

One bug down, the next shows up ;-)

> 
> Unhandled data write at 0xffe01800(1)

That's weird, I'm wondering why this didn't happen with the old
Jailhouse version.

> 
> FATAL: unhandled trap (exception class 0x24)
> 
> To solve this, I added the TCM memory region 0xffe00000 to the root cell 
> config. This memory is used by the R5 to boot its image:
> 
> /* TCM region for the R5 */ {
>                       .phys_start = 0xffe00000,
>                       .virt_start = 0xffe00000,
>                       .size =       0xC0000,
>                       .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE | 
> JAILHOUSE_MEM_EXECUTE,

Is it IO? JAILHOUSE_MEM_IO?

> },
> 
> However, when I use the zynqmp_r5_remoteproc driver with the jailhouse, the 
> driver has an error, and the code is not ran:
> 
> remoteproc remoteproc0: powering up ff9a0100.zynqmp_r5_rproc
> remoteproc remoteproc0: Booting fw image dma_scheduler.elf, size 815824
> Failed to get RPU node status.
> Failed to get RPU node status.

Hmm, don't know what's exactly behind that memory area or how R5 works,
but I'd guess it's iomem. Try to add JAILHOUSE_MEM_IO to the region.

  Ralf

> 
> This does not happen when Jailhouse is loaded. Should the flags contain 
> anything else?
> 
> Best
> Giovani
> 
>> Hi,
>>
>> On 08/09/2018 04:26 PM, Giovani Gracioli wrote:
>>> Hello,
>>>
>>> I am running Jailhouse v0.8 on the ultrascale+. I have enabled the root 
>>> cell then started the remote R5 processor (using the zynqmp_r5_remoteproc 
>>> and rpmsg_user_dev_driver drivers). The R5 communicates to A53 through 
>>> interrupts from the remote proc filesystem. 
>>>
>>> Once I started the R5 code, I got an "unhandled trap (exception class 
>>> 0x17)".
>>
>> This is a SMC trap. Try updating to latest next, there's a high chance
>> that this error will disappear.
>>
>>   Ralf
>>
>>>
>>> FATAL: unhandled trap (exception class 0x17)
>>> Cell state before exception:
>>>  pc: ffffff800808f428   lr: ffffff8008769094 spsr: 60000145     EL1
>>>  sp: ffffff8009f6bbf0  esr: 17 1 0000000
>>>  x0: 00000000c2000003   x1: 0000000000000007   x2: 0000000000000000
>>>  x3: 0000000000000000   x4: 0000000000000000   x5: 0000000000000000
>>>  x6: 0000000000000000   x7: 0000000000000000   x8: ffffffc04c1feb00
>>>  x9: 0000000000000000  x10: 000000005f49e37b  x11: 0000000018c74a31
>>> x12: 00000000a87bd568  x13: 00000000a78138a0  x14: 000000001b3408f1
>>> x15: 00000000175d87f8  x16: 0000000040034850  x17: 000000001b6b01bd
>>> x18: 00000000af4aa165  x19: ffffff8009f6bc78  x20: ffffff8009f6bcb8
>>> x21: ffffff8009f6bcbc  x22: ffffffc04b890838  x23: ffffffc04177a800
>>> x24: 0000000000000044  x25: ffffffc04c1fef44  x26: 0000000000000040
>>> x27: ffffff8008a21000  x28: ffffffc04cd80080  x29: ffffff8009f6bc00
>>>
>>> Parking CPU 1 (Cell: "ZynqMP-ZCU102")
>>>
>>> Is this a configuration problem or something else?
>>>
>>> Best
>>> Giovani
>>>
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to