XLF208 XN file missng flash pins

Technical questions regarding the xTIMEcomposer, xSOFTip Explorer and Programming with XMOS.
aelder
Member++
Posts: 24
Joined: Mon Sep 24, 2012 1:45 pm

XLF208 XN file missng flash pins

Postby aelder » Thu May 10, 2018 1:19 pm

I'm working on a .xn file for custom hardware based on the XLF208.

I started with file XLF208-128-TQ64-C10 shipped with xTimeComposer tools. Since the XLF208 part has embedded flash, I was expecting to see sections that looked something like

Code: Select all

         <Boot>
            <Source Location="bootFlash"/>
          </Boot>
          <Tile Number="0" Reference="tile[0]">
            <Port Location="XS1_PORT_1B" Name="PORT_SQI_CS"/>
            <Port Location="XS1_PORT_1C" Name="PORT_SQI_SCLK"/>
            <Port Location="XS1_PORT_4B" Name="PORT_SQI_SIO"/>
          </Tile>

and

Code: Select all

  <ExternalDevices>
    <Device NodeId="0" Tile="0" Class="SQIFlash" Name="bootFlash" Type="S25FL116K">
      <Attribute Name="PORT_SQI_CS" Value="PORT_SQI_CS"/>
      <Attribute Name="PORT_SQI_SCLK"   Value="PORT_SQI_SCLK"/>
      <Attribute Name="PORT_SQI_SIO"  Value="PORT_SQI_SIO"/>
      <Attribute Name="QE_REGISTER" Value="quad_spi_qe_location_status_reg_0"/>
      <Attribute Name="QE_BIT" Value="quad_spi_qe_bit_6"/>
    </Device>
  </ExternalDevices>


But the above sections are missing. Is this pin specification done some other way that I am unaware of?

Thanks,
Andrew
User avatar
mon2
XCore Legend
Posts: 1066
Joined: Thu Jun 10, 2010 11:43 am
Contact:

Postby mon2 » Thu May 10, 2018 6:18 pm

Wow, that is an interesting observation. Indeed that section of the xn file is empty. Section 8 of the respective datasheet offers the details of this internal flash and how it is mapped.

Have you attempted to flash this internal device? If the empty xn file fails, consider to insert your definition using the port pins they note in the datasheet. Could be a toolchain typo so perhaps open a support ticket on the xmos.com website to receive proper closure on this case.
aelder
Member++
Posts: 24
Joined: Mon Sep 24, 2012 1:45 pm

Postby aelder » Thu May 10, 2018 6:28 pm

Thanks for the response. Yes, section 8 does look clear enough to me. I will open a support ticket.
matthew1
Active Member
Posts: 39
Joined: Mon Oct 19, 2015 2:12 pm

Postby matthew1 » Fri May 11, 2018 9:49 am

Looks a genuine issue to me, I'll follow up internally. In the short term, you could create a custom xn based on the XLF208-256-TQ64-C10.xn file (which is OK in 14.3.3) but change 256 to 128 where appropriate.

Cheers,

Matthew.
XMOS

Who is online

Users browsing this forum: No registered users and 10 guests