• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 268 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

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

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

Jim Mrowca
Genius 4132 points
Part Number: AM6442


Tool/software:

Just checked software-dl.ti.com/processor-sdk-linux/esd/AM64X/11_00_09_04/exports/docs/devices/AM64X/AM64X_build_sheet_11_00_09_04_files/AM64X_build_sheet_11_00_09_04.htm

A few errors still present, as well as new suggestions/nomenclature

Processors and Accelerators >

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

 Suggest one inserts the acronym (IPC) in "Interprocessor Communication (IPC)" <check with (+) Nick Saulnier's Profile - Nick Saulnier - TI E2E support forums if he agrees>

Confusing: I thought DMA means Direct Memory Access instead of "Data Movement Architecture (DMA)" - what is the right meaning for DMA ???

High-speed Serial Interfaces > Universal Serial Bus Subsystem (USBSS) > Device 3.0  - Linux on A53 is a NO.!!!!

Industrial and Control Interfaces> 

   Controller Area Network (MCAN) -- new acronym

      (as I disclosed to  (+) Schuyler Patton's Profile - Schuyler Patton - TI E2E support forums   2 weeks ago in an e2e where AM64X EVMs do not have CAN transceivers)

         the CAN in Automation (CiA) standard development team is officially having the ISO standard amended to retitle CAN as CAN Classic (CAN CC)

            - so a specific SubModule cell entry should change from "CAN" to "CAN CC"  (but keep "CAN FD" as is in the other cell)

                      <the TI Interface group who does CAN* transceivers can also vouch for the change>

Last Question -

   on the Categories "Internal Diagnostics Modules" and "On-Chip Debug" - would/could/should JTAG be mentioned for completeness? 

  • +1
    TI__Guru**** 171821 points

    Hi Jim,

    Thanks for the feedback.

    Jim Mrowca said:

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

     Suggest one inserts the acronym (IPC) in "Interprocessor Communication (IPC)" <check with (+) Nick Saulnier's Profile - Nick Saulnier - TI E2E support forums if he agrees>

    Jim Mrowca said:
    High-speed Serial Interfaces > Universal Serial Bus Subsystem (USBSS) > Device 3.0  - Linux on A53 is a NO.!!!!

    I will report this to the dev team.

    Jim Mrowca said:
    Confusing: I thought DMA means Direct Memory Access instead of "Data Movement Architecture (DMA)" - what is the right meaning for DMA ???

    "Date Movement Architecture" is the name used in the device TRM.

    Jim Mrowca said:
             the CAN in Automation (CiA) standard development team is officially having the ISO standard amended to retitle CAN as CAN Classic (CAN CC)

    I will suggest our dev team to update this to "Classic CAN", which is the name used in the device TRM.

    Jim Mrowca said:
       on the Categories "Internal Diagnostics Modules" and "On-Chip Debug" - would/could/should JTAG be mentioned for completeness? 

    JTAG is just the interface of the On-Chip Debug subsystem. If JTAG was mentioned specifically, it would give an impression that other functions in the subsystem behind JTAG is not in the scope.

  • 0 in reply to Bin Liu
    Genius 4132 points

    Ok Bin;

    like we said back on SDK v10.1, that USB3.x device implications are confusing.

    We might want to also share the below with the interfaces group wrt CAN transceivers; quoted from the CiA newsletter "[CAN Community News] No. 3 - 2025-02-14"

    "

    CAN definition

    The term “controller area network (CAN)” is referenced in many documents including standards. In some of these documents, a definition is given. Unfortunately, those are not all valuable. In order to improve the situation, the following harmonized ISO definition should be used:

    controller area network
    CAN
    serial communication technology covering the data link layer and the physical coding
    sublayer as standardized in ISO 11898-1 as well as the physical medium attachment (PMA)
    sublayer as standardized in ISO 11898-2 or ISO 11898-3

    Note 1 to entry   There are three frame format types specified: CAN CC (classic), CAN FD (flexible data rate) and CAN XL (extended data-field length).

    Note 2 to entry   There are five PMA types specified: CAN HS (high-speed), CAN FD, CAN SIC (signal improvement capability), CAN SIC XL, and CAN FT (fault-tolerant).

    "

    Jim

  • +1 in reply to Jim Mrowca
    TI__Guru**** 171821 points

    Hi Jim,

    The AM64x device TRM states USB super-speed is not supported in device mode. The "USB3.0 device mode: Yes" in the Software Buildsheet is not correct, I have reported this to the sw dev team to update it.

    The TRM uses "Classic CAN", so the Software Buildsheet should use the same name too. I have reported the same to the sw dev team.

  • 0 in reply to Bin Liu
    Genius 4132 points

    Hi Bin:

     please have the SDK 11.1 build notes fixed by the sw dev teams.

    thanks

    Jim

  • +1 in reply to Jim Mrowca
    TI__Guru**** 171821 points

    Hi Jim,

    Yes, our internal ticket marked this report to be fixed in SDK 11.1.