Re: xCore-200 MC dev board - failed to connect to SQI flash device with sample code
Posted: Wed Oct 30, 2019 10:15 pm
Hi mon2,
Appreciate the good info! I'm looking at the board now, but here's a few answers to your questions straight off.
1) out of the box, does XMOS ship with onboard firmware on this kit? Perhaps some LEDs blink on the LED array? Please confirm this firmware detail as it is important.
== Nothing whatsoever, the board is dead as a Dodo with the exception of a a few PSU LEDs. No USB enumeration, nothing.
2) If the kit does feature some factory based firmware then most likely this firmware is loading from the external QSPI flash device. This relationship should validate that the flash device is operational and properly connected to the XMOS CPU on this kit. If there is no firmware supplied inside this external flash, continue to read on...
== Agree, but dead code-wise.
3) The read ID SPI flash command should have returned the ID of the external flash device. The 9fh ID command is common to many flash devices and is listed inside the ISSI datasheet. As long as the XN file is properly mapping the port pains to the proper external flash device, the xflash tool should have worked. From an earlier review of this thread, believe your XN file looked ok.
== This is interesting and I think perhaps I'm missing or assuming something here. Having a look at the board then the schematics the SPI flash is in no way connected to the xTAG3 header ( J9 ) directly as some programmers are to the device they're programming. The SPI flash is hanging off the xmos so am I correct to assume it plays a role with some sort of xTAG3 to SPI chuck of firmware? If so maybe that's the issue?
4) Can you confirm again on the part markings on the flash device onboard your kit? The XMOS schematic notes an ISSI IS25LQ080B @ U24. Perhaps the schematic is out of sync but worthwhile to review.
== Definitely a IS25LQ016BNLE ( U24 ) Yes, looks like the schematics are slightly out.. There's a white sticker on my board with 1904-00095 if it means anything.
These questions aside, I've seen a lot of mention about *.bin files which are required to be loaded in to the flash; looking through the directories of xTimeComposer I don't see a single bin. Although not immediately relevant to my SPI communication issue can the xTimeComposer produce *.bins in some sort of "release" build once I'm past this problem?
Thanks again, I now going to go through some of your other suggestion..
Appreciate the good info! I'm looking at the board now, but here's a few answers to your questions straight off.
1) out of the box, does XMOS ship with onboard firmware on this kit? Perhaps some LEDs blink on the LED array? Please confirm this firmware detail as it is important.
== Nothing whatsoever, the board is dead as a Dodo with the exception of a a few PSU LEDs. No USB enumeration, nothing.
2) If the kit does feature some factory based firmware then most likely this firmware is loading from the external QSPI flash device. This relationship should validate that the flash device is operational and properly connected to the XMOS CPU on this kit. If there is no firmware supplied inside this external flash, continue to read on...
== Agree, but dead code-wise.
3) The read ID SPI flash command should have returned the ID of the external flash device. The 9fh ID command is common to many flash devices and is listed inside the ISSI datasheet. As long as the XN file is properly mapping the port pains to the proper external flash device, the xflash tool should have worked. From an earlier review of this thread, believe your XN file looked ok.
== This is interesting and I think perhaps I'm missing or assuming something here. Having a look at the board then the schematics the SPI flash is in no way connected to the xTAG3 header ( J9 ) directly as some programmers are to the device they're programming. The SPI flash is hanging off the xmos so am I correct to assume it plays a role with some sort of xTAG3 to SPI chuck of firmware? If so maybe that's the issue?
4) Can you confirm again on the part markings on the flash device onboard your kit? The XMOS schematic notes an ISSI IS25LQ080B @ U24. Perhaps the schematic is out of sync but worthwhile to review.
== Definitely a IS25LQ016BNLE ( U24 ) Yes, looks like the schematics are slightly out.. There's a white sticker on my board with 1904-00095 if it means anything.
These questions aside, I've seen a lot of mention about *.bin files which are required to be loaded in to the flash; looking through the directories of xTimeComposer I don't see a single bin. Although not immediately relevant to my SPI communication issue can the xTimeComposer produce *.bins in some sort of "release" build once I'm past this problem?
Thanks again, I now going to go through some of your other suggestion..