-
Notifications
You must be signed in to change notification settings - Fork 80
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
tilib on OpenBSD #97
Comments
On Mon, Jun 29, 2020 at 07:58:08AM -0700, Hose wie Jacke wrote:
However, the connection via `tilib` fails:
$ mspdebug tilib
...
Using new (SLAC460L+) API
MSP430_GetNumberOfUsbIfs
No unused FET found.
Have you tried using -d to specify the device explicitly? I can't
remember how the auto-detection in the library works, but it's possible
that it's Linux-specific.
…--
Daniel Beer <dlbeer@gmail.com> http://dlbeer.co.nz/
PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B
|
Have you tried using -d to specify the device explicitly?
Yes, but I might have been specifying the wrong device.
There are no `/dev/ttyACM*` on OpenBSD, so I tried
- `/dev/ttyU?`
- `/dev/cuaU?`
The results are all the same:
Using new (SLAC460L+) API
MSP430_Initialize: /dev/ttyU0
tilib: MSP430_Initialize: Could not find MSP-FET430UIF on specified COM
port (error = 57)
tilib: device initialization failed
If I understand the man pages correctly, OpenBSD supports ACM through
umodem/ucom which are presented as `/dev/cuaU?`:
- https://man.openbsd.org/umodem.4
- https://man.openbsd.org/ucom.4
However, the "has no CM over data" claim in `dmesg` makes me suspicious:
umodem0 at uhub1 port 2 configuration 1 interface 0
"Texas Instruments MSP Tools Driver" rev 2.00/2.00 addr 8
umodem0: data interface 1, has no CM over data, has no break
umodem0: status change notification available
ucom0 at umodem0
|
On Tue, Jun 30, 2020 at 12:57:27AM -0700, Hose wie Jacke wrote:
Yes, but I might have been specifying the wrong device.
There are no `/dev/ttyACM*` on OpenBSD, so I tried
- `/dev/ttyU?`
- `/dev/cuaU?`
The results are all the same:
Using new (SLAC460L+) API
MSP430_Initialize: /dev/ttyU0
tilib: MSP430_Initialize: Could not find MSP-FET430UIF on specified COM
port (error = 57)
tilib: device initialization failed
If I understand the man pages correctly, OpenBSD supports ACM through
umodem/ucom which are presented as `/dev/cuaU?`:
- https://man.openbsd.org/umodem.4
- https://man.openbsd.org/ucom.4
However, the "has no CM over data" claim in `dmesg` makes me suspicious:
umodem0 at uhub1 port 2 configuration 1 interface 0
"Texas Instruments MSP Tools Driver" rev 2.00/2.00 addr 8
umodem0: data interface 1, has no CM over data, has no break
umodem0: status change notification available
ucom0 at umodem0
Unfortunately the diagnostics from the library aren't too descriptive.
One thing I would try is just to run as root, in case you don't have
permission for the device. Failing that, maybe try running with strace
to see what it's actually trying to do.
…--
Daniel Beer <dlbeer@gmail.com> http://dlbeer.co.nz/
PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B
|
Hi. I could get a bit further on porting It also fails at the Here's the port: https://github.com/phillbush/openbsd-ports/tree/master/devel/libmsp430 However, libmsp430 fails at the communication itself (error 35), because of an unexpected byte read from the serial port at the beginning of the communication. I explain the error better here: osresearch/MSPDebugStack#1 Thank you, |
I fixed the port. |
This is plain awesome 🥳 |
Hello all,
I'd like to use an FRAM launchpad on OpenBSD. AFAIK
tilib
is an appropriate driver for this. However, I couldn't make it work. Does anybody know what the problem could be?mspdebug
is compiled from #e65bc69:libmsp430.so
is compiled from Rev 3.15.1.001:The Launchpad is attached:
and recognized by
mspdebug
:However, the connection via
tilib
fails:A connection via
ezfet
fails, too:Is the anything else I could try?
PS: @dlbeer, thanks a lot for
mspdebug
!(
rf2500
works great on OpenBSD with the old Launchpad).The text was updated successfully, but these errors were encountered: