This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSPM0C1104: Sysconfig Bug with SPI port

Part Number: MSPM0C1104
Other Parts Discussed in Thread: SYSCONFIG,

Edit:  I have found that the particular project below is meant to have 2 CS lines (one for command, one for data).  So it uses the CS for command/data flags and isn't applicable for the customer.  I will suggest jhe choose one of the other 3 SPI command demo projects.  However the crash of sysconfig is terminal so we should resolve it as is below - but I think I have a workaround for my customer.

Hi, 

I have a assigned focus customer dead in the water with this SPI bug.  It is unrecoverable and the project / sysconfig has to be deleted.

Let me know if you have trouble reproducing it.  I can do it on my machine and his.  SDK 1.30.00.03.

The customer is trying to create a SPI master with 4 wires 3 clk/data lines + single CS.

-----------

import:  spi_controller_command_data_control_LP_MSPM0C1104_nortos_ticlang

Under SPI, there are 2 CS called out which seems in error but perhaps is just an enhancement.  The customer 'clicked around' to try and get rid of the 5th pin (2nd CS). 

If you go to SPI note the CS3 CD below

Then if you go to SPI Controller Basic Configuration

Pull the Drop down for Chip Select and select anything but the default CS0

it throws the following error and is unrecoverable as you can no longer open the SPI config section or delete it.

Thanks!

Blake