XCore Exchange

After trying to establish communication for many hours, I find out the datasheet info for used flash memory include wrong Device ID number: 0x1f8401 instead of 0x1f8501. With proper config file (i.e. Adesto.txt) the xflash returns the following (Don't forget to first run source SetEnv on Linux!):

./xflash --spi-read-id 0x9f --spi-spec Adesto.txt --target EEZ-XE216-512-EVAL --verbose
XFlash_Options::ListDevices : xgdb --batch -q --ex listdevices devl-b5da9800
XFlash::DoXFlash
XFlash::DoReadWriteErase
XFlash_Programmer_ReadDeviceID::ReadDeviceId
XFlash_Programmer_ReadDeviceID::GenerateSource
XFlash_SPI_DeviceId::IssueCompileCommand : xcc -Xmapper --dontenablesodlinks -Xmapper --wnoXN -x xc "sqi-ad4453d6" -x xn "/media/denis/SSD_256GB/BACKUP/EEZ/XMOS/Community_14.3.2/targets/EEZ-XE216-512-EVAL/EEZ-XE216-512-EVAL.xn" -o "sqi-2245beff" -lquadflash -D xnPORT_SQI_CS0=PORT_SQI_CS -D xnPORT_SQI_SCLK0=PORT_SQI_SCLK -D xnPORT_SQI_SIO0=PORT_SQI_SIO
XFlash_Utils::BuildRunCommand : xrun --io sqi-2245beff
Response to SPI ID command on tile[0]: 0x1f, 0x85, 0x1.

Hi. Thanks for the closure. Is it possible that you actually soldered into your PCB the AT25SF081 device?

From the AT25SF081 datasheet:

https://www.adestotech.com/wp-content/u ... 81_045.pdf




From the AT25SF041 datasheet:

https://www.adestotech.com/wp-content/u ... 41_044.pdf

Argh, that's crazy! Yes, you are right, for some reason a wrong flash is ordered and soldered on two boards :(. Updated header and config files are attached for further reference.

On a positive note, you have more code space than you originally thought for more complex led blinky projects :) That is what I hear from my staff members all the time :)