RT-UFL settings for Adesto EcoXIP flash to work with J-Link?

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

RT-UFL settings for Adesto EcoXIP flash to work with J-Link?

Jump to solution
3,008 Views
jackking
Senior Contributor I

I am looking for the working RT-UFL settings to use J-Link latest drivers with Adesto EcoXIP flash (on an Embedded Artists iMXRT1062 module).  I followed: https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/RT1170-Octal-flash-enablement/ta-p/1498369 which isn't specifically for the Adesto Flash part.

It seems to be able to communicate with flash, performing a compare, but then it fails to erase or program the flash with any new compilation.

I have tried modifying the JLinkDevice.xml with variations of:

<Device>
    <ChipInfo      Vendor="Embedded Artists"
                   Name="MIMXRT1062_EA"
                   WorkRAMAddr="0x00000000"
                   WorkRAMSize="0x00020000"
                   Core="JLINK_CORE_CORTEX_M7"
                   Aliases="MIMXRT1061xxx5A; MIMXRT1061xxx6A; MIMXRT1062xxx5A; MIMXRT1062xxx6A" />
    <FlashBankInfo Name="HyperFlash"
                   BaseAddr="0x60000000"
                   MaxSize="0x04000000"
                   Loader="Devices/NXP/iMXRT_UFL/MIMXRT_FLEXSPI_UFL_512B_4KB.FLM"
                   LoaderType="FLASH_ALGO_TYPE_OPEN" />
</Device>

 

You can see this from the Support console log:

