> > >>Can you share the cell and dts with me, from your GPIO transfer to the > baremetal cell? > Unfortunately, I cannot, because of University Regulations. You do not need dts for the baremetal cell. It is for the non-root Linux cell
> >>Are you working with the raspberry-pi/bcm2711 as well? > yes > >>The serial driver already is loaded, so I would expect this to work, but > I get some bus error, even the cell grants access to this address: > *>>[ 0.035905] OF: amba: of_address_to_resource() failed (-22) for > /serial@7e201600* > > >>The I2C drivers are also loaded and two internal I2C are running on the > base linux/the root cell. So I guess my defconfig should be ok?! > >>But the kernel logs give some phandle error, I find no helpful > information about online... > *>>[ 0.037665] OF: /i2c@7e804000: could not find phandle* > Hmmm, does Jailhouse TCP/IP inter-cell communication works fine?, I mean > can you ping the root cell from the non-root cell? > >>Yesterday I tried to transfer the GPIO as well. I oriented myself on > this dts[1] > >>Leading to this cell and dts additions, which is the 283x-dtsi with the > overriden values from the 2711.dts applied: > > [image: dts.png] > >>Originally I started with the reg size of 0xb4 like in the rpi4 dts > file, but booting the linux cell then gave me: > > > *>>[ 0.195071] pinctrl-bcm2835 7e200000000000ff.gpio: could not get IO > memory>>[ 0.195095] pinctrl-bcm2835: probe of 7e200000000000b4.gpio > failed with error -22* > > That is the correct workflow. Try on the root cell, and load to the > non-root Linux. But there are many constraints, are you sure that the > drivers are fit for Buildroot? From my painful experience, you have to > cross-compile your application with buildroot, or are you sure that the I2C > does not have any kernel dependecies? > > >>In the kernel logs. So I increased it a little, since in the peripheral > docs section 5.2[3] upto 0xf0 registers are mentioned, but the same error > ocurrs > >>with reg-size of 0xff. I also do not understand, why the 32-bit address > is expended to 64-bit, when the bcm2711 has a 35-bit bus... > > I see only one problem here, which is the size. Jailhouse only accepts > paged size for peripherals and also memory regions. So, 0xff will not work, > I would recommend you to change it to 256 bytes and try, because it does > not make any sense, why it wont work. > > >>And yes, I am using jailhouse-images. For building jailhouse myself - > >>I tried that - but I could'n start the kernel module with my self build > image, > >>but I am fine for now by working with the reference jailhouse-images. > >>If anybody has used peripherals in the linux demo in the rpi > jailhouse-image I would be happy for any code references, or hints ^^ > First step first is to port Jailhouse, with only jailhouse-images, you > have limited capabilities to learn and expand your understandings. But > jailhouse-images is the only way to understand how to port jailhouse > yourself > > >I don't know. Maybe my kernel hacking level is not up for using jailhouse > like that. I fell that I struggle with the kernel here more, then with > actual jailhouse. > >But on the other hand I would like to understand, make it running, and > add some practical examples of peripheral usage to some kind of docs, so > >that the learning curve for getting started is a little less step. I just > don't know where else to ask, if one can recommend some literature to read > or forum, where my > >issues are discussed more adequately I am grateful for any hints :) > Nothing special than Jan tutorial and the drone project video. There is > also one video from Texas instruments and the project autojail. > >Thank you all very much! > >Greetings Pau; Moustafa Noufale -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/cb798767-e2c8-4313-a93c-cf12e6c18d6cn%40googlegroups.com.
