Imxrt1064 mfg tool flash issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Imxrt1064 mfg tool flash issue

1,745 Views
vasudhevan
Contributor V

Hi,

     I have referred https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/Generating-a-Bootable-Image-for-the-RT1050/ta-p/... link in bootable image generation - XIP Hyperflash section.

     This method working fine application using example code (evkmimxrt1064_sdcard_fatfs) SRAM_DTC.

     Our project RAM we used OCRAM we followed bootable image generation - XIP Hyperflash method for generating boot image. using mfg tool we flashed board.

     After flashed unable to see our debug message. means our code is not running.

     If we use ocram generating boot image we have to follow some other method ?

     Why ocram bootable  image not working ?

     How to solve this issue ?

 

Thanks & Regards,

        Vasu

 

Labels (1)
0 Kudos
12 Replies

1,739 Views
jeremyzhou
NXP Employee
NXP Employee

Hi, 

Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
1) Why ocram bootable image not working?
-- To use the ocram, the application should store into the area whose address exceeds the 0x20208000, as the ROM code also use some area of the ocram.
So give a try.

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.
-------------------------------------------------------------------------------

0 Kudos

1,732 Views
vasudhevan
Contributor V

Hi @jeremyzhou ,

       Thanks for your reply.

       Which place we have to change  0x20208000 address ?

       

Thanks & Regards,

       Vasu

0 Kudos

1,726 Views
vasudhevan
Contributor V

Hi,

      I have modified MCU settings but our code is not running.

     ocram.PNG

 

Regards,

 Vasu

0 Kudos

1,716 Views
jeremyzhou
NXP Employee
NXP Employee

Hi,

Thanks for your reply.
After confirming, for the Non-XIP image, this should store into the area whose address starts the 0x20209000, just like the below shows.

ocram.PNG

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.
-------------------------------------------------------------------------------

0 Kudos

1,709 Views
vasudhevan
Contributor V

Hi @jeremyzhou 

     Thanks for your reply.

     Our image size is more than 2mb it won't fit for boot from ocram.

     We want to boot from XIP.

     ocram1.PNG

    again same issue not booting.

     Followed Steps:

     XIP_BOOT_HEADER_DCD_ENABLE=0

     XIP_BOOT_HEADER_ENABLE=0

     elftosb.exe -f imx -V -c ..\..\bd_file\imx10xx\imx-flexspinor-normal-unsigned.bd -o test.bin test.srec.

    elftosb.exe -f kinetis -V -c ..\..\bd_file\imx10xx\program_flexspinor_image_qspinor.bd -o boot_image.sb test_no_padding.bin

Anything we are missed ?

Regards,

  Vasu

0 Kudos

1,694 Views
jeremyzhou
NXP Employee
NXP Employee

Thanks for your reply.
It seems a bit weird, you can try to program your demo project to
i.MX RT1064 via the MCUXpreeso IDE instead of mfg tool flash, then check the demo project whether can boot up or not.

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.
-------------------------------------------------------------------------------

0 Kudos

1,688 Views
vasudhevan
Contributor V

Hi @jeremyzhou

     Thanks for your reply.

     Above mentioned steps followed for generating boot image for example project.

     Our project  SRAM_DTC, SRAM_ITC memory is not sufficient then we used ocram.

     MCU express we can able to debug and flash.

     But mfg tool flashed image is not working.

    Our project preprocessor macros.

     

 

MBEDTLS_CONFIG_FILE='"mbedtls_config_client.h"'
FSL_FEATURE_PHYKSZ8081_USE_RMII50M_MODE
XIP_BOOT_HEADER_DCD_ENABLE=0
HTTPSRV_CFG_WEBSOCKET_ENABLED=0
CPU_MIMXRT1064DVL6A
FSL_SDK_ENABLE_DRIVER_CACHE_CONTROL=1
SKIP_SYSCLK_INIT
CPU_MIMXRT1064DVL6A_cm7
SDK_DEBUGCONSOLE=1
XIP_EXTERNAL_FLASH=1
XIP_BOOT_HEADER_ENABLE=0
FSL_RTOS_FREE_RTOS
USE_RTOS=1
SERIAL_PORT_TYPE_UART=1
CR_INTEGER_PRINTF
PRINTF_FLOAT_ENABLE=1
PRINTF_ADVANCED_ENABLE=1
__MCUXPRESSO
__USE_CMSIS
DEBUG
__REDLIB__

 

 

 

Regards, 

  Vasu

0 Kudos

1,669 Views
jeremyzhou
NXP Employee
NXP Employee

Hi,

Thanks for your reply.
Do you mean the bootable image can boot up after be programed by the MCUXpresso, however, it will fail when using the mfg tool to program, is it right?
The MCUBootUtility tool allows the user to observe the bootable image in the i.MX RT1064's internal flash, so you can use this tool to compare the bootable image that programed by the mfg tool and MCUXPresso IDE, I think it can provide some clues for us to figure it out.
Please give a try.
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.
-------------------------------------------------------------------------------

0 Kudos

1,624 Views
vasudhevan
Contributor V

Hi @jeremyzhou ,

      Thanks for your reply.

      MCUBootUtility tool it's not working for me because of windows 8.1 os.

      Step followed for generating bootable image for OCRAM with XIP.

         Imported -> evkmimxrt1064_lwip_tcpecho_freertos example code.

         Modified OCRAM address.

         ocram11.PNG

ocram12.PNGocram13.PNG

 elftosb.exe -f imx -V -c ..\..\bd_file\imx10xx\imx-flexspinor-normal-unsigned.bd -o evkmimxrt1064_lwip_tcpecho_freertos.bin evkmimxrt1064_lwip_tcpecho_freertos.srec
elftosb.exe -f kinetis -V -c ..\..\bd_file\imx10xx\program_flexspinor_image_qspinor.bd -o boot_image.sb evkmimxrt1064_lwip_tcpecho_freertos.bin

 

  I have attached example code for your reference.

 If possible can you share example code along with procedure for generating bootable image OCRAM with XIP and NON XIP image.

  No where mentioned how to generate bootable image for ocram.

 

Thanks & Regards,

     Vasu 

 

0 Kudos

1,615 Views
jeremyzhou
NXP Employee
NXP Employee

Thanks for your reply.
After going through the steps, I don't find something wrong except for the application start address, it should be 0x70002000 instead of 0x70000000.
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.
-------------------------------------------------------------------------------

0 Kudos

1,607 Views
vasudhevan
Contributor V

Hi @jeremyzhou,

     Thanks for your reply.

     I have modified to 0x70002000.

     ooo1.PNG

elftosb.exe -f imx -V -c ..\..\bd_file\imx10xx\imx-flexspinor-normal-unsigned.bd -o evkmimxrt1064_lwip_tcpecho_freertos.bin evkmimxrt1064_lwip_tcpecho_freertos.srec

ooo2.PNG

 After change not able to generate .bin file.

Thanks & Regards,

      Vasu

0 Kudos

1,579 Views
jeremyzhou
NXP Employee
NXP Employee

Hi,

Thanks for your reply and the SRAM_OC configuration is not right.
Please follow the below configuration.

jeremyzhou_0-1601435678980.png

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.
-------------------------------------------------------------------------------

0 Kudos