AM2732: AM2732 QSPI Boot/Custom Flash Device

y-oyama

Prodigy 20 points

Part Number: AM2732
Other Parts Discussed in Thread: TMDS273EVM, SYSCONFIG, UNIFLASH

Tool/software:

I tried the SDK's GPIO_LED_Blink using the TMDS273EVM.

I also used the SBL and UART Flash writer from SDK.

This was successful for both writing and QSPI Boot, and we could see the LEDs blinking.

Next, to practice the Custom Flash Device, we used the QSPI Flash Diag to read the SFDP table according to “Adding Support For a Custom Flash Device” in the User Guide.

I created an SBL using this SFDP table. I followed the same procedure for writing, but could not confirm that the LEDs blinked.

I attach the SFDP table that I read out myself.

Some parameter settings are different between the Sysconfig in the SDK and the one configured in the above procedure.

I checked the Datasheet of the Flash Device and could not reach the same settings as in the SDK.

Could you please tell me exactly what steps I need to take to set the correct values like in the Sysconfig of the SDK?

Fullscreen GD25B64CWAG.txt Download

{
 
	"flashSize": 8388608,
	"flashPageSize":256,
	"flashManfId": "0xC8",
	"flashDeviceId": "0x4017",
	"flashBlockSize": 65536,
	"flashSectorSize": 4096,
	"cmdBlockErase3B": "0xD8",
	"cmdBlockErase4B": "0xD8",
	"cmdSectorErase3B": "0x20",
	"cmdSectorErase4B": "0x20",
	"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": {
			"isDtr": false,
			"cmdRd": "0x3B",
			"cmdWr": "0x02",
			"modeClksCmd": 0,
			"modeClksRd": 0,
			"dummyClksCmd": 0,
			"dummyClksRd": 8,
			"enableType": "0",
			"enableSeq": "0x00",
			"dummyCfg": null,
			"protoCfg": null,
			"strDtrCfg": null
		},
		"p114": {
			"isDtr": false,
			"cmdRd": "0x6B",
			"cmdWr": "0x02",
			"modeClksCmd": 0,
			"modeClksRd": 0,
			"dummyClksCmd": 0,
			"dummyClksRd": 8,
			"enableType": "2",
			"enableSeq": "0x00",
			"dummyCfg": null,
			"protoCfg": null,
			"strDtrCfg": null
		},
		"p118": null,
		"p444s": null,
		"p444d": null,
		"p888s": null,
		"p888d": null,
		"pCustom": null
	},
	"addrByteSupport": "0",
	"fourByteAddrEnSeq": "0x00",
	"resetType": "0x10",
	"cmdWren": "0x06",
	"cmdRdsr": "0x05",
	"srWip": 0,
	"srWel": 1,
	"cmdChipErase": "0xC7",
	"flashDeviceBusyTimeout": 0,
	"flashPageProgTimeout": 400
}

2 months ago

0 Daniel Bermudez 2 months ago

TI__Expert 7690 points

Hello,

So did the automatic import function from the sdk failed to populate the correct values? we normally recommend to double check the resulting sfdp from the example to make sure the flash is configured correctly as per its datasheet. I've had issues in the past using the JSON import of the sdk so I would suggest filling in the information manually to avoid this variable.

y-oyama said:
I checked the Datasheet of the Flash Device and could not reach the same settings as in the SDK.

Could you please tell me exactly what steps I need to take to set the correct values like in the Sysconfig of the SDK?

updating manually should work just fine, make sure things like the size of the flash, operating commands, and frequency are correctly reflected in the SDK

Keep in mind that the uniflash example must also be modified as for the flash writer to work correctly with your new device

Best,

Daniel

Processors

Processors forum

AM2732: AM2732 QSPI Boot/Custom Flash Device