I am able to download Simulink code to the UM11310 thanks to the help provided with this discussion: https://community.nxp.com/t5/NXP-Model-Based-Design-Tools/Download-code-created-with-MBDT-for-S32K-t...
Now I need to make battery measurements. I am using this article as a guide. https://community.nxp.com/t5/NXP-Model-Based-Design-Tools/BMS-amp-MBDT-MC33771B-MC33772B-TPL-communi... I am not successful so far.
I use CAN to send out the status value from the "MC3377xB Config" block. The status output is 8, which according to the documentation means, "Communication Timeout."
I believe I have the "SPI CS Selections" right based on the MCU schematic in section 3.7.3 of the UM11310 User manual. There are many, many pin options in the "LPSPI Config" blocks. I have played around a little bit in there, but so far I have not been successful.
Hello @ranulf ,
As you can see, both SIN (for Master LPSPI Instance) and SOUT (for Slave LPSPI instance) are not used in the schematic and not connected to anything. However, the MBDT SPI block does not allow you to set the "None" option on the pin, so the pin will be initialized for SPI, but not used when data is transferred. The data that might appear on that pin will be ignored. In the "original" SPI protocol, there is a net to send data from Master to Slave (MOSI) and another one to exchange data from Slave to Master(MISO). But on TPL there a special use-case. Let me explain.
In the above image, you can see how data is being transferred from S32K to an MC33771 via TPL, and reverse. Basically, MCU is going to use an entire SPI instance as MOSI, and another SPI instance as MISO. When S32K will send a frame on the TPL bus, it will send the frame via the MOSI and SCK1. The CS1 falling edge (Slave Select) will cause the "11" sequence on the bus. The frame will arrive at the selected MC33771 device, but also, the "11" sequence on the bus will select the S32K slave LPSI instance so the message will get to the S32K as a loopback message. Now, as you know, an SPI Slave cannot initialize a data transfer. So this is the reason why the second SPI instance is used by the S32K and configured as Slave. When the MC33771 sends a response to the S32K, the MC33771 start of frame "11" which will set the falling edge event on the CS2. This will notify the S32K SPI Slave configured instance that the MC33771 is sending a response. The data will arrive at the S32K on the second SPI instance, configured a MISO
We can simplify the UM11310 schematic by having a look at the MC33664 Typical application circuit. Basically, there is no MISO_0, because the MC33664 will not send anything back to the MCU when it wants to transfer data on the TPL bus. Same, for the RX: the MCU will not send any response to the MC33664.
So, both of the blocks drop down pins and the schematics are correct, but the usage of the TPL protocol has created this special use-case.
Hope this helps,
Marius
With LPSPI_Config set to master, SOUT on the Pins tab has three options (see below). However, none of these options appear to be available in the MCU schematic in section 3.7.3 on page 14 of the UM11310 User guide, Rev 1.
- PTB16 does not appear in the schematic. The range is PTB0-PTB7, PTB12, PTB13
- PTD2 is shown as not connected
- PTE0 is shown as not connected
Am I missing something?
Hello @ranulf,
I had a look at the schematic of the board you are trying to access from MBDT. The board uses an MC33771C as AFE which for now is not supported in our toolbox. The MBDT toolbox can communicate with MC33771BSPI, MC33771BTPL, MPC33772BSI and MC33772BTPL.
However, the C code that can configure and read the measurements from the board you are using can be easily inserted following this article here. https://community.nxp.com/t5/NXP-Model-Based-Design-Tools/How-to-use-your-own-C-code-in-our-Toolbox-... with the lite version of the drivers that can be accessed here https://www.nxp.com/design/analog-expert-software-and-tools/sdk-analog-expert-drivers/embedded-sw-ba...
I had a look on this driver, and we can provide such support through a patch to the MBDT release 4.2.0. To do such a request, please contact the NXP FAE that you are talking with. After that, we can consider adding such support.
Regarding the LPSPI configuration that you re mentioning here, the Pins tab fields and also the pins option from the LPSPI Config block are updated to be displayed just for the selected instance in the General tab. Let's discuss specifically on the UM11310 case.
The TPL protocol requires two LPSPI instances to be used, one as master ( for sending data through the MC33664 transceiver on the TPL bus) and other as slave (to receive data from the TPL bus through the MC33664 transceiver).
For the TX:
The bord uses PTB1, PTB2 and PTB5 as SOUT, SCK and respectively CS are the ones from the LPSPI0. For that, as Master you have to select the Instance 0. This will update the Pins, where you can select the ones mentioned in the schematic
For the RX:
THe board uses the LPSPI1 as PTD0, PTD1, PTD3 as SCK, SIN and PCS0.
Hope this helps,
Marius
I got the Lite version drivers for MC33771C from https://www.nxp.com/design/analog-expert-software-and-tools/sdk-analog-expert-drivers/embedded-sw-ba... The files available here are [bcc.c, bcc.h, bcc_communication.c, bcc_communication.h, bcc_mc33771c.h]
When I build I get the error
"fatal error: bcc_mc33771c.h: No such file or directory #include "bcc_mc33771c.h""
That is unexpected because I made bcc_mc33771c.h available as shown below.
