[kirkstone] beaglebone-ai64

[kirkstone] beaglebone-ai64

[Joel Winarske]

Hi folks,

I've built core-image-weston for beaglebone-ai64.

I'm imaging sdcard using:
    sudo bmaptool copy ./core-image-weston-beaglebone-ai64.wic.xz /dev/sda

The image is not booting.

Are there any known issues with this layer on kirkstone tip of tree?


(I'm looking into making flutter-auto (AGL) run on this device; I'm the author of flutter-auto)


Thanks,
Joel

Re: [meta-ti] [kirkstone] beaglebone-ai64

[Lisandro Damián Nicanor Pérez Meyer]

[-- Attachment #1: Type: text/plain, Size: 765 bytes --]

Hi!

El jueves, 14 de septiembre de 2023 16:57:17 -03 Joel Winarske escribió:
> Hi folks,
> 
> I've built core-image-weston for beaglebone-ai64.
> 
> I'm imaging sdcard using:
>     sudo bmaptool copy ./core-image-weston-beaglebone-ai64.wic.xz /dev/sda
> 
> The image is not booting.
> 
> Are there any known issues with this layer on kirkstone tip of tree?
> 
> 
> (I'm looking into making flutter-auto (AGL) run on this device; I'm the author of flutter-auto)

Yes, I could only run the image by booting from the SD card. I'm trying to add Balena support to it.

I've compared BeagleBone's and meta-ti's u-boot and they differ in a few places which seem to be related to the eMMC, so my guess is that the issue needs to be solved there first.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [meta-ti] [kirkstone] beaglebone-ai64

[Joel Winarske]

[-- Attachment #1: Type: text/plain, Size: 2617 bytes --]

My serial interface cables just arrived.  Looks like a kernel panic due
to pvrsrvkm.  Anyone aware of this one?

[    7.408257] pvrsrvkm: loading out-of-tree module taints kernel.
[    7.428045] PVR_K:  268: Device: 4e20000000.gpu
[    7.432837] SError Interrupt on CPU1, code 0xbf000000 -- SError
[    7.432840] CPU: 1 PID: 268 Comm: systemd-udevd Tainted: G           O
   5.10.162+ #1
[    7.432841] Hardware name:  /, BIOS 2021.01-gf65a2b8f 08/10/2022
[    7.432842] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--)
[    7.432843] pc : _RGXReadBVNCFromReg.isra.0+0x20/0x140 [pvrsrvkm]
[    7.432844] lr : RGXBvncInitialiseConfiguration+0x274/0x9c0 [pvrsrvkm]
[    7.432845] sp : ffff8000132cb740
[    7.432846] x29: ffff8000132cb740 x28: ffff800011a97000
[    7.432849] x27: 0000000000000000 x26: ffff8000132cb7a8
[    7.432851] x25: ffff000812d7c000 x24: ffff0008137c29a0
[    7.432853] x23: 0000000000000000 x22: ffff8000092ae000
[    7.432855] x21: ffff0008137c2808 x20: ffff8000092557c0
[    7.432857] x19: 0000000000000000 x18: ffff8000092030f4
[    7.432859] x17: 000000ffc0000000 x16: ffff800009203460
[    7.432862] x15: ffff8000092030e0 x14: ffff800009201050
[    7.432863] x13: ffff80000920c3a4 x12: 0000000000000000
[    7.432866] x11: ffff0008137c2808 x10: 0000000000000020
[    7.432868] x9 : 0000000000000000 x8 : 0000000000000024
[    7.432870] x7 : 0000000000000000 x6 : ffff800013a00000
[    7.432872] x5 : ffff8000132cb7b0 x4 : ffff8000132cb7ac
[    7.432874] x3 : ffff8000132cb7a8 x2 : ffff8000132cb7a4
[    7.432876] x1 : 0000000000000000 x0 : ffff0008137c2808
[    7.432878] Kernel panic - not syncing: Asynchronous SError Interrupt


On Mon, Sep 18, 2023 at 1:16 PM Lisandro Damián Nicanor Pérez Meyer <
perezmeyer@gmail.com> wrote:

> Hi!
>
> El jueves, 14 de septiembre de 2023 16:57:17 -03 Joel Winarske escribió:
> > Hi folks,
> >
> > I've built core-image-weston for beaglebone-ai64.
> >
> > I'm imaging sdcard using:
> >     sudo bmaptool copy ./core-image-weston-beaglebone-ai64.wic.xz
> /dev/sda
> >
> > The image is not booting.
> >
> > Are there any known issues with this layer on kirkstone tip of tree?
> >
> >
> > (I'm looking into making flutter-auto (AGL) run on this device; I'm the
> author of flutter-auto)
>
> Yes, I could only run the image by booting from the SD card. I'm trying to
> add Balena support to it.
>
> I've compared BeagleBone's and meta-ti's u-boot and they differ in a few
> places which seem to be related to the eMMC, so my guess is that the issue
> needs to be solved there first.
>

[-- Attachment #2: Type: text/html, Size: 3150 bytes --]

Re: [meta-ti] [kirkstone] beaglebone-ai64

[Joel Winarske]

[-- Attachment #1: Type: text/plain, Size: 2267 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 4562 bytes --]

Re: [meta-ti] [kirkstone] beaglebone-ai64

[Joel Winarske]

[-- Attachment #1: Type: text/plain, Size: 3275 bytes --]

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
<joel.winarske=gmail.com@lists.yoctoproject.org> 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 (#16998):
> https://lists.yoctoproject.org/g/meta-ti/message/16998
> Mute This Topic: https://lists.yoctoproject.org/mt/101366039/2167248
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [
> joel.winarske@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 6279 bytes --]

Re: [meta-ti] [kirkstone] beaglebone-ai64

[Joel Winarske]

[-- Attachment #1: Type: text/plain, Size: 4352 bytes --]

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
<joel.winarske=gmail.com@lists.yoctoproject.org> 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
> <joel.winarske=gmail.com@lists.yoctoproject.org> 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 (#17014):
> https://lists.yoctoproject.org/g/meta-ti/message/17014
> Mute This Topic: https://lists.yoctoproject.org/mt/101366039/2167248
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [
> joel.winarske@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 7958 bytes --]

Re: [meta-ti] [kirkstone] beaglebone-ai64

[Joel Winarske]

[-- Attachment #1: Type: text/plain, Size: 4878 bytes --]

Nevermind on BeagleBoard-DeviceTree.  I just compared the kernel and
BeagleBoard-DeviceTree;
they are at parity.  BeagleBoard-DeviceTree is not needed.  The thing that
was throwing me off what the older kernel/dt.

I'll submit a patch for rolling the kernel forward.

On Thu, Oct 5, 2023 at 8:08 AM Joel Winarske via lists.yoctoproject.org
<joel.winarske=gmail.com@lists.yoctoproject.org> wrote:

> 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
> <joel.winarske=gmail.com@lists.yoctoproject.org> 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
>> <joel.winarske=gmail.com@lists.yoctoproject.org> 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/2167248
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [
> joel.winarske@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 8953 bytes --]

Re: [meta-ti] [kirkstone] beaglebone-ai64

[Joel Winarske]

[-- Attachment #1: Type: text/plain, Size: 5546 bytes --]

I just discovered a workaround to my original pvrsrvkm kernel panic.

1. bitbake core-image-weston
2. image SD card with core-image-weston-beaglebone-ai64.wic.xz
3. mount SD card in host and decompress the pvrsrvkm kernel driver:
    cd /lib/modules/5.10.168+/extra
    sudo xz --decompress pvrsrvkm.ko.xz
4. reboot device with updated SD card

(This is with kernel updated to 5.10.168-r111)

On Thu, Oct 5, 2023 at 11:09 AM Joel Winarske via lists.yoctoproject.org
<joel.winarske=gmail.com@lists.yoctoproject.org> wrote:

> Nevermind on BeagleBoard-DeviceTree.  I just compared the kernel and BeagleBoard-DeviceTree;
> they are at parity.  BeagleBoard-DeviceTree is not needed.  The thing
> that was throwing me off what the older kernel/dt.
>
> I'll submit a patch for rolling the kernel forward.
>
> On Thu, Oct 5, 2023 at 8:08 AM Joel Winarske via lists.yoctoproject.org
> <joel.winarske=gmail.com@lists.yoctoproject.org> wrote:
>
>> 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
>> <joel.winarske=gmail.com@lists.yoctoproject.org> 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
>>> <joel.winarske=gmail.com@lists.yoctoproject.org> 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 (#17062):
> https://lists.yoctoproject.org/g/meta-ti/message/17062
> Mute This Topic: https://lists.yoctoproject.org/mt/101366039/2167248
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [
> joel.winarske@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 9874 bytes --]