...
1.3.1 One SDK Objectives
The main objectives of One SDK are:
...
(1) protect and monetize Firmware IP
...
; (2) faster time-to-market
...
; and (3) reduce solution cost
...
.
...
One SDK must protect protects Firmware IP such as FG algorithm and TCPM . The protection will come from by leveraging hardware security such as ARM Trust Zone or from by software security such as encryption. One SDK can also support supports faster time-to-market by combining FG and TCPM with other value-add added firmware features, such as combining BMS features such as FG and TCPM with CAN and Bluetooth by pairing the firmware with ready-made Renesas MCUs that has have the required hardware peripherals.
1.3.2 One SDK supported MCUs
One SDK supports RL78, Cortex M0+, M23 and M33. RL78 is largely for supporting legacy BMS FGIC. Cortex M0+ is for 1S FGIC support. Cortex M23 is largely for high-cell count BMIC support. Cortex M33 is for high-cell count BMC/FGIC support and motherboard MCU support. One SDK supported MCU shall have catalog firmware pre-programmed in Flash. For M23 and M33 which has Trust Zone support, the IP shall be protected by Trust Zone. None-secured firmware can be overwritten to reclaim the Flash memory. Due to the lack of HW security, firmware for RL78 and M0+ have to be developed by Renesas to protect the firmware IP and limiting Flash data readout. Below shows stated policy. The scenarios enclosed by dotted red lines are considered "sticky", i.e., customer developing fond dependence on BMS devices due to attractive features, ease of use and , or value gain.
2.0 One SDK Architecture
...