Received monitor command: reset
ResetTarget() start
ResetTarget() end - Took 126ms
AfterResetTarget() start
AfterResetTarget() end - Took 2.60ms
Resetting target
Downloading 8192 bytes @ address 0x60000000 - Verified OK
Downloading 16032 bytes @ address 0x60002000 - Verified OK
Downloading 16032 bytes @ address 0x60005EA0 - Verified OK
Downloading 16128 bytes @ address 0x60009D40 - Verified OK
Downloading 16000 bytes @ address 0x6000DC40 - Verified OK
Downloading 16096 bytes @ address 0x60011AC0 - Verified OK
Downloading 16128 bytes @ address 0x600159A0 - Verified OK
Downloading 16096 bytes @ address 0x600198A0 - Verified OK
Downloading 16096 bytes @ address 0x6001D780 - Verified OK
Downloading 15968 bytes @ address 0x60021660 - Verified OK
Downloading 15984 bytes @ address 0x600254C0 - Verified OK
Downloading 15984 bytes @ address 0x60029330 - Verified OK
Downloading 16032 bytes @ address 0x6002D1A0 - Verified OK
Downloading 16096 bytes @ address 0x60031040 - Verified OK
Downloading 16160 bytes @ address 0x60034F20 - Verified OK
Downloading 16144 bytes @ address 0x60038E40 - Verified OK
Downloading 16160 bytes @ address 0x6003CD50 - Verified OK
Downloading 16144 bytes @ address 0x60040C70 - Verified OK
Downloading 16144 bytes @ address 0x60044B80 - Verified OK
Downloading 16160 bytes @ address 0x60048A90 - Verified OK
Downloading 16144 bytes @ address 0x6004C9B0 - Verified OK
Downloading 16096 bytes @ address 0x600508C0 - Verified OK
Downloading 16064 bytes @ address 0x600547A0 - Verified OK
Downloading 16048 bytes @ address 0x60058660 - Verified OK
Downloading 16176 bytes @ address 0x6005C510 - Verified OK
Downloading 16176 bytes @ address 0x60060440 - Verified OK
Downloading 16192 bytes @ address 0x60064370 - Verified OK
Downloading 16208 bytes @ address 0x600682B0 - Verified OK
Downloading 16192 bytes @ address 0x6006C200 - Verified OK
Downloading 16160 bytes @ address 0x60070140 - Verified OK
Downloading 16176 bytes @ address 0x60074060 - Verified OK
Downloading 16176 bytes @ address 0x60077F90 - Verified OK
Downloading 16176 bytes @ address 0x6007BEC0 - Verified OK
Downloading 16192 bytes @ address 0x6007FDF0 - Verified OK
Downloading 16160 bytes @ address 0x60083D30 - Verified OK
Downloading 16160 bytes @ address 0x60087C50 - Verified OK
Downloading 16160 bytes @ address 0x6008BB70 - Verified OK
Downloading 16128 bytes @ address 0x6008FA90 - Verified OK
Downloading 16160 bytes @ address 0x60093990 - Verified OK
Downloading 16144 bytes @ address 0x600978B0 - Verified OK
Downloading 16176 bytes @ address 0x6009B7C0 - Verified OK
Downloading 16128 bytes @ address 0x6009F6F0 - Verified OK
Downloading 16144 bytes @ address 0x600A35F0 - Verified OK
Downloading 16176 bytes @ address 0x600A7500 - Verified OK
Downloading 16160 bytes @ address 0x600AB430 - Verified OK
Downloading 16144 bytes @ address 0x600AF350 - Verified OK
Downloading 16080 bytes @ address 0x600B3260 - Verified OK
Downloading 16032 bytes @ address 0x600B7130 - Verified OK
Downloading 16096 bytes @ address 0x600BAFD0 - Verified OK
Downloading 16176 bytes @ address 0x600BEEB0 - Verified OK
Downloading 16032 bytes @ address 0x600C2DE0 - Verified OK
Downloading 16160 bytes @ address 0x600C6C80 - Verified OK
Downloading 16080 bytes @ address 0x600CABA0 - Verified OK
Downloading 16176 bytes @ address 0x600CEA70 - Verified OK
Downloading 16112 bytes @ address 0x600D29A0 - Verified OK
Downloading 16032 bytes @ address 0x600D6890 - Verified OK
Downloading 16144 bytes @ address 0x600DA730 - Verified OK
Downloading 16064 bytes @ address 0x600DE640 - Verified OK
Downloading 16080 bytes @ address 0x600E2500 - Verified OK
Downloading 16144 bytes @ address 0x600E63D0 - Verified OK
Downloading 16128 bytes @ address 0x600EA2E0 - Verified OK
Downloading 16080 bytes @ address 0x600EE1E0 - Verified OK
Downloading 16128 bytes @ address 0x600F20B0 - Verified OK
Downloading 16096 bytes @ address 0x600F5FB0 - Verified OK
Downloading 16112 bytes @ address 0x600F9E90 - Verified OK
Downloading 16192 bytes @ address 0x600FDD80 - Verified OK
Downloading 16208 bytes @ address 0x60101CC0 - Verified OK
Downloading 16016 bytes @ address 0x60105C10 - Verified OK
Downloading 16112 bytes @ address 0x60109AA0 - Verified OK
Downloading 16112 bytes @ address 0x6010D990 - Verified OK
Downloading 16080 bytes @ address 0x60111880 - Verified OK
Downloading 16192 bytes @ address 0x60115750 - Verified OK
Downloading 16192 bytes @ address 0x60119690 - Verified OK
Downloading 16016 bytes @ address 0x6011D5D0 - Verified OK
Downloading 16160 bytes @ address 0x60121460 - Verified OK
Downloading 16064 bytes @ address 0x60125380 - Verified OK
Downloading 16048 bytes @ address 0x60129240 - Verified OK
Downloading 16144 bytes @ address 0x6012D0F0 - Verified OK
Downloading 16128 bytes @ address 0x60131000 - Verified OK
Downloading 15952 bytes @ address 0x60134F00 - Verified OK
Downloading 16096 bytes @ address 0x60138D50 - Verified OK
Downloading 15952 bytes @ address 0x6013CC30 - Verified OK
Downloading 16032 bytes @ address 0x60140A80 - Verified OK
Downloading 16032 bytes @ address 0x60144920 - Verified OK
Downloading 16064 bytes @ address 0x601487C0 - Verified OK
Downloading 16016 bytes @ address 0x6014C680 - Verified OK
Downloading 16048 bytes @ address 0x60150510 - Verified OK
Downloading 16128 bytes @ address 0x601543C0 - Verified OK
Downloading 16080 bytes @ address 0x601582C0 - Verified OK
Downloading 16128 bytes @ address 0x6015C190 - Verified OK
Downloading 16096 bytes @ address 0x60160090 - Verified OK
Downloading 16144 bytes @ address 0x60163F70 - Verified OK
Downloading 16080 bytes @ address 0x60167E80 - Verified OK
Downloading 16224 bytes @ address 0x6016BD50 - Verified OK
Downloading 16208 bytes @ address 0x6016FCB0 - Verified OK
Downloading 16256 bytes @ address 0x60173C00 - Verified OK
Downloading 16176 bytes @ address 0x60177B80 - Verified OK
Downloading 16320 bytes @ address 0x6017BAB0 - Verified OK
Downloading 16320 bytes @ address 0x6017FA70 - Verified OK
Downloading 16304 bytes @ address 0x60183A30 - Verified OK
Downloading 12256 bytes @ address 0x601879E0 - Verified OK
Downloading 11252 bytes @ address 0x6018A9C0 - Verified OK
Downloading 5296 bytes @ address 0x6018D5B4 - Verified OK
Downloading 16364 bytes @ address 0x6018EA64 - Verified OK
Downloading 16352 bytes @ address 0x60192A50 - Verified OK
Downloading 16352 bytes @ address 0x60196A30 - Verified OK
Downloading 16352 bytes @ address 0x6019AA10 - Verified OK
Downloading 16352 bytes @ address 0x6019E9F0 - Verified OK
Downloading 16352 bytes @ address 0x601A29D0 - Verified OK
Downloading 16352 bytes @ address 0x601A69B0 - Verified OK
Downloading 16352 bytes @ address 0x601AA990 - Verified OK
Downloading 16352 bytes @ address 0x601AE970 - Verified OK
Downloading 16352 bytes @ address 0x601B2950 - Verified OK
Downloading 16352 bytes @ address 0x601B6930 - Verified OK
Downloading 16352 bytes @ address 0x601BA910 - Verified OK
Downloading 16352 bytes @ address 0x601BE8F0 - Verified OK
Downloading 16352 bytes @ address 0x601C28D0 - Verified OK
Downloading 16352 bytes @ address 0x601C68B0 - Verified OK
Downloading 16352 bytes @ address 0x601CA890 - Verified OK
Downloading 16352 bytes @ address 0x601CE870 - Verified OK
Downloading 16352 bytes @ address 0x601D2850 - Verified OK
Downloading 16352 bytes @ address 0x601D6830 - Verified OK
Downloading 16352 bytes @ address 0x601DA810 - Verified OK
Downloading 16352 bytes @ address 0x601DE7F0 - Verified OK
Downloading 16352 bytes @ address 0x601E27D0 - Verified OK
Downloading 16352 bytes @ address 0x601E67B0 - Verified OK
Downloading 16352 bytes @ address 0x601EA790 - Verified OK
Downloading 16352 bytes @ address 0x601EE770 - Verified OK
Downloading 10772 bytes @ address 0x601F2750 - Verified OK
Downloading 16140 bytes @ address 0x601F5164 - Verified OK
Downloading 16208 bytes @ address 0x601F9070 - Verified OK
Downloading 2252 bytes @ address 0x601FCFC0 - Verified OK
Downloading 179 bytes @ address 0x601FD88C - Verified OK
Writing register 'pc' = 0x60002364
ERROR: Failed to erase sectors.

