• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 32 subscribers
  • Views 376 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

AM62P: AM62P: interact with customized flash via OSPI driver

AM62P: AM62P how to use customized QSPI flash W25Q256JV

pengfei sui
Prodigy 240 points

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

Hi  Ti

I followed this documentation guide 

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/latest/exports/docs/api_guide_am62px/EXAMPLES_DRIVERS_OSPI_FLASH_DIAG.html

I use SDK   AM62Px MCU+ SDK  11.00.00

I use uart bootloader  default_sbl_uart_hs_fs.cfg 

 
--file=../../examples/drivers/ospi/ospi_flash_diag/am62px-sk/wkup-r5fss0-0_freertos/ti-arm-clang/ospi_flash_diag.debug.appimage.hs_fs
 
the download is ok , But  R5 core  WKUP_UART0 can not output any log 
 
If I use  DM appimage 
--file=../../examples/drivers/ipc/ipc_rpmsg_echo/am62px-sk/wkup-r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo.debug.appimage.hs_fs
 
it can output log
 
I don't know  why I use demo   ospi_flash_diag.debug.appimage.hs_fs  can not output any log ?
 
there is  ospi_flash_diag  example.syscfg  file
 

example.syscfg.txt 

 

there is  W25Q256JV  datasheet pdf doc

W25Q256JV SPI RevQ 02072025 Plus.pdf 

 

Thanks

  • 0
    TI__Intellectual 1430 points

    Hello,
    Thank you for your query. The concerned expert is Out of Office due to **TI India** Holiday.
    Please expect a delay in response. We appreciate your patience and understanding.

    Best regards,
    TI E2E Support Team
    ---
    *This is an automated notification.*

  • 0
    TI__Guru 59465 points

    Hi,

    Please tell us the full FLASH PART Number which you have ordered/evaluating?

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Kumar
    Prodigy 240 points

    Hi 

    I use  W25Q256JV   QSPI FLASH 

    there is the datasheet 

    5381.W25Q256JV SPI RevQ 02072025 Plus.pdf

    Regards,

    SUI

  • 0 in reply to pengfei sui
    TI__Guru 59465 points

    Hi,

    I will need the full flash name. You can check with the flash vendor as to what is the full flash part number name.

    For a reference, this is the full naming convention for the flash.

    Looking forward to your response.

    Thanks,

    Vaibhav

  • 0 in reply to Vaibhav Kumar
    Prodigy 240 points

    Hi  Vaibhav

    I am so sorry  , the full FLASH PART Number  W25Q256JVEBQ

    The new datasheet is 

    0724.W25Q256JV AG Rev B 051618.pdf

    Regards,

    SUI

    Thanks

  • 0 in reply to pengfei sui
    TI__Guru 59465 points

    Hi,

    Thanks for sharing the same.

    Aryamaan, you can share with them the values for FLASH and OSPI.

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Kumar
    TI__Intellectual 3000 points

    Hi Pengfei,

    Please refer to the configurations attached below:

    Regards,

    Aryamaan Chaurasia

  • 0 in reply to Aryamaan Chaurasia
    Prodigy 240 points

    Hi  Aryamaan Chaurasia

    Now I use your configurations and I build all code , my board MCU WKUP_UART0  can not output any log, there is no wrong log and right log 

    I don't know  why I use demo   ospi_flash_diag.debug.appimage.hs_fs  can not output any log ?

    there is my download log and configurations 

    Regards,

    Pengfei

  • 0 in reply to pengfei sui
    TI__Intellectual 3000 points

    Hi Pengfei,

    Could you try using the default OSPI Flash Diagnostic example? Note: the OSPI driver would be added by default in SysConfig, there's no need to add a separate Flash instance.

    Regards,

    Aryamaan Chaurasia

  • 0 in reply to Aryamaan Chaurasia
    Prodigy 240 points

    Hi  Aryamaan Chaurasia

    YES , I can use the default OSPI Flash Diagnostic example at  AM62P EVM board 

    it is ok , the MCU WKUP_UART0  can output right log , you can check ,

    there is the  AM62P EVM board   OSPI Flash Diagnostic   log

    Fullscreen AM62P-SKEVM-OSPI_FLASH_DIAG.json.txt Download 
    Sciserver Testapp Built On: Dec  5 2025 10:29:29
