• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 103 subscribers
  • Views 212 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM625: Linux SDK 9.00 Issues Tracker Details

Stuart Baker
Genius 10420 points
Part Number: AM625

I'm working with a customer that is using QNX as their operating system kernel. However, they are using TI's U-Boot distribution for their [secure] boot process. They are wanting to know if we can provide more detail on the Issues Tracker list items found here:

https://software-dl.ti.com/processor-sdk-linux-rt/esd/AM62X/09_00_00_03/exports/docs/devices/AM62X/linux/Release_Specific_Release_Notes.html#issues-tracker

More specifically:

I have been experimenting with the latest U-Boot images and had a question about the fixes described here: 2.1. Release Notes — Processor SDK AM62x Documentation. Is there a way to determine if these fixes apply to U-Boot or to Yocto with regards to the AM62x?

Thanks,

Stuart

  • 0
    TI__Guru 61656 points
    Stuart Baker said:
    I have been experimenting with the latest U-Boot images and had a question about the fixes described here: 2.1. Release Notes — Processor SDK AM62x Documentation. Is there a way to determine if these fixes apply to U-Boot or to Yocto with regards to the AM62x?

    We would need to look at each item in Jira, and from there should see where the fixes was made. Glancing through the list a multitude of projects are affected even beyond U-Boot or Yocto, depending on the item. It is a long list; are you interested in a few items specifically?

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 130 points

    Dear Andreas,

    Thank you for your help, from the Release Notes I would be interested in learning if the following record IDs pertain to U-Boot or Yocto for the AM62x:

    • LCPD-29792
    • LCPD-29589
    • LCPD-29441
    • LCPD-29300
    • LCPD-28764
    • LCPD-28415
    • LCPD-28414
    • LCPD-34686
    • LCPD-34131
    • LCPD-32945

    Also, would it be possible to understand the severity of these issues? Thanks for your help.

    From,

    Daniel Fettke

  • 0 in reply to Dan Fettke
    TI__Guru 61656 points

    Hi Dan,

    let me dig up some info on these Jira tickets. I'm traveling for the rest of the week so it'll be next week before I can get back. If this is needed more urgently please escalate internally.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    TI__Guru 61656 points
    Dan Fettke said:
    • LCPD-29792
    • LCPD-29589
    • LCPD-29441
    • LCPD-29300
    • LCPD-28764
    • LCPD-28415
    • LCPD-28414
    • LCPD-34686
    • LCPD-34131
    • LCPD-32945

    I did some research, here's some more detail as to where the fix is located, I split it by U-Boot and Kernel ("Yocto" is really a superset, all fixes are in Yocto if you will so I'm not sure how this would be helpful). None of those issues was related to userspace (rootfs).

    ID Summary Fix Location
    LCPD-29792 am62x: mcspi not functional Linux Kernel DTS fix ("arm64: dts: ti: k3-am62-main: Fix clocks for McSPI")
    LCPD-29589 AM62x CPSW: PPS example not enabled by default Linux Kernel DTS fix and defconfig update
    LCPD-29441 am62x: kingston emmc fails on AM62x U-Boot and Kernel DTS fix ("arm64: dts: ti: k3-am62-main: Update OTAP and ITAP delay select"), plus U-Boot code fix ("drivers: mmc: am654_sdhci: Update OTAP/ITAP delay")
    LCPD-29300 U-Boot: OSPI-NOR: sf probe shows 0 randomly Was not able to identify a specific fix in U-Boot, but likely due to changes in drivers/spi/cadence_qspi.c possible due to moving from U-Boot 2021.01 to 2023.04.
    LCPD-28764 AM62x: Cannot resume from low power mode Kernel (possibly ATF), wasn't able to identify and point to a specific fix
    LCPD-28415 AM62: emmc: Had to disable higherspeeds U-Boot, Kernel. Likely same fix as LCPD-29441.
    LCPD-28414 AM62x EVM Devicetree should disable unused MCU peripherals Kernel DTS
    LCPD-34686 MMC itapdly sel values are not specified in uboot DTS U-Boot DTS
    LCPD-34131 AM62: Boot inconsistencies on HS FS U-Boot and/or Device FW (TIFS, DM)
    LCPD-32945 AM62x USB-DFU Boot is broken in R5 SPL U-Boot

    For some of those I wasn't able to find a specific fix (commit) to point to as those issues were implicitly resolved by the general SDK migration from v8.6 (U-Boot 2021.01 and Kernel 5.10) to v9.0 (U-Boot 2023.04 and Kernel 6.1) by way of a newer code base, with those issues no longer being observable.

    Lastly, as for severity, I think that's somewhat subjective and use-case dependent. Personally I think all the OSPI and MMC related fixes I'd say are critical if you use those peripherals. Others are more use-case specific.

    Regards, Andreas