MicroPython Forum (Archive)

I'm able to get the REPL going using screen /dev/tty.usbmodem1412, but screen is really clunky.

I've installed shell but can't get it talking to the same device.

rshell

connect serial /dev/tty.usbmodem1412

Connecting to /dev/tty.usmodem1412 ...
failed to access /dev/tty.usmodem1412

Would someone help?

What's the output of: show?

I don't use OSX much. Is there /dev/cu.usbmodem1412 as well?

On my Mac Mini, the pyboad shows as /dev/cu.usbmodem99999 (where 99999 is some number).

dhylands wrote:What's the output of:

Code: Select all

ls -l /dev/tty.usbmodem1412

show?

I don't use OSX much. Is there /dev/cu.usbmodem1412 as well?

On my Mac Mini, the pyboad shows as /dev/cu.usbmodem99999 (where 99999 is some number).

Is there /dev/cu.usbmodem1412 as well?

Yes. What's the difference between the two?
Should I always use the cu device with MicroPython?


Thanks

I didn't know the answer, but found out that this is what makes the difference:
http://stackoverflow.com/questions/8632 ... and-dev-cu

For rshell/pyboard, you definitely want to use /dev/cu.usbmodem*

I don't know what the pyboard USB stack does with DCD. It would probably be possible to make it set DCD in such a way that it would also work, but I'm pretty sure that the code doesn't currently do anything to manage that.

dhylands wrote:I didn't know the answer, but found out that this is what makes the difference:
http://stackoverflow.com/questions/8632 ... and-dev-cu

For rshell/pyboard, you definitely want to use /dev/cu.usbmodem*

I don't know what the pyboard USB stack does with DCD. It would probably be possible to make it set DCD in such a way that it would also work, but I'm pretty sure that the code doesn't currently do anything to manage that.

Very interesting. I've added this to my notes.

Thanks Dave