... On 03/01/2017 04:49 AM, [email protected] wrote: > I'm still experimenting with GPIO from bare-metal inmate. Actually I need to > change Pull-Up/Pull-Down value for SPI1_MISO and SPI1_SCK PADs. > > So did the following changes on jetson-x1.c and jetson-demo.c cell configs > file > > 1) I splitted MISC range to share PINMUX_AUX (I need to share all the pinmux > since it's 4k long and sub-paging seems to not work on arm64 at lest from my > tests) Oh, okay, it doesn't? What's broken? > > /* MISC stuff (see datasheet) */ { > .phys_start = 0x70000000, > .virt_start = 0x70000000, > .size = 0x3000, > .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE | > JAILHOUSE_MEM_IO, > }, > /* MISC: PINMUX AUX submodule (Shared) */ { > .phys_start = 0x70003000, > .virt_start = 0x70003000, > .size = 0x1000, > .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE | > JAILHOUSE_MEM_IO | JAILHOUSE_MEM_ROOTSHARED, > }, > > 2) I added the shared PINMUX_AUX region to the jetson-demo.c > /* MISC: PINMUX AUX submodule (Shared) */ { > .phys_start = 0x70003000, > .virt_start = 0x70003000, > .size = 0x1000, > .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE | > JAILHOUSE_MEM_IO | JAILHOUSE_MEM_ROOTSHARED, > }, > > But whe I try to read the actual configuration for SPI1_MISO PAD from my > inmate, I get the following exception (That is different from a MMIO > non-mapped area exception): > > Unhandled data read at 0x7003054(4) Look at the address. Look twice ;-)
You probably only miss a zero in the base address of your code. > > FATAL: unhandled trap (exception class 0x24) > Cell state before exception: > pc: 0000000000007400 lr: 00000000000073d8 spsr: 20000005 EL1 > sp: 0000000000009f50 esr: 24 1 1850006 > x0: 0000000000000000 x1: 0000000007003054 x2: 000000000000001f > x3: 0000000007003058 x4: 0000000000000000 x5: 0000000000000002 > x6: 0000000000000000 x7: 0000000000000000 x8: 0000000000000008 > x9: 0000000000000000 x10: 0000000000000000 x11: 0000000000007630 > x12: ffffffffffffffff x13: 00000000ffffffd0 x14: 0000000000000020 > x15: 0000000000000000 x16: 0000000000000000 x17: 0000000000000000 > x18: 0000000000000000 x19: 0000000000001108 x20: 000000006000d008 > x21: 000000006000d018 x22: 000000006000d068 x23: 000000006000d058 > x24: 0000000000001000 x25: 00000000000079aa x26: 0000000050041440 > x27: 0000000050041080 x28: 000000005004141b x29: 0000000000000000 > > I tryed to read the address as 32 (reported) and 16 bits variable but I get > the same exception (obviusly with the read attempted size reported is 2). > > > What exception class: 0x24 refer to? Any idea about this behaviour? 0x24: Data abort from lower exception level. Because you're accessing an physical address that is not mapped :) Ralf > > Regards, > Errico Guidieri -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