Sciserver Version: v2025.04.0.0-REL.MCUSDK.K3.11.00.00.16+
RM_PM_HAL Version: v11.00.07
Starting Sciserver..... PASSED
[OSPI Flash Diagnostic Test] Starting ...
[OSPI Flash Diagnostic Test] Flash Manufacturer ID : 0x34
[OSPI Flash Diagnostic Test] Flash Device ID       : 0x5B1A
[OSPI Flash Diagnostic Test] Executing Flash Erase on first block...
[OSPI Flash Diagnostic Test] Done !!!
[OSPI Flash Diagnostic Test] Performing Write-Read Test...
[OSPI Flash Diagnostic Test] Write-Read Test Passed!
[OSPI Flash Diagnostic Test] SFDP Information : 
================================================
                      SFDP                      
================================================
SFDP Major Revision                       : 0x1
SFDP Minor Revision                       : 0x8
Number of Parameter Headers in this Table : 6

Types of Additional Parameter Tables in this flash
---------------------------------------------------
4 BYTE ADDRESSING MODE INSTRUCTIONS TABLE
NOR SPI PROFILE TABLE 
STATUS CONTROL AND CONFIGURATION REGISTER MAP TABLE
OCTAL DDR MODE COMMAND SEQUENCE TABLE
SECTOR MAP TABLE

Parsing of OCTAL DDR MODE COMMAND SEQUENCE TABLE table not yet supported. 
JSON Data for the flash :

{

	"flashSize": 67108864,
	"flashPageSize": 256,
	"flashManfId": "0x34",
	"flashDeviceId": "0x5B1A",
	"flashBlockSize": 262144,
	"flashSectorSize": 4096,
	"cmdBlockErase3B": "0xDC",
	"cmdBlockErase4B": "0xDC",
	"cmdSectorErase3B": "0x21",
	"cmdSectorErase4B": "0x21",
	"protos": {
		"p111": {
			"isDtr": false,
			"cmdRd": "0x03",
			"cmdWr": "0x02",
			"modeClksCmd": 0,
			"modeClksRd": 0,
			"dummyClksCmd": 0,
			"dummyClksRd": 0,
			"enableType": "0",
			"enableSeq": "0x00",
			"dummyCfg": null,
			"protoCfg": null,
			"strDtrCfg": null
		},
		"p112": null,
		"p114": null,
		"p118": null,
		"p444s": null,
		"p444d": null,
		"p888s": null,
		"p888d": {
			"isDtr": true,
			"cmdRd": "0xEE",
			"cmdWr": "0x12",
			"modeClksCmd": 0,
			"modeClksRd": 0,
			"dummyClksCmd": 4,
			"dummyClksRd": 24,
			"enableType": "0",
			"enableSeq": "0x00",
			"dummyCfg": {
				"isAddrReg": true,
				"cmdRegRd":"0x65",
				"cmdRegWr":"0x71",
				"cfgReg":"0x00800003",
				"shift":0,
				"mask":"0x03",
				"bitP":11
			},
			"protoCfg": {
				"isAddrReg": true,
				"cmdRegRd": "0x65",
				"cmdRegWr": "0x71",
				"cfgReg": "0x00800006",
				"shift": 0,
				"mask": "0x00",
				"bitP": 0
			},
			"strDtrCfg": {
				"isAddrReg": true,
				"cmdRegRd": "0x65",
				"cmdRegWr": "0x71",
				"cfgReg": "0x00800006",
				"shift": 1,
				"mask": "0x00",
				"bitP": 1
			}
		},
		"pCustom": { 
			"fxn": null
		}
	},
	"addrByteSupport": "1",
	"fourByteAddrEnSeq": "0xA0",
	"cmdExtType": "REPEAT",
	"resetType": "0x10",
	"deviceBusyType": "1",
	"cmdWren": "0x06",
	"cmdRdsr": "0x05",
	"srWip":  0,
	"srWel":  1,
	"cmdChipErase": "0xC7",
	"rdIdSettings": {
		"cmd": "0x9F",
		"numBytes": 5,
		"dummy4": 0,
		"dummy8": 0
	},
	"xspiWipRdCmd": "0x65",
	"xspiWipReg": "0x00800000",
	"xspiWipBit": 0,
	"flashDeviceBusyTimeout": 256000000,
	"flashPageProgTimeout": 512
}

All tests have passed!!

    Regards,

    Pengfei

  • +1 in reply to pengfei sui
    TI__Intellectual 3000 points

    Hi Pengfei,

    I meant running the Diagnostic example on the board which has the custom flash.

    Aryamaan Chaurasia said:
    Please refer to the configurations attached below:

    I have also edited my previous reply for the correct configurations. You can use those configurations to run the OSPI Flash IO example, running the OSPI Diagnostic example wont be required.

    Regards,

    Aryamaan Chaurasia