Monday, April 23rd 2018, 10:54pm UTC+2

You are not logged in.

  • Login
  • Register

Eli Hughes

Beginner

Date of registration: Mar 19th 2018

Posts: 7

1

Monday, March 19th 2018, 4:36pm

[SOLVED] Embedded Studio 3.34 + Ozone 2.56e + i.MXRT1052 EVK Issue

Hello:

I am having a debug issue with the NXP i.MX RT1052EVK with Ozone.

Setup:
---------------------------
Embedded Studio 3.34
Ozone 2.56e

i.MXRT1052 EVK

Using External J-LINK debugger on J21



The board is jumpered to boot from HyperFlash (although I am only testing RAM only projects).




What is Working:
----------------------------------------


I was abel to create the sample Hello world project in Embedded Studio after installing the 1-52 support package. It could compile and download fine. I could single step, etc withing embedded studio. Hellow World messages showedup in the debug terminal.




Problem:
-------------------------------------------


I prefer to use the ozone debugger. From the "Debug" menu I selected "Debug With Ozone". Ozone startup successfully. When to tried to download, ozone froze here. (Screenshot attached).




I eventually get "failed to read target status. Abort Debug Session".




I think this may be an ozone issue as I can debug in embedded studio.


Also, I have also debugged via NXP's MCUXpresso tool. I would like to get Ozone up an running as it has been the best debug tool











Eli Hughes has attached the following image:
  • ozone.png

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 949

2

Tuesday, March 20th 2018, 5:28pm

Hello,

Thank you for your inquiry.
For this particular device to work with Ozone you need to uncomment the functions TargetReset() and AfterTargetDownload() in the .jdebug file.
To do this simply save the Ozone project and edit the .jedebug file.

Does this work for you?

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


Eli Hughes

Beginner

Date of registration: Mar 19th 2018

Posts: 7

3

Tuesday, March 20th 2018, 7:05pm

Hello Nino:

Thank you for the response.

I followed your instructions:

1.) Saved the .jdebug file
2.) Uncommented the functions TargetReset() and AfterTargetDownload()

It seems to get a little further in the process but still hangs. I have attached my .jdebug file that was created by Embedded Studio launching Ozone as well as a capture of the console when the freeze occurs.

Note: I had to rename the .jdebug to .jdebug.txt to allow upload to the forum.
Eli Hughes has attached the following image:
  • Ozone2.png
Eli Hughes has attached the following file:

This post has been edited 1 times, last edit by "Eli Hughes" (Mar 20th 2018, 7:06pm)


Eli Hughes

Beginner

Date of registration: Mar 19th 2018

Posts: 7

4

Tuesday, March 27th 2018, 7:35pm

Just a bump on this.

I recently grabbed Jlink6.31d (beta). Ozone now appears to work. My test application can single step, etc.

I did notice that there a couple i.MX RT1052 options.

in particular there is a

MIMXRT1052xxxxA


and a

MIMXRT1052xxxxB



What is the difference?

I looked in the JLinkdevices.xml

Source code

1
                                                                       




"A" and "B" appear to be identical as they both use a hyper flash driver.


I though one might be for QSPI flash programming but "NXP_iMXRT105x_QSPI.elf" is never specified. (I found NXP_iMXRT105x_QSPI.elf in the JLink_V631d\Devices\NXP\iMXRT105x folder).


If I do want QSPI, can I simply edit the .XML file to use the correct driver?

Thanks!

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 949

5

Wednesday, March 28th 2018, 9:20am

Hello,

Great to hear that Ozone works now for you.
A and B should be 99% identical. The difference between them should be described in the target device reference manual.
How to switch between Hyperflash and QSPI is described here: https://wiki.segger.com/IMXRT105x

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


Eli Hughes

Beginner

Date of registration: Mar 19th 2018

Posts: 7

6

Wednesday, March 28th 2018, 5:23pm

Thanks for the Wiki link. I was unware of it.

You can mark this thread as solved.