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

[H74x/H75x and G0]: Probing fails only on raspberry pi 3B+ #1324

Closed
5 tasks done
OSHW-Rico opened this issue Aug 10, 2023 · 9 comments · Fixed by #1052
Closed
5 tasks done

[H74x/H75x and G0]: Probing fails only on raspberry pi 3B+ #1324

OSHW-Rico opened this issue Aug 10, 2023 · 9 comments · Fixed by #1052

Comments

@OSHW-Rico
Copy link

OSHW-Rico commented Aug 10, 2023

  • Programmer/board type: [V2] (e.g STLINK /V1, /V2, /V2-onboard, /V2-clone, /V3)
  • Operating system an version: [Raspian] (e.g Linux, Windows)
  • stlink tools version and/or git commit hash: [1.7.0] (e.g v1.6.1/git-d0416149)
  • stlink commandline tool name: [st-info] (e.g st-info, st-flash, st-trace, st-util)
  • Target chip (and board, if applicable): [H7 and G0] (e.g STM32F103C8T6 (NUCLEO-F103RB))

When st-info --probe from the raspberry pi with Raspian Bullseye:


Found 1 stlink programmers
 serial:     543f6906783f565333341167
 hla-serial: "\x54\x3f\x69\x06\x78\x3f\x56\x53\x33\x34\x11\x67"
 flash:      0 (pagesize: 0)
 sram:       0
 chipid:     0x0000
 descr:      unknown device

When connecting to an amd64 Laptop Ubuntu:

  version:    V2J41S7
  serial:     54FF69067880565333341167
  flash:      2097152 (pagesize: 131072)
  sram:       131072
  chipid:     0x0450
  descr:      H74x/H75x

I tried with a V3, same thing.
Any ideas?

@Nightwalker-87
Copy link
Member

The output shows that the version of the toolset can not be the same. The lower output is correct.

@OSHW-Rico
Copy link
Author

What do you mean by toolset?

It's the same thing hardwire wise, took it out from one USB port to the other.

Software wise, it happens with a fresh compiled master branch and the default version from the package manager. (Don't remember the version for that, but I can check if it is important)

@Nightwalker-87
Copy link
Member

Nightwalker-87 commented Aug 10, 2023

... the stlink tools, this toolset. The versions from the package managers are mostly outdated.
You should try to use the latest self-compiled develop-branch. The master branch is quite old and has several bugs, which have been resolved since then.

@OSHW-Rico
Copy link
Author

I will check again tomorrow. Should I compile and test with the master branch or the distro version?

Anything else I can collect if the error persists?

@Nightwalker-87
Copy link
Member

I've just edited the previous reply.

@OSHW-Rico
Copy link
Author

Okay, thank you.

I tried development at first but encountered some error. I will try again and report back tomorrow.

@OSHW-Rico
Copy link
Author

So with the compiled development-branch it does work on amd64. Had no chance yet to try it with the raspberry, I will close it for now, since I expect it to work on the raspberry aswell.

Thanks for helping out.

@Nightwalker-87
Copy link
Member

Thanks for the feedback. 👍 I'll mark this as resolved, but leave the ticket open to have it closed by automation.
In this way we can match the resolving commit or PR to have our changelog updated respectively.

@Nightwalker-87
Copy link
Member

Fixed in #1052 and thus in Release 1.7.0.

@Nightwalker-87 Nightwalker-87 modified the milestones: v1.8.0, v1.7.0 Sep 2, 2023
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Sep 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.