cancel
Showing results for 
Search instead for 
Did you mean: 

Broken/odd pin mapping when configuring BMS63CHAIN for C4MINI1 board

hno-wires
Associate

I am trying to configure BMS63CHAIN component on AEK-MCU-C4MINI1 board connected to an AEK_POW_BMSNOTX but the allocated pin mapping created by the tool does not match the C4MINI1 board connectors.

I tried following the AutoDevKit chapter in um3185 Getting started with AutoDevKit battery management system (BMS) evaluation boards:

1. Open AutoDevKit Studio 2.6.1
2. Create New SPC5 Application using SPC58ECxx Platform Component RLA
3. Add SPC58ECxx Init Package Component RLA
4. Add SPC58ECxx Low Level Drivers Component RLA
5. Add AutoDevKit 4 Mini Init Package Component
Note: Getting Started guide mentions adding AutoDevKit Init Package, but I can not select this together with 4 Mini Init. Seems to be mutually exclusive.
6. Add AEK-POW-BMS63CHAIN component
7. Open AEK-POW-BMS63CHAIN -> AEK_POW_BMSCHAIN[0]
8. Select Node type: AEK_POW_BMSNOTX
9. Seletct dspi: dspi0, cs0

Go back to the AEK-POW-BMS63CHAIN component and press Allocate button.

Go to SPC58EC 4M Mini board view. This looks strange. Cannot scroll down to view the AEK-POW-BMSNOTX wiring allocation. If I zoom out then I can see the connection wiring table and it is a mess. Expected SPI connections to all be on CN12 (dspi0), and NTC and FAULT to be at meaningful locations.

CS0: CN1-1
MISO: CN12-4 (ok)
MOSI: CN2-6
SCK: CM12-3 (ok)
FAULT: X
eNTC1: X
eNTC2: CN16-13
eNTC3: X
eNTCb: CN16-14

Why is it selecting random pins like this?

Can I somehow adjust the pin mapping to some more sane use of the connectors?

Update: I now tried to import the AEK-MCU-C4MINI - AEK_POW_BMSCCTX_GUI_application for discovery example application, and the initial import shows meaningful pin mapping, but if I try to make any changes then the pinmapping gets just as broken. Simply pushing "Deallocate" and then "Allocate" after importing the sample is sufficient to break the pin mapping.

0 REPLIES 0