config tools with MCIMX93-EVK

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

config tools with MCIMX93-EVK

Jump to solution
1,823 Views
hermann_ruckerb
Contributor III

Hello, 

sorry for this stupid question ... 

i have used the MCU config tools with the MCIMX93-EVK evaluation board in the past already. I stopped for a while and not i wanted to restart my work and I get it not to work!

I guess the main issue is mentioned in the log file:

ERROR memtool.comm.sdps_comm Invalid USB HID device selection 0 from list [] !
ERROR memtool.common.base_test Load application ended with exception: 'NoneType' object has no attribute 'open'

DIP switches are set to serial download (not changed from last working trial)

i tried all 4 COM ports even thinking to know that it is the third one.

Original test was done with v14, and after this was not working i checked v15 and started from Scratch.. same result. 

 

I have not found any way to check if the board is really connected and the serial download is somehow working (but the LEDs that i expect to indicate serial traffic does not show anything).

i think to remember there should be a hid device in the device manager.. but I am not sure how to check wich is my EVK. 

Any help is highly appreciated!

Hermann 

 

 

0 Kudos
Reply
1 Solution
1,767 Views
Alejandro_Salas
NXP TechSupport
NXP TechSupport

Hello @hermann_ruckerb 

 

The problem is you are not connecting the USB cable from your host PC to USB1 of board.

I have the same log as you when I have not connected that USB cable:

Alejandro_Salas_0-1707493293735.png

but connecting it, you should be able to run the test without any problems.

 

My steps:

1. Set the board in Download serial mode

2. Connect the Debug cable to my PC (J1401)

3. Connect the USB1-C of board to my PC too.

4. Run the test in correspondent COM port, 34 in case:

Alejandro_Salas_1-1707493472076.png

And run the test:

Alejandro_Salas_2-1707493558435.png

 

I hope this can help to you.

 

Best regards!

 

Salas.

 

View solution in original post

7 Replies
1,776 Views
hermann_ruckerb
Contributor III

Hello Sales, 

Thanks for taking care! 

what I want to do: Run the DDR tools (memory training, Stress test, .. ) on MCIMX93-EVK.

What I do:

In the past i did what i describe below with v14 and this was working. After 3 weeks i re-tried and it was not working with the same result as below (not sure if i made anything different). So i tried the following (in order to use config tools v15):

 

Install Config Tools for i.MX v15 on Host PC (windows 10 version)
Start Config tools and create a new setup by selecting MCIMX93-EVK and core A55.
Enabling DDR tools.
(for new tests reload old configuration .mex file)

Switch 1301 is set to 0011 for serial download mode
Connect Power to MCIMX93-EVK.
Connect Host PC USB to MCIMX93-EVK USB C Debug (JP1401)
Check on Host PC to get 4 serial ports (COM22-25) and verify all are set to 115200/8/None/1/None
Power on MCIMX93-EVK with switch
Check USB Debug RX/TX status Leds: See on one some blinking to indicate traffic, this stops after a while.
Go to DDR Test in config tools and select expected third com port for A55 (Com24)
Select e. g. Operational tests run Write-Read_compare
Get the message "Queued" in the Result colum (blue flashing).
After some time get a red "Failed" in the result column.
Fail reason colum states "AttributeError "None Type" object... "
check the logs (see attached) and see error messages e. g. 
ERROR memtool.comm.sdps_comm Invalid USB HID device selection 0 from list [] !
ERROR memtool.common.base_test Load application ended with exception: 'NoneType' object has no attribute 'open'
Select other 3 com ports one by one and try to run test again: same result for all 4 Com ports. 

One more information:

the boot from SD card is successful and i can use a terminal when booting from SD card:
Known Change since last use: the DRAMs was changed, because this is what I want to check on the eval board.
As the boot from SD card works with the SD card works the change of the DRAM is expected to be sucessful.

 

Thanks for any feedback.

Hermann

 

 

 

0 Kudos
Reply
1,768 Views
Alejandro_Salas
NXP TechSupport
NXP TechSupport

Hello @hermann_ruckerb 

 

The problem is you are not connecting the USB cable from your host PC to USB1 of board.

I have the same log as you when I have not connected that USB cable:

Alejandro_Salas_0-1707493293735.png

but connecting it, you should be able to run the test without any problems.

 

My steps:

1. Set the board in Download serial mode

2. Connect the Debug cable to my PC (J1401)

3. Connect the USB1-C of board to my PC too.

4. Run the test in correspondent COM port, 34 in case:

Alejandro_Salas_1-1707493472076.png

And run the test:

Alejandro_Salas_2-1707493558435.png

 

I hope this can help to you.

 

Best regards!

 

Salas.

 

377 Views
UzairKiani
Contributor I
Hi, I am having same problem. I have custom device, connected with directly to PC. The device is serial download mode, but getting same error. Could you please look into it.
0 Kudos
Reply
1,763 Views
hermann_ruckerb
Contributor III

You made my day (and my weekend)! !!!!

Thanks a lot.

three weeks seems to long for me, to remember, that I had to use 2 USB connections! And even with re-reading the Guides i missed this information.

with the second USB cable it works!

Thanks a lot!!!

 

Hermann 

1,734 Views
hermann_ruckerb
Contributor III

Hello ,

sorry me again..

Functional and vTSA tests are working fine now.. 

but i run into trouble with the Stressing.

first of all i would like to run it forever and when i stop i would like to get a result.
But for the timeout i can only set a high number (1999999999 seems the max).
this seems large enough, still i would prefer to disable any timeout. 

If i run forever i can only select "cancel" and in this case i get a skipped as result, but not a pass or fail until then. How do i get a Pass/Fail when i stop e. g. after 24h?

last but not least: i get an error message that i do not understand:

ERROR memtool.common.base_test Load application ended with exception: SPSDK: Invalid size of written bytes has been detected: -1 != 1021

 

Any ideas what this means ? 

 

Hermann 

 

 

0 Kudos
Reply
1,798 Views
Alejandro_Salas
NXP TechSupport
NXP TechSupport

Hello @hermann_ruckerb 

 

Could you please provide to me a step by step instructions to replicate the issue?

And what do you want to do exactly?

 

Best regards!

 

Salas.

0 Kudos
Reply
1,772 Views
hermann_ruckerb
Contributor III
sorry, seems my answer was to the original post.. please take a look there to see answers to your questions.
0 Kudos
Reply