Hi!

> Shouldn't it be sudo instead of sesu?

You're right. That was a typo when writing the email.

Well, I was able to connect now.

> Whats the error message thats printed out? I've never got cu working,

It said "Line busy" ...?

There's a hint somewhere in the Wiki which suggested to chown /dev/ttyACM0 (once it's there) to uucp:uucp. Maybe that does the trick.

> What version of u-boot are you running?

How can I find out?

Regards,
Torsten


andy selby schrieb:
I try

sesu cu -l /dev/ttyACM0


Shouldn't it be sudo instead of sesu?


but I don't have that device node at all on my system.


Whats the error message thats printed out? I've never got cu working,
I've always used
screen /dev/ttyACM0
What version of u-boot are you running?

Reply via email to