How to activate ttyUSB0?

[Roland]

How can I activate 'ttyUSB0' in PPC Linux distros? In Ubuntu18 it is enough to plug in an USB device using that (e.g. a USB-SER adapter), the ttyUSB0 appears automatically into /dev. But that does not happen with any of the PPC distros (MintPPC, Fienix, Ubuntu16) I tested.

[xeno74]

How can I activate 'ttyUSB0' in PPC Linux distros? In Ubuntu18 it is enough to plug in an USB device using that (e.g. a USB-SER adapter), the ttyUSB0 appears automatically into /dev. But that does not happen with any of the PPC distros (MintPPC, Fienix, Ubuntu16) I tested.

Please add console=ttyS0,115200 to the boot arguments.

Further information: X5000 via null modem RS-232 serial cable

[Roland]

Please add console=ttyS0,115200 to the boot arguments.

I added "console=ttyS0,38400", but that did not help...

Further information: X5000 via null modem RS-232 serial cable

It is _not_ the RS-232 port I want to use but read the MCU debug output (connector on motherboard) via an USB port. The baudrate for it is 38400.

With Ubuntu18 (on a portable), I can access the MCU simply with "sudo screen /dev/ttyUSB0 38400" in a terminal, nothing else is needed.

[xeno74]

It is _not_ the RS-232 port I want to use but read the MCU debug output (connector on motherboard) via an USB port. The baudrate for it is 38400.

With Ubuntu18 (on a portable), I can access the MCU simply with "sudo screen /dev/ttyUSB0 38400" in a terminal, nothing else is needed.

I am sorry, I don't have any experiences with the MCU supervisor interface.

I only know that it provides voltage and temperature monitoring for the CPU.

Setup:

• 38400 Baud
• 8 bit data
• No Parity
• 1 Stop bit
• No Flow Control

[Roland]

I am sorry, I don't have any experiences with the MCU supervisor interface.

I only know that it provides voltage and temperature monitoring for the CPU.

All that is probably meaningless what comes to this issue... The MCU is just one possible target for the adapter cable. I think he problem is that OS does not communicate with the adapter (and the chip used in it) properly. Is there missing a driver from the kernel?!

The product (ADA954 3.3V TTL USB-serial adapter cable) is this:
https://www.adafruit.com/product/954htt ... roduct/954

"lsusb" tells that it has the PL2303 chip:

Bus 002 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port

[xeno74]

Hi Roland,

Kernel 5.10.208 config:

Code: Select all

...

CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_CP210X is not set

...

Kernel 6.9-rc6 config:

Code: Select all

...

CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_CP210X is not set

...

Have you already tested it with installed kernel modules? (PL2303)

If yes, maybe the CP210X kernel module is missing.

Cheers,
Christian

[Roland]

Have you already tested it with installed kernel modules? (PL2303)

No, I did not remember there were also those modules which are not compiled in the kernel...

I copied the whole bunch to the lib/module, and now it's working! Thank you for the tip .

But is better to have on disk only the modules you know to need? Are they eating memory when the machine is booted, or are they loaded only if some device try to call them?

Code: Select all

>> help

 command                    description
 =======                    ======================================================
 help                       Print this help list
 id                         Identify (report h/w and f/w revisions)
 id date                    Identify (report h/w and f/w revisions build date)
 p                          Power up all supplies
 s                          Shut down all supplies
 q                          Toggle printing
 v                          Print voltages and temperatures
OK
>> id

Cyrus Plus
MCU Firmware Version 2.5
Hardware Version 2.2
CPLD Version 1.0
Dual Ethernet devices fitted.
Release Build
OK
>> v

-       vcc_cpld: 3.32
-  vdd_3v3_xorro: 3.31
-    vdd_1v0_idt: 1.01
-  vdd_1v0_xorro: 1.00
-        vdd_3v3: 3.35
-        vdd_2v5: 2.50
-    vdd_1v2_eth: 1.20
-         vdd_pl: 1.03
-         vdd_ca: 1.20
-         vdd_cb: 1.19
-    vdd_ddr3_io: 1.49
-    vdd_xvdd_fl: 1.82


-       pcb_temp: 41 deg C  
-       cpu_temp: 59 deg C  
-       pex_temp: 59 deg C  


-        FAN RPM: 0

OK
>>

[xeno74]

Are they eating memory when the machine is booted, or are they loaded only if some device try to call them?

They are only loaded once the devices have been recognized.