Hello,
I am working with Syscfg v1.18 with LP-AM263 SDK, and for setting up the SPI configs in my .syscfg, I am unsure how to add multiple CS pins to a single SPI bus. Under the SPI driver syscfg setup, in MCSPI Channel Configuration/Signals, I am able to to set a single CS Pin, but cannot find a way to add another CS pin for a second slave device.
Is there a way to add multiple CS pins through the syscfg tool?
Hello Yue Hue,
Please follow the following steps for selecting multiple channels:
- Select Mode of Operation to Multi Channel Controller
- Go to McSPI channel Configuration and click add button to add channels and select from drop down.
I hope above step will help you. Let me know in case you have any queries.
Regards,
Akash Soni.
- 
Hi! Thanks switching to multichannel controller did allow me to set another CS pin. I am running into a quick follow up issue though: in our system we are using pin K2 as the second slave. So for SPI4, we are using:
B14 - Clock
C12 - D0 (MOSI)
D11 - D1 (MISO)
A14 - CS0
K2 - CS1
However, it does not let me select K2 for CS1, saying "This selection is not possible with your other pin/peripheral overrides". However, K12 I have not assigned to any peripherals or as a GPIO, and on the pinout on the right hand side, the pin K2 is marked as "dark gray" or "Pin Available"
Can you please help he see why I am unable to select K2 as CS1?
For sanity, I also started a brand new syscfg project just for testing, and set it up so the only thing configured was SPI4 (and no other pins/peripherals). In this empty project, K2 is also not able to be selected
Hi! I am able to select K2 pin as a CS1. Could please check your syscfg once again or else you can share example.syscfg file. I have attached the screen for your reference.
.
For some reason, I am unable to attach the syscfg to this, as insert -> file does not allow me to upload it. But I created an empty syscfg with my SDK, and only enabled SPI4. I am still unable to set CS1 to K4. As it is small, I will just copy the text to this message instead
Would you also mind sharing me your syscfg file?
Syscfg (copy pasted)
/**
* These arguments were used when this file was generated. They will be automatically applied on subsequent loads
* via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
* @cliArgs --device "AM263x_beta" --package "ZCZ" --part "AM263x" --context "r5fss0-0" --product "MCU_PLUS_SDK_AM263x@09.01.00"
* @versions {"tool":"1.18.0+3266"}
*/
/**
* Import the modules used in this configuration.
*/
const mcspi = scripting.addModule("/drivers/mcspi/mcspi", {}, false);
const mcspi1 = mcspi.addInstance();
const clock = scripting.addModule("/kernel/dpl/clock");
const debug_log = scripting.addModule("/kernel/dpl/debug_log");
const mpu_armv7 = scripting.addModule("/kernel/dpl/mpu_armv7", {}, false);
const mpu_armv71 = mpu_armv7.addInstance();
/**
* Write custom configuration values to the imported modules.
*/
mcspi1.$name = "CONFIG_MCSPI0";
mcspi1.mode = "MULTI_CONTROLLER";
mcspi1.SPI.$assign = "SPI4";
mcspi1.SPI.CLK.$assign = "EQEP0_A";
mcspi1.SPI.D0.$assign = "EQEP0_STROBE";
mcspi1.SPI.D1.$assign = "EQEP0_INDEX";
mcspi1.child.$name = "drivers_mcspi_v1_mcspi_v1_template0";
mcspi1.mcspiChannel.create(2);
mcspi1.mcspiChannel[0].$name = "CONFIG_MCSPI_CH0";
mcspi1.mcspiChannel[0].CSn.$assign = "EQEP0_B";
mcspi1.mcspiChannel[1].$name = "CONFIG_MCSPI_CH1";
const edma = scripting.addModule("/drivers/edma/edma", {}, false);
const edma1 = edma.addInstance({}, false);
edma1.$name = "CONFIG_EDMA0";
mcspi1.edmaDriver = edma1;
edma1.edmaRmDmaCh[0].$name = "CONFIG_EDMA_RM0";
edma1.edmaRmQdmaCh[0].$name = "CONFIG_EDMA_RM1";
edma1.edmaRmTcc[0].$name = "CONFIG_EDMA_RM2";
edma1.edmaRmParam[0].$name = "CONFIG_EDMA_RM3";
mpu_armv71.$name = "CONFIG_MPU_REGION0";
/**
* Pinmux solution for unlocked pins/peripherals. This ensures that minor changes to the automatic solver in a future
* version of the tool will not impact the pinmux you originally saw. These lines can be completely deleted in order to
* re-solve from scratch.
*/
mcspi1.mcspiChannel[1].CSn.$suggestSolution = "<error>";
Hi,
I am using MCU_PLUS_SDK_AM263x@09.01.00, and in your syscfg i see you are using MCU_PLUS_SDK@07.03.01. I do not have MCU_PLUS_SDK@07.03.01 installed. Is this what I should be using for the syscfg?
Furthermore, I see you are using syscfg version 1.20, while I am using syscfg version 1.18. I was using 1.20 but switched back to 1.18, as I ran into a bug with syscfg 1.20, where on 1.20 using MCU_PLUS_SDK_AM263x@09.01.00, I was not able to configure GPIOs (please see screenshot below). This was resolved by switching to syscfg 1.18, after discussing with Gunter (first comment), and as 1.18 was recommended by the MCU_PLUS_SDK_AM263x@09.01.00 user guide
Hi
This works for me as well, and also works on my syscfg locally. However, the problem is this is assigning SPI0 as multichannel controller, and allowing K2 pin to be used as SPI0 CS pin channel 2 (your SPI instance field is set to SPI0, not SPI4)
In my application, I need to bind K2 pin to SPI4, not SPI0, which your syscfg when loaded does not allow me to do either.
So in my end:
1. Setting SPI0 instance to mutlichannel allows me to select K2 pin as second CS channel to SPI0 no problem (just like your above example)
2. Setting SPI4 instance to multichannel does NOT allow me to select K2 as second CS channel to SPI4
I am actually a bit surprised that K2 as allowed to be chosen as CS1 for SPI0 instance in the syscfg , as from the data sheet, K2 does not work with SPI0 (see below attached from data sheet) and only works for SPI4
Hovering over SPI4 instance second channel (see screen shot below of green arrow), where I am trying to select K2, the syscfg tool reports that K2 is only available on SPI0, and not available for SPi4, which does not seem to line up with the data sheet:
