MCU-PLUS-SDK-AM243X: custom OSPI flash with AM2434_ALV

Hi Dominik,

It is possible that the reason you are seeing this fail is because the diag example actually expects the flash to be in 1s1s1s mode to establish initial communication with it and then print out the SFDP of the flash device. If the flash is already configured in octal ddr mode then the SoC would fail due to the mismatch in communication protocols. 

If it is not possible to get the SFDP table initially from the flash then I'd like to suggest a few options:

1) we have a set of instructions in the sdk documentation regarding flash support: AM243x MCU+ SDK: Adding Support For a Custom Flash Device (ti.com). Try going over the steps, but treating this scenario as a "Case 2: Flash Doesn't Support SFDP." This case essentially explains that you need to fill out the flash information in SysConfig manually. After you have this information then you can try running a different flash example, like the io example present in the SDK.

2) this is more of a question, but have you read through the Flash Selection Guide for the AM243 to see if this flash is compatible with the SoC? I'd check here too to verify that there wouldn't be any other underlying potential conflicts that can occur even after solving the given problem. Link: AM243x OSPI, QSPI Flash Selection Guide

Please let me know if any of these help or if you need more assistance

Best,

Daniel  

Hi Daniel,

thanks for your hints. We followed the steps from here "Case 2: Flash Doesn't Support SFDP" and tried to fill out the sysconfig manually. However, we are still stuck, see the following call stack from Board_driversOpen()

/**
* 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 "AM243x_ALV_beta" --package "ALV" --part "ALV" --context "r5fss0-0" --product "MCU_PLUS_SDK_AM243x@09.00.00"
* @versions {"tool":"1.17.0+3128"}
*/
 
/**
* Import the modules used in this configuration.
*/
const flash      = scripting.addModule("/board/flash/flash", {}, false);
const flash1     = flash.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();
const mpu_armv72 = mpu_armv7.addInstance();
const mpu_armv73 = mpu_armv7.addInstance();
const mpu_armv74 = mpu_armv7.addInstance();
const mpu_armv75 = mpu_armv7.addInstance();
 
/**
* Write custom configuration values to the imported modules.
*/
flash1.$name                      = "CONFIG_FLASH0";
flash1.device                     = "CUSTOM_FLASH";
flash1.fname                      = "MT35X";
flash1.flashManfId                = "0x2C";
flash1.cmdSectorErase3B           = "0xD8";
flash1.cmdSectorErase4B           = "0xDC";
flash1.cmdWr                      = "0x02";
flash1.flashOeType                = "1";
flash1.proto_cmdRegRd             = "0xB5";
flash1.proto_cmdRegWr             = "0xB1";
flash1.cmdRd                      = "0x13";
flash1.strDtr_isAddrReg           = false;
flash1.dummyClksCmd               = 0;
flash1.dummyClksRd                = 0;
flash1.proto_isAddrReg            = false;
flash1.dummy_isAddrReg            = false;
flash1.dummy_cmdRegRd             = "0xB5";
flash1.strDtr_cmdRegRd            = "0xB5";
flash1.dummy_cmdRegWr             = "0xB1";
flash1.strDtr_cmdRegWr            = "0xB1";
flash1.cmdChipErase               = "0xC4";
flash1.fourByteEnableSeq          = "0xB7";
flash1.peripheralDriver.$name     = "CONFIG_OSPI0";
flash1.peripheralDriver.dmaEnable = true;
flash1.peripheralDriver.phyEnable = true;
 
const udma                         = scripting.addModule("/drivers/udma/udma", {}, false);
const udma1                        = udma.addInstance({}, false);
udma1.$name                        = "CONFIG_UDMA0";
flash1.peripheralDriver.udmaDriver = udma1;
 
debug_log.enableUartLog        = true;
debug_log.uartLog.$name        = "CONFIG_UART_LOG";
debug_log.uartLog.UART.$assign = "USART0";
 
