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.

AM6442: AM64X SDKs 10.1 - errors/question on software build sheet

Part Number: AM6442

Tool/software:

Folks:

 After downloading the MCU plus & Linux SDK ver 10.1

I saw some discrepancies & concerns on these URLs

(should they should have identical content?)

By Category > Module > SubModule

Processors and Accelerators >

    Dual-R5F MCU Subsystem  -- should that be listed as a Quad - or are you accounting for 2 Dual-R5F subsystems?

    Dual-A53 MPU subsystem - wrt RTOS on A53 -- as long as you do not insinuate that one could SMP between the Dual-A53 in FreeRTOS - but in the MCU+ release notes you say that A53 FreeRTOS is experimental - that is inconsistency.

    "Programmable Real-Time Unit and Industrial Communication Subsystem - Gigabit" - that cell needs a word-wrap of text

High-speed Serial Interfaces >

    Universal Serial Bus Subsystem (USBSS) > Device 3.0 - big error (confirm with Bin Lu) - Linux on A53 is a NO.

Industrial and Control Interfaces>

    Enhanced Quadrature Encoder Pulse (EQEP) Module > why is Linux on A53 is a NO?? I believe that Nick Saulnier had confirmed Linux drivers for EQEP exists.

    Controller Area Network (MCAN) > why not combine CAN & CAN FD rows together? You could then insert a global NO for a CAN XL row. 

Timer Modules>

    Timers>

       Timer -- question - does this row apply apply to hardware in core "dmtimer" modules? Nick Saulnier also confirmed dmtimer support on A53 Linux for me. 

  • Hi Jim,

    Most of folks are already out of the office for the holidays. I will follow up after the New Year. Thanks for the feedback.

  • Hi Jim,

    Happy New Year!

    Sorry for my late response.

    (should they should have identical content?)

    Do you mean there is any inconsistent content in the build sheet pages in both Processor SDK and MCU+ SDK documentation?

        Dual-R5F MCU Subsystem  -- should that be listed as a Quad - or are you accounting for 2 Dual-R5F subsystems?

    Yes 2x dual-r5f subsystems. This is what the device TRM called.

           Timer -- question - does this row apply apply to hardware in core "dmtimer" modules?

    This row is for the dedicated timer modules in the SoC, not the timer in the core.

    Nick Saulnier also confirmed dmtimer support on A53 Linux for me. 

    The core timer is supported in Linux, it is used only for kernel time keeping, not for any application, so the core timer is listed in the table.

    The rest of your comments have been reported to our dev team. Hopefully they will get addrssed in the next revision. Thanks for the feedback.

  • Bin:

    I believe and agree the 2 URLs for the build sheet should have identical content.

    On the other items:  

    "High-speed Serial Interfaces >

        Universal Serial Bus Subsystem (USBSS) > Device 3.0 - big error (confirm with Bin Lu) - Linux on A53 is a NO."

    I think the readability of these four rows should be altered.

    Instead of the present

    Universal Serial Bus Subsystem (USBSS) Host 3.0
    Device 3.0
    Host 2.0
    Device 2.0

    Maybe it should be adjusted to this:

    Universal Serial Bus Subsystem (USBSS) 3.0 Host
    Device
    2.0 Host
    Device

    I mention CAN XL as a specific NO input for (+) Michael Firth's Profile - Michael Firth - TI E2E support forums to consider, given I just saw that the CAN in Automation community newsletter said that TI has CAN XL transceiver ICs prototyped and demonstrated in silicon (expect the EU customers that use Bosch will be asking if Sitara product will support the new MAC & PHY for ethernet across CAN XL).

    thanks

    Jim

  • Hi Jim,

    On your comment about the USB items, I agree the wording "Host/Device 3.0/2.0" is not intuitive, but I am not sure how nowadays the dev team generates this table and if it is trivial to add one more table column only for this USB row. But I think we can just change the wording to something like "USB3.0 Host mode", "USB2.0 Device mode", ...

    The intent of this Software Buildshet is to document what are supported/unsupported for the hardware modules/features documented in the device TRM. Since CAN XL is not mentioned in the AM64x TRM, I will leave CAN XL as a separate topic to discuss.