Re: [meta-xilinx] What kernel for MPSoC?
On 27-07-16 19:19, Manjukumar Harthikote Matha wrote:>>> On 07/22/2016 09:56 AM, Manjukumar Harthikote Matha wrote:>> Hi Mike,>>>>> Kind regards, Mike Looijmans System Expert TOPIC Products Materiaalweg 4 5681 RJ Best T: +31 (0) 499 33 69 69 Postbus 440 E: mike.looijm...@topicproducts.com 5680 AK Best W: www.topicproducts.com The Netherlands Please consider the environment before printing this e-mailTopic zoekt gedreven (embedded) software specialisten! -Original Message->>> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx->>> boun...@yoctoproject.org] On Behalf Of Mike Looijmans>>> Sent: Thursday, July 21, 2016 10:26 PM>>> To: meta-xilinx@yoctoproject.org>>> Subject: Re: [meta-xilinx] What kernel for MPSoC?>>>>> <>>>> On 21-07-16 13:30, Mike Looijmans wrote:>>>> I got the "dev" kernel to compile by removing the Xilinx PHY support>>>> (which was causing the failure). The resulting ~4.5 kernel crashes on>>>> the same spot, also in the psci core.>>>>>> We will look into why PHY driver is broken and keep you posted.>>> PHY driver is fixed in masterIndeed. Don't know if it actually works, but the compile error is solved.Thanks,Mike. -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] What kernel for MPSoC?
On 07/22/2016 09:56 AM, Manjukumar Harthikote Matha wrote: Hi Mike, -Original Message- From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- boun...@yoctoproject.org] On Behalf Of Mike Looijmans Sent: Thursday, July 21, 2016 10:26 PM To: meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] What kernel for MPSoC? <> On 21-07-16 13:30, Mike Looijmans wrote: I got the "dev" kernel to compile by removing the Xilinx PHY support (which was causing the failure). The resulting ~4.5 kernel crashes on the same spot, also in the psci core. We will look into why PHY driver is broken and keep you posted. PHY driver is fixed in master Thanks Manju -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] What kernel for MPSoC?
Hi Mike, > -Original Message- > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- > boun...@yoctoproject.org] On Behalf Of Mike Looijmans > Sent: Thursday, July 21, 2016 10:26 PM > To: meta-xilinx@yoctoproject.org > Subject: Re: [meta-xilinx] What kernel for MPSoC? > <> > On 21-07-16 13:30, Mike Looijmans wrote: > > I got the "dev" kernel to compile by removing the Xilinx PHY support > > (which was causing the failure). The resulting ~4.5 kernel crashes on > > the same spot, also in the psci core. > > We will look into why PHY driver is broken and keep you posted. Thanks Manju This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] What kernel for MPSoC?
On 22-07-16 16:03, Nathan Rossi wrote:> On Fri, Jul 22, 2016 at 11:44 PM, Mike Looijmans> wrote: On 22-07-16 15:31, Nathan Rossi wrote:>>> On Fri, Jul 22, 2016 at 3:25 PM, Mike Looijmans wrote: If I modify the devicetree and disable the 'psci' part, the system boots fine but doesn't wake the other three cores.>> By default ZynqMP machines are setup to use PSCI for cpu bringup (QEMU>>> has a PSCI implementation in-built), which means you will have to load>>> some firmware before the kernel to handle PSCI calls, etc. ARM Trusted>>> Firmware is what Xilinx recommends and they provide support for.>> The u-boot post regarding SPL>>> (http://lists.denx.de/pipermail/u-boot/2016-May/254902.html) has info>>> for booting atf. By default meta-xilinx will build an ATF binary for>>> ZynqMP targets.>> Please explain, it seems to build a package "arm-trusted-firmware" but it>> doesn't seem to make its way into the image or deployment area?>> It deploys (or it at least should deploy) the> "bl31-.bin"/"bl31-.elf" binaries. This is a piece of> ATF, specifically stage 3 - 1 (the el3 runtime). You can read more> info here https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/firmware-design.md.Okay, thanks, got it figured out now.I sent a patch to automate that "mkimage" step. Will save other people a lot of headaches.M. Kind regards, Mike Looijmans System Expert TOPIC Products Materiaalweg 4 5681 RJ Best T: +31 (0) 499 33 69 69 Postbus 440 E: mike.looijm...@topicproducts.com 5680 AK Best W: www.topicproducts.com The Netherlands Please consider the environment before printing this e-mailTopic zoekt gedreven (embedded) software specialisten! -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] What kernel for MPSoC?
On Fri, Jul 22, 2016 at 11:44 PM, Mike Looijmans wrote: > > On 22-07-16 15:31, Nathan Rossi wrote: > > On Fri, Jul 22, 2016 at 3:25 PM, Mike Looijmans > > wrote: > >> > >> If I modify the devicetree and disable the 'psci' part, the system boots > >> fine > >> but doesn't wake the other three cores. > > > > By default ZynqMP machines are setup to use PSCI for cpu bringup (QEMU > > has a PSCI implementation in-built), which means you will have to load > > some firmware before the kernel to handle PSCI calls, etc. ARM Trusted > > Firmware is what Xilinx recommends and they provide support for. > > > > The u-boot post regarding SPL > > (http://lists.denx.de/pipermail/u-boot/2016-May/254902.html) has info > > for booting atf. By default meta-xilinx will build an ATF binary for > > ZynqMP targets. > > > Please explain, it seems to build a package "arm-trusted-firmware" but it > doesn't seem to make its way into the image or deployment area? It deploys (or it at least should deploy) the "bl31-.bin"/"bl31-.elf" binaries. This is a piece of ATF, specifically stage 3 - 1 (the el3 runtime). You can read more info here https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/firmware-design.md. Regards, Nathan > > > > Kind regards, > > > > Mike Looijmans > > System Expert > > > > > > TOPIC Products > > > > > > Materiaalweg 4 > > > > > > 5681 RJ Best > > T: > > +31 (0) 499 33 69 69 > > Postbus 440 > > E: > > mike.looijm...@topicproducts.com > > 5680 AK Best > > W: > > www.topicproducts.com > > The Netherlands > > > Please consider the environment before printing this e-mail > > > Topic zoekt gedreven (embedded) software specialisten! > -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] What kernel for MPSoC?
On 22-07-16 15:31, Nathan Rossi wrote:> On Fri, Jul 22, 2016 at 3:25 PM, Mike Looijmans wrote: If I modify the devicetree and disable the 'psci' part, the system boots fine>> but doesn't wake the other three cores.>> By default ZynqMP machines are setup to use PSCI for cpu bringup (QEMU> has a PSCI implementation in-built), which means you will have to load> some firmware before the kernel to handle PSCI calls, etc. ARM Trusted> Firmware is what Xilinx recommends and they provide support for.>> The u-boot post regarding SPL> (http://lists.denx.de/pipermail/u-boot/2016-May/254902.html) has info> for booting atf. By default meta-xilinx will build an ATF binary for> ZynqMP targets.Please explain, it seems to build a package "arm-trusted-firmware" but it doesn't seem to make its way into the image or deployment area? Kind regards, Mike Looijmans System Expert TOPIC Products Materiaalweg 4 5681 RJ Best T: +31 (0) 499 33 69 69 Postbus 440 E: mike.looijm...@topicproducts.com 5680 AK Best W: www.topicproducts.com The Netherlands Please consider the environment before printing this e-mailTopic zoekt gedreven (embedded) software specialisten! -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] What kernel for MPSoC?
On Fri, Jul 22, 2016 at 3:25 PM, Mike Looijmans wrote: > > If I modify the devicetree and disable the 'psci' part, the system boots fine > but doesn't wake the other three cores. By default ZynqMP machines are setup to use PSCI for cpu bringup (QEMU has a PSCI implementation in-built), which means you will have to load some firmware before the kernel to handle PSCI calls, etc. ARM Trusted Firmware is what Xilinx recommends and they provide support for. The u-boot post regarding SPL (http://lists.denx.de/pipermail/u-boot/2016-May/254902.html) has info for booting atf. By default meta-xilinx will build an ATF binary for ZynqMP targets. Regards, Nathan > > On 21-07-16 13:30, Mike Looijmans wrote: > > I got the "dev" kernel to compile by removing the Xilinx PHY support (which > > was causing the failure). The resulting ~4.5 kernel crashes on the same > > spot, > > also in the psci core. > > > > > > On 21-07-16 10:57, Mike Looijmans wrote: > > > With current meta-xilinx master the kernel won't boot on the zcu102 > > board, it > > > crashes on an invalid instruction. I tried using "linux-xlnx-dev" as > > provider > > > but that won't even compile. > > > > Kind regards, > > > > Mike Looijmans > > System Expert > > > > > > TOPIC Products > > > > > > Materiaalweg 4 > > > > > > 5681 RJ Best > > T: > > +31 (0) 499 33 69 69 > > Postbus 440 > > E: > > mike.looijm...@topicproducts.com > > 5680 AK Best > > W: > > www.topicproducts.com > > The Netherlands > > > Please consider the environment before printing this e-mail > > > Topic zoekt gedreven (embedded) software specialisten! > > > -- > ___ > meta-xilinx mailing list > meta-xilinx@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-xilinx > -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] What kernel for MPSoC?
If I modify the devicetree and disable the 'psci' part, the system boots fine but doesn't wake the other three cores.On 21-07-16 13:30, Mike Looijmans wrote:> I got the "dev" kernel to compile by removing the Xilinx PHY support (which> was causing the failure). The resulting ~4.5 kernel crashes on the same spot,> also in the psci core.>>> On 21-07-16 10:57, Mike Looijmans wrote:> > With current meta-xilinx master the kernel won't boot on the zcu102 board, it> > crashes on an invalid instruction. I tried using "linux-xlnx-dev" as provider> > but that won't even compile. Kind regards, Mike Looijmans System Expert TOPIC Products Materiaalweg 4 5681 RJ Best T: +31 (0) 499 33 69 69 Postbus 440 E: mike.looijm...@topicproducts.com 5680 AK Best W: www.topicproducts.com The Netherlands Please consider the environment before printing this e-mailTopic zoekt gedreven (embedded) software specialisten! -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] What kernel for MPSoC?
I got the "dev" kernel to compile by removing the Xilinx PHY support (which was causing the failure). The resulting ~4.5 kernel crashes on the same spot, also in the psci core.On 21-07-16 10:57, Mike Looijmans wrote:> With current meta-xilinx master the kernel won't boot on the zcu102 board, it> crashes on an invalid instruction. I tried using "linux-xlnx-dev" as provider> but that won't even compile.>>> Starting kernel ...>> [ 0.00] Booting Linux on physical CPU 0x0> [ 0.00] Linux version 4.4.0-xilinx (mike@...) (gcc version 6.1.1> 20160511 (GCC) ) #1 SMP6> [ 0.00] Boot CPU: AArch64 Processor [410fd034]> [ 0.00] bootconsole [uart0] enabled> [ 0.00] efi: Getting EFI parameters from FDT:> [ 0.00] efi: UEFI not found.> [ 0.00] cma: Reserved 128 MiB at 0x7800> [ 0.00] psci: probing for conduit method from DT.> [ 0.00] swapper[0]: undefined instruction: pc=ffc8acf0> [ 0.00] Code: d402 d65f03c0 d503201f d503201f (d403)> [ 0.00] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP> [ 0.00] Modules linked in:> [ 0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.0-xilinx #1> [ 0.00] Hardware name: ZynqMP ZCU102 RevB (DT)> [ 0.00] task: ffc000b17840 ti: ffc000b08000 task.ti:> ffc000b08000> [ 0.00] PC is at __invoke_psci_fn_smc+0x0/0x8> [ 0.00] LR is at psci_probe+0x30/0x22c> [ 0.00] pc : [] lr : [] pstate:> 42c5> [ 0.00] sp : ffc000b0beb0> [ 0.00] x29: ffc000b0beb0 x28: > [ 0.00] x27: 0040 x26: ffc000b91000> [ 0.00] x25: ffc000bcbc68 x24: 8200> [ 0.00] x23: ffc0009874d8 x22: ffc000b1ad18> [ 0.00] x21: ffc000b23000 x20: ffc000bec000> [ 0.00] x19: ffc000bec298 x18: ffc080b93617> [ 0.00] x17: 8000 x16: 0001> [ 0.00] x15: x14: > [ 0.00] x13: 0018 x12: 0101010101010101> [ 0.00] x11: 0018 x10: 0101010101010101> [ 0.00] x9 : x8 : 7f7f7f7f7f7f7f7f> [ 0.00] x7 : fefefefeff626c72 x6 : 008080808082> [ 0.00] x5 : 0200 x4 : ffc8acf0> [ 0.00] x3 : x2 : > [ 0.00] x1 : x0 : 8400> [ 0.00]> [ 0.00] Process swapper (pid: 0, stack limit = 0xffc000b08020)> [ 0.00] Stack: (0xffc000b0beb0 to 0xffc000b0c000)> [ 0.00] bea0: ffc000b0bee0> ffc000acc988> [ 0.00] bec0: ffc07700 ffc000b18000 ffc000b23000> ffc000b1ad18> [ 0.00] bee0: ffc000b0bef0 ffc000accad8 ffc000b0bf10> ffc000aa847c> [ 0.00] bf00: ffc07700 ffc000ae8ba0 ffc000b0bfa0> ffc000aa5660> [ 0.00] bf20: ffc000add9e8 ffc000b91000 ffc000b0e000> ffc000b91000> [ 0.00] bf40: 7df14118 00c05000> 00c08000> [ 0.00] bf60: ffc81198 0001> 0fff5000> [ 0.00] bf80: 0001 > > [ 0.00] bfa0: 0079a000 0400> 0e12> [ 0.00] bfc0: 0fff5000 0003 7df14118> > [ 0.00] bfe0: ffc000add9e8 > > [ 0.00] Call trace:> [ 0.00] [] __invoke_psci_fn_smc+0x0/0x8> [ 0.00] [] psci_0_2_init+0x14/0x1c> [ 0.00] [] psci_dt_init+0x30/0x40> [ 0.00] [] setup_arch+0x384/0x538> [ 0.00] [] start_kernel+0xa0/0x3b8> [ 0.00] [<0079a000>] 0x79a000> [ 0.00] Code: d402 d65f03c0 d503201f d503201f (d403)> [ 0.00] ---[ end trace cb88537fdc8fa200 ]---> [ 0.00] Kernel panic - not syncing: Attempted to kill the idle task!> [ 0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle> task!> Kind regards, Mike Looijmans System Expert TOPIC Products Materiaalweg 4 5681 RJ Best T: +31 (0) 499 33 69 69 Postbus 440 E: mike.looijm...@topicproducts.com 5680 AK Best W: www.topicproducts.com The Netherlands Please consider the environment before printing this e-mailTopic zoekt gedreven (embedded) software specialisten! -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
[meta-xilinx] What kernel for MPSoC?
With current meta-xilinx master the kernel won't boot on the zcu102 board, it crashes on an invalid instruction. I tried using "linux-xlnx-dev" as provider but that won't even compile.Starting kernel ...[ 0.00] Booting Linux on physical CPU 0x0[ 0.00] Linux version 4.4.0-xilinx (mike@...) (gcc version 6.1.1 20160511 (GCC) ) #1 SMP6[ 0.00] Boot CPU: AArch64 Processor [410fd034][ 0.00] bootconsole [uart0] enabled[ 0.00] efi: Getting EFI parameters from FDT:[ 0.00] efi: UEFI not found.[ 0.00] cma: Reserved 128 MiB at 0x7800[ 0.00] psci: probing for conduit method from DT.[ 0.00] swapper[0]: undefined instruction: pc=ffc8acf0[ 0.00] Code: d402 d65f03c0 d503201f d503201f (d403)[ 0.00] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP[ 0.00] Modules linked in:[ 0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.0-xilinx #1[ 0.00] Hardware name: ZynqMP ZCU102 RevB (DT)[ 0.00] task: ffc000b17840 ti: ffc000b08000 task.ti: ffc000b08000[ 0.00] PC is at __invoke_psci_fn_smc+0x0/0x8[ 0.00] LR is at psci_probe+0x30/0x22c[ 0.00] pc : [] lr : [] pstate: 42c5[ 0.00] sp : ffc000b0beb0[ 0.00] x29: ffc000b0beb0 x28: [ 0.00] x27: 0040 x26: ffc000b91000[ 0.00] x25: ffc000bcbc68 x24: 8200[ 0.00] x23: ffc0009874d8 x22: ffc000b1ad18[ 0.00] x21: ffc000b23000 x20: ffc000bec000[ 0.00] x19: ffc000bec298 x18: ffc080b93617[ 0.00] x17: 8000 x16: 0001[ 0.00] x15: x14: [ 0.00] x13: 0018 x12: 0101010101010101[ 0.00] x11: 0018 x10: 0101010101010101[ 0.00] x9 : x8 : 7f7f7f7f7f7f7f7f[ 0.00] x7 : fefefefeff626c72 x6 : 008080808082[ 0.00] x5 : 0200 x4 : ffc8acf0[ 0.00] x3 : x2 : [ 0.00] x1 : x0 : 8400[ 0.00][ 0.00] Process swapper (pid: 0, stack limit = 0xffc000b08020)[ 0.00] Stack: (0xffc000b0beb0 to 0xffc000b0c000)[ 0.00] bea0: ffc000b0bee0 ffc000acc988[ 0.00] bec0: ffc07700 ffc000b18000 ffc000b23000 ffc000b1ad18[ 0.00] bee0: ffc000b0bef0 ffc000accad8 ffc000b0bf10 ffc000aa847c[ 0.00] bf00: ffc07700 ffc000ae8ba0 ffc000b0bfa0 ffc000aa5660[ 0.00] bf20: ffc000add9e8 ffc000b91000 ffc000b0e000 ffc000b91000[ 0.00] bf40: 7df14118 00c05000 00c08000[ 0.00] bf60: ffc81198 0001 0fff5000[ 0.00] bf80: 0001 [ 0.00] bfa0: 0079a000 0400 0e12[ 0.00] bfc0: 0fff5000 0003 7df14118 [ 0.00] bfe0: ffc000add9e8 [ 0.00] Call trace:[ 0.00] [] __invoke_psci_fn_smc+0x0/0x8[ 0.00] [] psci_0_2_init+0x14/0x1c[ 0.00] [] psci_dt_init+0x30/0x40[ 0.00] [] setup_arch+0x384/0x538[ 0.00] [] start_kernel+0xa0/0x3b8[ 0.00] [<0079a000>] 0x79a000[ 0.00] Code: d402 d65f03c0 d503201f d503201f (d403)[ 0.00] ---[ end trace cb88537fdc8fa200 ]---[ 0.00] Kernel panic - not syncing: Attempted to kill the idle task![ 0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! Kind regards, Mike Looijmans System Expert TOPIC Products Materiaalweg 4 5681 RJ Best T: +31 (0) 499 33 69 69 Postbus 440 E: mike.looijm...@topicproducts.com 5680 AK Best W: www.topicproducts.com The Netherlands Please consider the environment before printing this e-mailTopic zoekt gedreven (embedded) software specialisten! -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