mpu_armv71.$name             = "CONFIG_MPU_REGION0";
mpu_armv71.size              = 31;
mpu_armv71.attributes        = "Device";
mpu_armv71.accessPermissions = "Supervisor RD+WR, User RD";
mpu_armv71.allowExecute      = false;
 
mpu_armv72.$name             = "CONFIG_MPU_REGION1";
mpu_armv72.size              = 15;
mpu_armv72.accessPermissions = "Supervisor RD+WR, User RD";
 
mpu_armv73.$name             = "CONFIG_MPU_REGION2";
mpu_armv73.baseAddr          = 0x41010000;
mpu_armv73.size              = 15;
mpu_armv73.accessPermissions = "Supervisor RD+WR, User RD";
 
mpu_armv74.$name             = "CONFIG_MPU_REGION3";
mpu_armv74.baseAddr          = 0x70000000;
mpu_armv74.size              = 21;
mpu_armv74.accessPermissions = "Supervisor RD+WR, User RD";
 
mpu_armv75.$name    = "CONFIG_MPU_REGION5";
mpu_armv75.baseAddr = 0x80000000;
mpu_armv75.size     = 31;
 
/**
* 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.
*/
flash1.peripheralDriver.OSPI.$suggestSolution      = "OSPI0";
flash1.peripheralDriver.OSPI.CLK.$suggestSolution  = "OSPI0_CLK";
flash1.peripheralDriver.OSPI.CSn0.$suggestSolution = "OSPI0_CSn0";
flash1.peripheralDriver.OSPI.DQS.$suggestSolution  = "OSPI0_DQS";
flash1.peripheralDriver.OSPI.D7.$suggestSolution   = "OSPI0_D7";
flash1.peripheralDriver.OSPI.D6.$suggestSolution   = "OSPI0_D6";
flash1.peripheralDriver.OSPI.D5.$suggestSolution   = "OSPI0_D5";
flash1.peripheralDriver.OSPI.D4.$suggestSolution   = "OSPI0_D4";
flash1.peripheralDriver.OSPI.D3.$suggestSolution   = "OSPI0_D3";
flash1.peripheralDriver.OSPI.D2.$suggestSolution   = "OSPI0_D2";
flash1.peripheralDriver.OSPI.D1.$suggestSolution   = "OSPI0_D1";
flash1.peripheralDriver.OSPI.D0.$suggestSolution   = "OSPI0_D0";
debug_log.uartLog.UART.RXD.$suggestSolution        = "UART0_RXD";
debug_log.uartLog.UART.TXD.$suggestSolution        = "UART0_TXD";

Yes we were aware of the  AM243x OSPI, QSPI Flash Selection Guide, actually we used a Flash mentioned here "MT35XU512ABA"

Hi Dominik,

Do you get the same problem when running a different OSPI example other than the diagnostic? the diag example should not be used in any other mode than 1s1s1s so i believe it would just fail constantly for this flash device

Can you also try to run the ospi_flash_io example using the SBL NULL? is it possible to change bootmodes in your custom board?

Best,

Daniel

Hi Daniel,

yes that was already the ospi_flash_io example with the adjusted sysconfig. We did not execute ospi_diag example with changed settings (ospi_diag, would not use Flash_...() funcitons of driver I guess). We can switch boot modes, we have similar dip switches as on a EVM board. Currently we are in Dev Boot mode/No Boot mode and do the initialization manually via ccs scripting.

I thought for flashing and using the SBL null bootloader we need a working OSPI flash, that's why we currently are doing SOC initialization via CCS scripting

Hi Daniel,

thank you for the information, that's good to know. We will checkout our possibilities.

Kind regards

Dominik

Hi Dominik,

Thank you, I will place a ticket to modify the flash selection guide based on this information. I will be closing this thread now. If you have any other question feel free to open a new thread.

Best,

Daniel 

Just to sum it up: We now switched to MT35XU512ABA1G12-0AAT this chip seems to work, we can execute ospi_diag flash example successfully and get parameters/json printed

Hi Dominik,

Glad to hear that switching the device worked for you, please let us know if you have any further questions

Best,

Daniel