2.6. Release Notes - 07_00_00¶

Security Features:

• Official support for silicon tested J721e HS images.
• HS Devices: Support for configuring derived KEK (DKEK) in SA2UL and enabled host access to SA2UL
• Removed support of HSM-related features (TRNG, Asymmetric key services, and keystore)
• Global soft lock for extended OTP

PM Features:

• HW PTSTAT silicon errata workaround

RM Features:

• RM board configuration now allows up to two assignments of a resource per host.
• Added the TISCI_MSG_RM_UDMAP_FLOW_DELEGATE message to pass configuration control of common flows to other hosts.

Boot Time Optimizations

• SYSFW Boot notification + Board Configuration = 6.39 ms (Within Budget of 5 ms (+/- 2 ms))
• ROM MCU Only Boot mode support.

The PDK Jacinto package is now a combined package for both AM65xx and J721E platforms. Hence the pdk folder name in SDK reflect the family name rather than the SOC name like am65xx or j721e. Due to this the PDK_SOC variable derived from the pdk folder while sourcing pdksetupenv.sh/.bat will default to one of the SOC in the family i.e. in this case am65xx

• This means user need to set PDK_SOC variable to the required SOC while calling pdk makefile from PDK_INSTALL_DIR/packages

Only the files applicable to a particular platform is packaged. This is to done to reduce the overall package size, remove unwanted files for users for better file/folder navigation and also to ensure that a file which is not applicable for a platform is not wrongly included by application

• Due to this some of the application interface files may be missing from the package compared to last release. Users are advised to remove the inclusion of these files in their application for the respective platform builds

API guide for PDK is now generated for the entire PDK package instead of individual module API guides. The generated API guide is now present in PDK_INSTALL_DIR/docs/api_guide folder. This gives flexibility to give cross references across modules in PDK as well generate SOC specific documentation. Due to this API_Documentation.html present in PDK_INSTALL_DIR/packages is removed

Hardware push instance number in CPTS events is now an enumeration of type CpswCpts_HwPush, not an 8-bit integer.

CPSW DMA TX channel params (CpswDma_UdmaChTxPrms) added boolean flags to filter out extended and protocol specific info words.

Exposed below UDMA ring and channel config params

• Added Ring mode config option in CpswDma_UdmaRingPrms
• CpswDma_UdmaFlowPrms - added boolean flags to indicate if extended or protocol specific info words.

CpswDma_PktInfo now has fields for packet timestamp information (CpswDma_PktTsInfo) and directed port numbers.

Due to a System Firmware ABI change, applications using the Sciclient_rmGetResourceRange API to retrieve host processor IRQ ranges need to update the processor through which processor IRQ ranges are discovered.

System Firmware no longer directly manages host processor input IRQs as a resource. All resources of subtype TISCI_RESASG_SUBTYPE_<destination processor IRQ interface>_IRQ_GROUPr*_FROM_<source interrupt router> have been removed.

System Firmware now manages all interrupt router (IR) outputs directly with SoC IR output ranges managed under the resource subtype TISCI_RESASG_SUBTYPE_IR_OUTPUT

Applications that query System Firmware for the host processor input IRQ range via the Sciclient_rmGetResourceRange() must update the types and subtypes used in the query. The processor IRQ subtypes have been removed. The query via Sciclient_rmGetResourceRange() now needs to use SoC IR types and the IR output resource subtype. Note, this requires knowledge of which IR is directly connected to the processor IRQ input range desired for configuration. The linked tables below show the resource type migration that an application using the Sciclient_rmGetResourceRange() API should make when switching from the old IRQ input resource types to the new IR output resource types.

AM65X Sciclient Interrupt Resource Type Migration Table

AM65X SR2 Sciclient Interrupt Resource Type Migration Table

J721E Sciclient Interrupt Resource Type Migration Table

To facilitate backwards compatibility between the new IR output resource and the Sciclient_rmIrqSet and Sciclient_rmIrqRelease APIs which take a destination host IRQ (dst_host_irq parameter) as input the Sciclient_rmIrqTranslateIrOutput() API has been added.

The Sciclient_rmIrqTranslateIrOutput API translates an IR output to the destination processor input IRQ value. The returned value can be provided directly to the dst_host_irq parameter of the Sciclient_rmIrqSet and Sciclient_rmIrqRelease APIs.

New Sciclient_rmIrqSetRaw and Sciclient_rmIrqReleaseRaw APIs have been added. These APIs allow direct programming of SoC interrupt aggregators (IA) and interrupt routers (IR) in accordance to new System Firmware interrupt management functionality.

The existing Sciclient_rmIrqSet and Sciclient_rmIrqRelease APIs continue to function as they did before.