I'm narrowing in on the issue.

I have a BeagleBoard.org OS image release where I can see PowerVR running,
and PCIe (WiFi/BT) works:
* bbai64-emmc-flasher-debian-11.7-xfce-edgeai-arm64-2023-09-02-10gb.img
Rescue option 1 (default image panics when booting with PCIe populated):
[    0.000000] Linux version 5.10.168-ti-arm64-r111 (voodoo@AM69-SK-32g-01)
(gcc (Debian 10.2.1-6) 10.2.1u3

These images use a device tree from a different repo than the ti-kernel
repo:
    kernel: https://github.com/beagleboard/linux.git
    dt:
https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees

Dumping the DT from Yocto linux-bb and BeagleBoard.org the output is not
the same.

Proposed minimum changes:
* add option for BeagleBoard-DeviceTree
* update kernel versions in linux-bb
* update PowerVR version to match kernel/DT

Thoughts?

On Mon, Sep 25, 2023 at 11:56 AM Joel Winarske via lists.yoctoproject.org
<[email protected]> wrote:

> Update on issue.
>
> I can boot a kirkstone core-image-base (headless) without any issue.
>
> Randolph at TI has indicated the panic is related to an outdated gpu
> definition in DT.  The gpu DT def defines two power domains, only one is
> required.  I have not yet successfully confirmed this change.
>
>
>
> On Wed, Sep 20, 2023 at 5:08 PM Joel Winarske via lists.yoctoproject.org
> <[email protected]> wrote:
>
>> Today's limited progress:
>>
>> 1. U-Boot from eMMC is used by default.  Shipping devices have outdated
>> U-Boot.
>> 2. Rule out U-Boot, and use Yocto built U-Boot by pressing RST + BOOT,
>> wait, release RST, then release BOOT.  Boot flow will use all boot bits
>> from the SD card with this approach.
>> 3. Update `linux-bb.org_git.bb` to use tip of tree:
>> # 5.10.168 version for 32-bit
>> SRCREV:armv7a = "0f40ca5e749e9176ad4ea30c68be4fb2340647db"
>> PV:armv7a = "5.10.168+git${SRCPV}"
>> BRANCH:armv7a = "5.10.168-ti-r71"
>>
>> # 5.10.168 version for 64-bit
>> SRCREV:aarch64 = "ac2750dbf3a3b9078feff995e6754d5c5f609c19"
>> PV:aarch64 = "5.10.168+git${SRCPV}"
>> BRANCH:aarch64 = "v5.10.168-ti-arm64-r110"
>>
>>
>>
>> Updating kernel has no impact on kernel panic:
>>
>> [    6.621063] pvrsrvkm: loading out-of-tree module taints kernel.
>> [    6.637510] PVR_K:  251: Device: 4e20000000.gpu
>> [    6.642337] SError Interrupt on CPU0, code 0xbf000000 -- SError
>> [    6.642339] CPU: 0 PID: 251 Comm: systemd-udevd Tainted: G           O
>>      5.10.168+ #1
>> [    6.642340] Hardware name: BeagleBoard.org BeagleBone AI-64 (DT)
>> [    6.642341] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--)
>> [    6.642343] pc : _RGXReadBVNCFromReg.isra.0+0x20/0x140 [pvrsrvkm]
>> [    6.642343] lr : RGXBvncInitialiseConfiguration+0x274/0x9c0 [pvrsrvkm]
>> [    6.642344] sp : ffff8000143db740
>> [    6.642345] x29: ffff8000143db740 x28: ffff8000091e4548
>> [    6.642349] x27: 0000000000000000 x26: ffff8000143db7a8
>> [    6.642351] x25: ffff0008132da000 x24: ffff000813c741a0
>> [    6.642353] x23: 0000000000000000 x22: ffff8000091ed000
>> [    6.642355] x21: ffff000813c74008 x20: ffff8000091947c0
>> [    6.642357] x19: 0000000000000000 x18: ffff800009142e74
>> [    6.642359] x17: 000000ffc0000000 x16: ffff8000091431e0
>> [    6.642361] x15: ffff800009142e60 x14: ffff800009140dd0
>> [    6.642363] x13: ffff80000914c124 x12: 0000000000000000
>> [    6.642365] x11: ffff000813c74008 x10: 0000000000000020
>> [    6.642367] x9 : 0000000000000000 x8 : 0000000000000024
>> [    6.642369] x7 : 0000000000000000 x6 : ffff800012500000
>> [    6.642371] x5 : ffff8000143db7b0 x4 : ffff8000143db7ac
>> [    6.642373] x3 : ffff8000143db7a8 x2 : ffff8000143db7a4
>> [    6.642375] x1 : 0000000000000000 x0 : ffff000813c74008
>> [    6.642377] Kernel panic - not syncing: Asynchronous SError Interrupt
>>
>>
>>
>>
>>
> 
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17058): 
https://lists.yoctoproject.org/g/meta-ti/message/17058
Mute This Topic: https://lists.yoctoproject.org/mt/101366039/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to