Read 2 bytes @ address 0x60136F38 (Data = 0x0000)
Read 2 bytes @ address 0x60163594 (Data = 0x0000)
Read 4 bytes @ address 0x60002364 (Data = 0x00000000)
Read 4 bytes @ address 0x60002364 (Data = 0x00000000)
Read 2 bytes @ address 0x60136F38 (Data = 0x0000)
Read 2 bytes @ address 0x60163594 (Data = 0x0000)
Reading common registers: Read register 'r0' (4 bytes) from hardware: 0x01000000
Read register 'r1' (4 bytes) from hardware: 0x00000100
Read register 'r2' (4 bytes) from hardware: 0x00000000
Read register 'r3' (4 bytes) from hardware: 0xF0900000
Read register 'r4' (4 bytes) from hardware: 0x00200060
Read register 'r5' (4 bytes) from hardware: 0x703A2020
Read register 'r6' (4 bytes) from hardware: 0x92652671
Read register 'r7' (4 bytes) from hardware: 0xF0000000
Read register 'r8' (4 bytes) from hardware: 0x00032000
Read register 'r9' (4 bytes) from hardware: 0x34A70000
Read register 'r10' (4 bytes) from hardware: 0x00000000
Read register 'r11' (4 bytes) from hardware: 0x00800F40
Read register 'r12' (4 bytes) from hardware: 0x00000000
Read register 'sp' (4 bytes) from hardware: 0x509B0000
Read register 'lr' (4 bytes) from hardware: 0xA1440000
Read register 'pc' (4 bytes) from hardware: 0x509B0000
Read register 'xpsr' (4 bytes) from hardware: 0x00000021
Read 4 bytes @ address 0x00009B50 (Data = 0x22BD3FFB)
Read 2 bytes @ address 0x00009B50 (Data = 0x3FFB)
Read 2 bytes @ address 0x6002C538 (Data = 0x0000)
Read 4 bytes @ address 0x000044A0 (Data = 0x602FA6EB)
Read 2 bytes @ address 0x000044A0 (Data = 0xA6EB)
Read 4 bytes @ address 0x000044A0 (Data = 0x602FA6EB)
Read 2 bytes @ address 0x000044A0 (Data = 0xA6EB)
Received monitor command: semihosting enable
Semi-hosting enabled (Handle on breakpoint instruction hit)
Received monitor command: exec SetRestartOnClose=1
Executed SetRestartOnClose=1
Received monitor command: reset
ResetTarget() start
Invalid flash header detected.
Target halted on flash header read.
ResetTarget() end - Took 241ms
AfterResetTarget() start
AfterResetTarget() end - Took 1.12ms
Resetting target
Setting breakpoint @ address 0x6002C538, Kind = 2, Type = THUMB, BPHandle = 0x0001
Starting target CPU...

 

