Sciclient Interface to DMSC ROM

Introduction

Sciclient needs to interact with ROM to be able to load the central processing firmware during boot. This is called only once via the SBL executing on MCU R5 in the AM6x device family.

DMSC ROM will set up 2 outbound/inbound threads(secure proxy) for Normal and High priority messages and pairs this threads via Ring Accelerator in MCU NAVSS for both DMSC and R5 ROM to exchange messages.

The thread ID's for each message type is Sciclient_RomThreadIds

Message Type	Thread Id
DMSC Out Bound Normal Prioirty	Thread 0
DMSC In Bound Normal Priority	Thread 1
DMSC Out Bound High Priority	Thread 2
DMSC In Bound High Priority	Thread 3
R5 Out Bound Normal Priority	Thread 4
R5 In Bound Normal Priority	Thread 5
R5 Out Bound High Priority	Thread 6
R5 In Bound High Priority	Thread 7

The DMSC ROM messages handled by the Sciclient_loadFirmware API is Sciclient_RomMessageType.

Files
file	sciclient_romMessages.h
	This file contains the declaration of the messaging format to talk to ROM.

Data Structures
struct	Sciclient_RomFirmwareLoadPayload_t
	ROM messaging: Payload for loading firmware . More...

Sciclient load firmware ROM Message Types.
Requirement: DOX_REQ_TAG(PDK-2143)
#define	SCICLIENT_ROM_MSG_R5_TO_M3_M3FW   (0x8105U)
#define	SCICLIENT_ROM_MSG_M3_TO_R5_M3FW_RESULT   (0x8805U)
#define	SCICLIENT_ROM_MSG_CERT_AUTH_PASS   (0x555555U)
#define	SCICLIENT_ROM_MSG_CERT_AUTH_FAIL   (0xffffffU)

Macro Definition Documentation

SCICLIENT_ROM_MSG_R5_TO_M3_M3FW

#define SCICLIENT_ROM_MSG_R5_TO_M3_M3FW   (0x8105U)

Firmware Load Command ID from R5 to M3

SCICLIENT_ROM_MSG_M3_TO_R5_M3FW_RESULT

#define SCICLIENT_ROM_MSG_M3_TO_R5_M3FW_RESULT   (0x8805U)

Firmware Load Command ID from M3 to R5

SCICLIENT_ROM_MSG_CERT_AUTH_PASS

#define SCICLIENT_ROM_MSG_CERT_AUTH_PASS   (0x555555U)

Firmware Load Command response Authorization Passed

SCICLIENT_ROM_MSG_CERT_AUTH_FAIL

#define SCICLIENT_ROM_MSG_CERT_AUTH_FAIL   (0xffffffU)

Firmware Load Command response Authorization Failed