The Adapter ID of XK-EVK-XU316 is XXXXXXXX

[denny10079]

Hi,

I got XK-EVK-XU316 today.
I connected the USB port & DEBIG port on board to PC and type "xrun -l", I get the Adapter ID is "XXXXXXXX"
I think there may something wrong, but I think my environment is fine, I have programed the XU208 with XTAG4 before. https://www.xcore.com/viewtopic.php?t=9087
================2025/08/13=====================
I attached the video of XK-EVK-XU316, hope it can help for debug.
Video for XK-EVK-XU316

[markp]

Have/can you tried a different XTAG on the same machine/PC?

Which version of the XTC Tools are you using?

[denny10079]

yes, I have run XTAG4 and download the program to XU208 on the same PC.
now, I use the XTAG4 which build-in on XK-EVK-XU316.
The version of XTC tool is 15.3.1.

[Joe]

Hi,

This is odd.

Can you select the XTAG-4 in device manager and look at the Device instance path property under the details tab and post what it says?

Thanks,
Joe

instance.PNG

[denny10079]

yes, I can see the information below.

upload images

[denny10079]

I try the command "xrun", it's work.
I think I can run the program well, but not flash the program.


I'm not sure if my task is wrong?

[markp]

Can you try xflash from the command line first? It should work successfully in the same way as the "xrun" command line invocation has worked.

In your task "args", remove the "--id <id>" part completely (leaving in the following text; the path to the example.xe). If xflash works on the command line it should work through the task mechanism with this change.

[Joe]

Hi,

You should be able to use the board as normal but the XXXXXX issue is that windows isn't happy with the serial number on the XTAG4 on the board. It would be a help if you could try the same test on a linux or mac system to see what they say. If it displays the same behaviour on linux/mac then it's probably a board manufacturing issue and you should return it for a replacement.

Out of interest have you modified the board at all? From your image I see what might be a different flash IC on the board?

Cheers,
Joe

[denny10079]

Can you try xflash from the command line first? It should work successfully in the same way as the "xrun" command line invocation has worked.

In your task "args", remove the "--id <id>" part completely (leaving in the following text; the path to the example.xe). If xflash works on the command line it should work through the task mechanism with this change.

thanks, while I tpye the command "xflash" on command line, it works successfully.

[denny10079]

Hi,

You should be able to use the board as normal but the XXXXXX issue is that windows isn't happy with the serial number on the XTAG4 on the board. It would be a help if you could try the same test on a linux or mac system to see what they say. If it displays the same behaviour on linux/mac then it's probably a board manufacturing issue and you should return it for a replacement.

Out of interest have you modified the board at all? From your image I see what might be a different flash IC on the board?

Cheers,
Joe

thanks, I don't have the machine for linux or mac system. I think I should argue with Microsoft... .
I have never modify the board, can you please point out the different you think?