0 Kudos
1 Solution
2,341 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

   I can make it works on my side now.

Check the Jflash downloading and the debug downloading situation.

kerryzhou_0-1687774525189.png

kerryzhou_1-1687774534102.png

Now follow me.

Please download the attachment.

1. copy MIMXRT106X_FLEXSPI.elf to 

C:\Program Files\SEGGER\JLINKV768B\Devices\NXP\iMXRT_UFL

2. copy JLinkDevices.xml to C:\Program Files\SEGGER\JLINKV768B

3. click C:\Program Files\SEGGER\JLINKV768B\JLinkDLLUpdater.exe

Then, you can use the Jflash to connect and program.

4. About the MCUXPresso IDE download

  Still like your previous settings, just change the device name to: MIMXRT1060_ATX032

Then test it.

Please note, in your project, you need to configure the xip folder file to the adesto code.

copy evkmimxrt1060_flexspi_nor_config.c and exip_defs.h to your xip folder.

 

Best Regards,

Kerry

 

 

 

 

 

View solution in original post

0 Kudos
20 Replies
2,342 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

   I can make it works on my side now.

Check the Jflash downloading and the debug downloading situation.

kerryzhou_0-1687774525189.png

kerryzhou_1-1687774534102.png

Now follow me.

Please download the attachment.

1. copy MIMXRT106X_FLEXSPI.elf to 

C:\Program Files\SEGGER\JLINKV768B\Devices\NXP\iMXRT_UFL

2. copy JLinkDevices.xml to C:\Program Files\SEGGER\JLINKV768B

3. click C:\Program Files\SEGGER\JLINKV768B\JLinkDLLUpdater.exe

Then, you can use the Jflash to connect and program.

4. About the MCUXPresso IDE download

  Still like your previous settings, just change the device name to: MIMXRT1060_ATX032

Then test it.

Please note, in your project, you need to configure the xip folder file to the adesto code.

copy evkmimxrt1060_flexspi_nor_config.c and exip_defs.h to your xip folder.

 

Best Regards,

Kerry

 

 

 

 

 

0 Kudos
2,309 Views
jackking
Senior Contributor I

@kerryzhou   Thanks!  I was able to get the flash programmed once, after that it skips the programming (?) on subsequent debug sessions.  So it sorta works, but not completely for me.

0 Kudos
2,291 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

  Jflash download works Ok right?

  In fact, the IDE also can download it OK.

  It means the flashloader can download now. For the debug, it may related to the script.

   You can use JLINK download the code in the meanwhile, any other issues, please create the new case, as this case is really a little old, thanks a lot for your understanding.

Best Regards,

Kerry

0 Kudos
2,345 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

   I have borrowed one validation board that can make the RT1060+ATXP032 work with the serial download mode, then boot works Ok in internal boot mode. the original RT-UFL really has issues for the ATP032 with JLINK.

  It is related to the flashdriver, I am trying to modify the RT-UFL source code, please keep patient, any updated information, I will let you know.

