RT1064 update procedure

[mrecoskie]

Hi,

I am trying to create a command line procedure for committing new firmware to the RT1064 - via USB from Linux.  I am using the standard RT1064 evaluation board.  

I first use sdphost to burn the flashloader image to the 1064 using the sdphost tool.  ivt_flashloader.bin was extracted from the package ‘Flashloader_RT106x_1.0_GA’.

Then I boot it.  However afterwards when I list the memory using blhost - the Internal Flash is not present/recognized.  This prevents me from writing new firmware to it.  Could someone review my procedure below and provide suggestions?  Thanks.

Mark

[m@localhost nxp-tools]$ lsusb
Bus 001 Device 003: ID 1fc9:0135 NXP Semiconductors 
Bus 001 Device 002: ID 203a:fffa PARALLELS 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 203a:fffc PARALLELS 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[m@localhost nxp-tools]$ sudo ./sdphost -u 0x1fc9,0x0135 -- write-file 0x20000000 "ivt_flashloader.bin" 
Preparing to send 90529 (0x161a1) bytes to the target.
(1/1)0%Status (HAB mode) = 1450735702 (0x56787856) HAB disabled.
Reponse Status = 2290649224 (0x88888888) Write File complete.

[m@localhost nxp-tools]$ sudo ./sdphost -u 0x1fc9,0x0135 -- jump-address 0x20000400
Status (HAB mode) = 1450735702 (0x56787856) HAB disabled.

[m@localhost nxp-tools]$ lsusb
Bus 001 Device 004: ID 15a2:0073 Freescale Semiconductor, Inc. 
Bus 001 Device 002: ID 203a:fffa PARALLELS 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 203a:fffc PARALLELS 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[m@localhost nxp-tools]$ sudo ./blhost -u 0x15a2,0x0073 -- list-memory
Inject command 'list-memory'
Internal Flash:
  No Internal Flash available
Internal RAM:
  Region 0: 0x00000000 - 0x0001ffff; Total size: 128 KB
  Region 1: 0x20000000 - 0x2001ffff; Total size: 128 KB
  Region 2: 0x20200000 - 0x202bffff; Total size: 768 KB
SEMC NOR:
  kStatusMemoryNotConfigured
FlexSPI NOR:
  kStatusMemoryNotConfigured
SEMC NAND:
  kStatusMemoryNotConfigured
SPI NAND:
  kStatusMemoryNotConfigured
SPI NOR/EEPROM:
  kStatusMemoryNotConfigured
SD/SDHC:
  kStatusMemoryNotConfigured
MMC/eMMC:
  kStatusMemoryNotConfigured  

[PrestonSmith · Accepted solution]

Exactly what I needed! You just saved me several hours. Thanks!

FaceTime App

[jeremyzhou]

Hi @mrecoskie ,
Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
For RT1064, the internal flash is completely different from the general MCU's internal flash, such as Kinetis and LPC series MCU, RT1064 contains an external QSPI in its package, so its 'internal flash' is an external flash essentially.
So the list-memory command can't recognize it.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[mrecoskie]

Hi.  Thanks.   That makes sense.  

Do you know the next steps which can be used to burn the flash via command line??

Mark

[jeremyzhou]

Hi,
Thanks for your reply.
1) Do you know the next steps which can be used to burn the flash via the command line??
-- I'd like to suggest you use the MCUXpresso Secure Provisioning tool to program an image to the RT1064, plus the log of the tool illustrates the commands to do it.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------