BODAS CB-ME, CL-API and FlashingReference Updates
We updated the BODAS CB-ME, CL-API and FlashingReference with new features and improved usability for the unified basic solution for Machinery Regulation (MR) and Cyber Resilience Act (CRA) compliance.
Remark: The implementation the CRA basic security solution in your project is optional and depends on your Threat Assessment and Risk Analysis (TARA) - see myBODAS Community.
CB-ME (Packages _260619)
RC5-6/40 (V01.11.00), RC18-12/40 + RC27-18/40 (V03.12.00) & RC18-12E/40 + RC27-18E/40 (V01.05.00)
CAN Channel UDS Request Handling: CB-ME now responds to UDS requests on a single CAN channel, utilizing the CAN ID and baud rate configured by the ASW through NVM shared configuration, regardless of whether the CB-ME hex file or CL-API hex file is flashed to the ECU.
One-Shot Password Provisioning and Update via keyfile: A new security feature, one-shot operation, is now available for managing passwords via keyfile. When enabled, this mechanism permanently and irreversibly restricts any further password updates through the keyfile.
For further details, refer RC Customer Manual 40.s/ml300-bs (and all CRA patch workflows).
Limitations:
This CB-ME is compatible with BSW 1.29-bs (workflows 40.ml290-bs, 40.ml290-bs.rts) or another basic security (-bs) patched version of the older workflows (-bs). However, One-Shot Password Provisioning and Update will not be available.
This CB-ME is incompatible with BODAS Secure Sign 0.2.2, please update to BODAS Secure Sign 1.0.3
Flashing Reference for RC40-Family has been updated accordingly. The new version is availble in myRexorth --> 23_FlashingReference, please contact your Sales Representative or our Onboarding Team.
CL-API (Packages _260619)
RC5-6/40 (V01.11.00), RC18-12/40 + RC27-18/40 (V03.12.00)
Signature and Certificate Support: Memory and linker file configurations have been updated to support signature and certificate implementation by the CLAPI application.
Documentation:
The CL-API manual has been updated with additional description for clnvm_readBlock regarding NVM RAM mirror behavior during startup.
The error codes provided to the callback cluds_registerErrorCallback() are described separately.