Best Regards,

Kerry 

0 Kudos
2,962 Views
jackking
Senior Contributor I

@kerryzhouDo you have any tips on setting the RT-UFL correctly?

 

0 Kudos
2,947 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

    Sorry for my later reply, as this case is taken by my colleague, so I didn't find this case in our working box.

  Anyway, reply you at first.

   Which flash you are using now? 

AT25SL128A?

   What's the detail board and RT chip you are using, please share the board link.

  Seems you are using the 3rd part email to create the question post, please use the company email to create the account and the question post, then it will have higher support priority, and I also can help you to check with adesto, they may have the related flashloader for your reference.

 

Wish it helps you!

Best Regards,

Kerry

   

0 Kudos
2,938 Views
jackking
Senior Contributor I

@kerryzhouThanks.

We are using the Adesto ATXP032 EcoXIP part (https://www.nxp.com/docs/en/white-paper/NXPADESTOWP.pdf)

Adesto was acquired by Renesas and subsequently dropped the EcoXIP line.

I am using the MIMXRT1062CVL5A as part of an Embedded Artists iMXRT1062 module, not a custom board. (https://www.embeddedartists.com/products/imx-rt1062-oem/)  Embedded Artists has also dropped the use of the Adesto part, moving to a QuadSPI flash now.

This Adesto part is supported by MCUXpresso with the EcoXIP driver:
Notification_Center.png

This is my only email address.



0 Kudos
2,875 Views
jackking
Senior Contributor I

@kerryzhouDo you have any recommendations for this?

0 Kudos
2,758 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

  So sorry for my later reply, as this case is not in my box, so the updated information will be ignored when I have a lot of my own box cases updated(to be honest, a little overflow now).

   Here, at first, you need to make sure your board is really working with the adesto ATXP032  flash, 

Just make sure your hardware has no problem.

You can use the MCUbootutility to test it at first in the serial download mode with USB or the UART:

kerryzhou_0-1686623142081.png

https://github.com/JayHeng/NXP-MCUBootUtility/releases/tag/v5.1.0
the related user manual is:
https://github.com/JayHeng/NXP-MCUBootUtility

After it works, then we can do the RT-UFL debugging, make sure, the RT-UFL can do the erase, program, read, etc, then generate the file for the JLINK.

You can check the mcubootutility at first, after it works, please let me know.

Then, you can create a new question post to @kerry zhou, I will take it.

My side has your ATXP032 chip  +RT1050 board(to the RT1060, I need to borrow the validation board to test, anyway, I have a way to test it on my side), I can help you to test it, just need you to create a new question post, then also share the link in this post. Thanks a lot for your cooperation and understanding.

 

Best Regards,

kerry

 

0 Kudos
2,746 Views
jackking
Senior Contributor I

@kerryzhou  I created *this* thread at your request from another post: https://community.nxp.com/t5/i-MX-RT/How-to-program-rt1170-evk-octal-flash-with-JLink/m-p/1662365/hi... 

Yes,of course, the flash works correctly when using MCUBootUtility, as well with J-Link versions before they switched to using a different flash driver method (maybe around J-Link 7.60?).  I have been stuck using J-Link version 7.50a because of this.

I have been using the Embedded Artists EVK and my own custom design for years now, and flash is erased, programmed and verified successfully every time.

This is the (successful) programming with J-Link 7.50a to show it does work:
ECOXIP_JLINK_750a.gif

2,717 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

   Thanks for your information!

  In your mentioned linker, that is RT1170, so now, you want to use RT1060 with adesto octal flash chip, right?

  Your testing board is Embedded Artists EVK  or your customer board?

   I have one Embedded Artists EVK  board which is RT1050 and a socket which can insert the different flash chip.

  Please help to check my understanding about your question:

1. use the older JLINK driver version, it works OK, eg, 7.50a.

   As from your video, seems your downloading works.

2. Please note, in your video, the .cfx flashdriver is not used for the JLINK, it is for the CMSIS DAP debugger.

   If you want to use the JLINK, you need to select the correct version.

  Whether the new JLINK driver can't work on your side?

  widndow->preferences

kerryzhou_0-1686710105520.png

Here select the JLINK driver, if you use the RT-UFL, you also need to select to the RT-UFL JLINK driver area. And in the debug configuration, device need to select the UFL flash device name, do you all do it?

3. What's your detail requirement? Use the directly new JLINK driver can't work right? And you want to use the RT-UFL as the JLINK flashdriver, but until now, you didn't make it works on the MIMXRT1060+Adesto octal flash, right?

Next time, if you want me to provide service for you in the new post, please in the original post @kerry zhou directly, otherwise, this case maybe won't enter my box, and it may still consume my working time, thanks a lot for your understanding.

Anyway, I will find time to help you do the testing, but it maybe delay, as a lot of customers in my testing now, please keep patient, thanks.

Best Regards,

kerry

 

 

 

 

 

 

0 Kudos
2,707 Views
jackking
Senior Contributor I

@kerryzhou  My detailed requirement is to use the latest J-Link versions to debug the IMXRT1062xxxxA with Adesto EcoXIP OctalSPI Flash (ATXP032) with MCUXpresso v11.7.1 (on Mac) using the Embedded Artists Development Kit (EVK)

I have done the following:

* Select the specific J-Link version (7.88e) in the MCUXpresso debug configuration. 

* Configure the J-Link launch to use the MIMXRT1062xxx6A alias

* Download the RT-UFL project and place the RT-UFL files into the J-Link directory

* Create and/or modify the JLinkDevices.xml to use the RT-UFL Loader.  I do not know the correct RT-UFL settings to use for Adesto EcoXIP Flash. I have tried many different settings.  This is what I am asking for in this post

When I launch the debug session, J-Link fails to erase or program the flash with the application, and then debug fails.

Here is a video of it *not* working with J-Link 7.88e.

ECOXIP_JLINK_788e.gif

 

 

0 Kudos
2,590 Views
jackking
Senior Contributor I

@kerryzhou  Does that video help illustrate what I am trying to do? 

Have you been able to test with your EVK and Adesto ATXP032 EcoXIP OctalSPI Flash?

 

0 Kudos
2,513 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

  So sorry for my later reply, really too many cases in the testing queue recently, I am totally overflow.

  What's the JLINK you are using? JLINK plus or others?

   You also can try the JFlash directly, if the Jflash or the JLINK commander can't work, it is related to the flashdriver.

   I get the information that the Adesto octal flash is EOL, so you still want to use that octal flash for the new product? If yes, I will test it on my MIMXRT1050 with adesto octal flash.

    Maybe need to debug the RT-UFL directly.

 

Best Regards,

Kerry

0 Kudos
2,496 Views
jackking
Senior Contributor I

I have tried with J-Link Base, J-Link Plus, J-Link Ultra+ and J-Trace Pro (Cortex-M).  All of them behave the same.


As in my original question...what are the correct settings for RT-UFL to use with Adesto EcoXIP OctalSPI Flash? There is no documentation on RT_UFL and how to set up correct settings for other parts.

Programming fails in J-Flash as well.

This is for an existing product, not a new product, so changing the Adesto Flash part is not an option.


Please test it on your Embedded Artists EVK.

 

 

0 Kudos
2,386 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

  Please let me know your ATXP032 boot pin configuration, I mean all BOOT_CFG configuration which is used to select the adesto ATXP032 chip on your side.

 

Best Regards,

Kerry

0 Kudos
2,376 Views
jackking
Senior Contributor I

@kerryzhou  The Embedded Artists iMXRT1062 module is configured to always boot from external Flash.  The BOOT_CFG pins are left as undriven outputs, there are no boot config switches on the EA EVK as there are on the NXP EVK.

 

There is an ISP enable switch on the EA EVK to force booting from USB OTG when needed.

 

0 Kudos
2,374 Views
jackking
Senior Contributor I
0 Kudos
2,360 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

   Thanks for your information.

   My board is from the adesto side, very old with RT1052, until now, I can't make it work even with the serialdownload mode to connect with blhost. This board also no CFG pin configuration. and I also lack the schematic.

    Anyway, I will try to find our internal validation board to test the RT1062+Adesto octal flash directly.

    About your EA board, can you make sure your octal flash already works in serial download mode with MCUBootutility? I need to make sure the hardware no issue at first.

 

Best Regards,

Kerry

0 Kudos
2,394 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @jackking ,

   Let's use the JLINK plus as the debugger.

  I am testing it today, will reply you later.

  Just from your IDE calling the RT-UFL, it's OK, anyway, let me test it at first.

Best Regards,

kerry

0 Kudos