Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Probe not detected by MCUXpresso #27

Open
allexoll opened this issue Sep 7, 2021 · 2 comments
Open

Probe not detected by MCUXpresso #27

allexoll opened this issue Sep 7, 2021 · 2 comments

Comments

@allexoll
Copy link

allexoll commented Sep 7, 2021

Openning this issue since we were talking about it on matrix.

hs-probe not detected by MCUXpresso

Issue: version 0.1.0, turbo, not detected on either Windows or macOs with MCUXpresso v11.4.0.

There is a probetable.csv that contains differents VID:PID

Screenshot 2021-09-07 at 15 47 11

that table was last documented in 2016: Auto-detect custom CMSIS-DAP probe:


 
VID     PID     Packet Size Has SWD  Has JTAG Has SWV Has ETM Descriptor   Usage Page Interface
------- ------- ----------- -------  -------- ------- ------- ----------   ---------- ---------
0x1FC9, 0x0090, 1024,       1,       1,       0,      0,      "CMSIS-DAP", 0xFF00,    0
 
 
VID:         Vendor ID
PID:         Product ID
Packet Size: USB packet size. Most probes use 64 byte HID packets. The Keil (non-bridge) firmware
             uses a 1024 byte packet. The NXP bridge and non-bridge CMSIS-DAP probes also use a
             1024 byte packet.
Has SWD:     Probe supports SWD protocol.
Has JTAG:    Probe supports JTAG protocol.
Has SWV:     Probe supports Serial Wire Viewer (NXP proprietary)
Has ETM:     Probe supports ETM (NXP proprietary)
Descriptor:  Text string (or partial text string) used to match against the probe product string.
             A non-null descriptor string is used for bridge probes to inform the server it must
             also match the debug connection on Usage Page or Interface number, depending on host.
             If used, both must be valid.
Usage Page:  Usage page, or 0 (zero) if don�t care.
Interface:   Interface number, or -1 if don�t care. See Descriptor.

I have tried to add the VID:PID of probe-rs, redlink sees the probe but there's an issue at some point:

[Started server]
[Connected on port 3025]
DEVICE ATTACH 1209: 4853 14200000
IOCreatePlugInInterfaceForService Error: E00002BE
IOCreatePlugInInterfaceForService Error: E00002BE
IOCreatePlugInInterfaceForService Error: E00002BE
redlink> ProbeList
Error: No probes found

related topics on NXP's forum:

Notes:

  • I think LPCLink debuggers that are on devkits are board-locked, so there might be a challenge/response included with those VID:PID
  • the hs-probe is seen with cargo flash --list-probes, and so is the LPCLink on the devkit i have.
@allexoll
Copy link
Author

allexoll commented Sep 7, 2021

IOCreatePlugInInterfaceForService Error: E00002B seems to not be related to to MCUXpresso, because it also happens with lsusb on macos:

 lsusb -s 020:006                                                                                         16:13:26
2021-09-07 16:14:02.176 system_profiler[84104:7052914] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
2021-09-07 16:14:02.176 system_profiler[84104:7052914] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
2021-09-07 16:14:02.177 system_profiler[84104:7052914] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
Bus 020 Device 006: ID 1209:4853 1209 HS-Probe with CMSIS-DAP Support  Serial: 13000f001650563641333620

that happens if the probe is connected or not, i'll try after a reboot too.

@allexoll
Copy link
Author

allexoll commented Sep 8, 2021

found how to have MCUXpresso list hs-probe, by adding

0x1209, 0x4853, 64, 1, 1, 0, 0, "", 0x0000, -1, -1

to probetable.csv (at least in MCUXpresso 11.4.0)

have not tested debugging yet, but its progress. I think we might need to include this information somewhere at some point, i'm unsure if other IDE have similar limitations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant