Hi Ashok Ra,
Thanks for your updated information.
Yes, you are using the wrong debugger firmware, please download the MIMXRT1015 to your board again.
You can find the related bootloader firmware from this link:
If your firmware is correct, you will detect :
If you use the external debugger, you still need to choose the correct MIMXRT1015 part number.
External JLINK need to remove J47-J50, this following is my JLINK commander detect result:
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Hi Kerry,
Now i removed the jumpers (J47,J48,J49,J50) not ( correction J61-J64). And Jlink is connected now.
So looks onboard debug chip is dead or did not working.. But still it detect as
Sad part is The hardware user-guide does not talk about the Jumpers J47 to J50. It shoud be updated.
In editor , what should be the launch configuration looks like for jlink? i choosed device as "Cortex-M7" instead of MIMXRT1011DAE5A.
Now its not entering into main. Please share the proper lunch configuration
Thanks
Ashok R
HiAshok Ra,
Are you sure you are using the MIMXRT1010-EVK board?
If yes, you still need to disconnect J61-J64, then connect your external JLINK SWD interface to the j55.
I have tested it on my side, it works OK.
The JLINK driver please use the newest one:
https://www.segger.com/downloads/jlink/JLink_Windows.exe
Any updated information, please kindly let me know.
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Hi Ashok Ra
Please let me know your board version, you can find it from the back side in the board, just like my board picture:
SCH-45852 REVC.
Please give me your board version picture.
Any updated information, please kindly let me know.
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Hi Ashok Ra,
Please double check your board name, is it MIMXRT1010-EVK or MIMXRT1015-EVK?
Because I find my MIMXRT1015-EVK schematic version is SCH-38830 REVB, it seems you have chosen the wrong RT chip device.
Please double check your board.
Any updated information, please kindly let me know.
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Hi Ashok Ra,
Thanks for your updated information.
Yes, you are using the wrong debugger firmware, please download the MIMXRT1015 to your board again.
You can find the related bootloader firmware from this link:
If your firmware is correct, you will detect :
If you use the external debugger, you still need to choose the correct MIMXRT1015 part number.
External JLINK need to remove J47-J50, this following is my JLINK commander detect result:
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Hi Ashok Ra
RT1010 is the series, you can choose the RT1011.
As you know, the MIMXRT1010-EVK is using the MIMXRT1011DAE5A chip.
Please try it on your side in the serial download mode at first.
If you still have questions about it, please kindly let me know.
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Hi Ashok Ra,
Please check the following configuration, do you use the adesto_AT25SFxxxA flash?
After you modify the SW8 -> OFF OFF OFF ON, please also press the reset button, then try to connect your board.
Please also check whether your COM8 is really your on board virtual COM port.
BTW, I am will on our Chinese Spring festival from tomorrow, and will back on Feb. 3.
Then, if you have any updated information, I will reply you after I am back to works.
If you are in hurry, you also can create the new case, then our colleague will help you.
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Sorry to say this! Im using same Boot configuration and it does not works.. when i click the Flash button .. The LED blinks fast and i could see yellow indication in the Tool, then suddenly RED led stops (board) and indication changed into red color. gets error message
Hi Ashok Ra,
Sorry for my later reply because of chinese Spring Festival.
Do you have the external JLINK, can use the JLINK commander window to connect your own new board, and can you find the ARM core? Let's check the hardware works OK or not at first, just without the external flash.
Any updated information, please kindly let me know.
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Hi Kerry Zhou,
I tried with Jlink Debugger , connected with Port J55 on board.
Below the response i got. Did not connecting ..
SEGGER J-Link GDB Server V6.54c Command Line Version
JLinkARM.dll V6.54c (DLL compiled Nov 7 2019 17:01:02)
Command line: -select USB -device Cortex-M7 -endian little -if SWD -speed auto -noir -LocalhostOnly
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: localhost only
Generate logfile: off
Verify download: off
Init regs on start: off
Silent mode: off
Single run mode: off
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: Cortex-M7
Target interface: SWD
Target interface speed: auto
Target endian: littleConnecting to J-Link...
J-Link is connected.
Firmware: J-Link Lite-Cortex-M V9 compiled May 17 2019 09:50:01
Hardware: V9.00
S/N: 519004084
Feature(s): GDB
Checking target voltage...
Target voltage: 3.28 V
Listening on TCP/IP port 2331
Connecting to target...ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
Shutting down...
Hi Ashok Ra,
If you are using the external JLINK debugger, you also need to disconnect the on board debugger: J61-J64 disconnect.
Then try it again, can you find the ARM core? If you still can't find the ARM core, it means your hardware have problems. Please also make sure your board is powered on after you use the external debugger.
Any updated information, please kindly let me know.
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------
Hi Ashok Ra ,
Which IDE you are using?
Please modify the SW8 to 1:off, 2:off:3:off, 4:on.
Then use the MCUBootUtility tool:
https://github.com/JayHeng/NXP-MCUBootUtility/archive/v2.2.0.zip
the related user manual is:
https://github.com/JayHeng/NXP-MCUBootUtility
Connect your board through the UART com port, then erase the external flash.
After the flash is erased, then you can try the IDE connection again.
Please try it.
If you still have questions about it, please kindly let me know.
Have a great day,
Kerry
-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------