...

The PC application is One GUI.  It communicates with the motherboard and all the daughterboards present on the motherboard.  In concept, One GUI has a main page that shows the system view, as well as individual pages providing register access of each detected devices.  In system view icons of the motherboard and the daughterboards present on the motherboard are shown (see below figure).  If any of the devices are selected, the registers window for that device will be brought into focus.  Hovering over any of the signals or power bus lines will show the name of the named label.  Any register value or system parameters can be shown in static or dynamic charts.  One GUI also includes automatic testing and cell characterization features.

1.3 One SDK

One SDK forms the building blocks of MCU firmware for BMS devices, and is the main focus on this design document.  It combines PDC Library and FG functionality such that the same firmware can support any combination of the following functions:

• Type-C Port Manager (TCPM)
• Fuel Gauge (FG)
• Cell Characterization (CCHAR)
• Motherboard Controller (MC)

TCPM typically works with a Type-C Port Controller (TPCP) to support USB-PD power negotiation up to 48V@5A.   FG typically works with an AFE (aka BMIC) to provide battery monitoring.  In both cases, the MCU+AFE combination can be a chipset, or fully encased in the same IC (i.e., co-pack).   Cell characterization (CCHAR) is a standalone daughtercard capable of cycling the battery cells over temperature.  CCHAR sequence will be orchestrated by the One GUI, with the proxy firmware running on the motherboard MCU

1.3.1 One SDK Objectives

The main objectives of One SDK are:

1. Protect and monetize Firmware IP
2. Faster time-to-market
3. Reduce solution cost

One SDK must protect the Firmware IP such as FG algorithm and TCPM.  The protection will come from hardware security such as ARM Trust Zone or from software security such as encryption.  One SDK can also support faster time-to-market by combining FG and TCPM with other value-add firmware features, such as CAN and Bluetooth by pairing the firmware with Renesas MCUs that has 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., fond dependence on BMS devices due to attractive features, ease of use and value gain.

Image Addedsfdsfd

2.0 One SDK Architecture

2.1 Overview

...