Tiny Core Base > TCB Talk
Re: Tiny Core v17.0 upgrade issues
Stefann:
--- Quote from: Rich on March 28, 2026, 12:23:18 PM ---Hi Stefann
--- Quote from: Stefann on March 28, 2026, 08:13:41 AM --- ...
--- Code: ---tc@huis:/$ lsusb -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M <-------------------- Slow port
|__ Port 1: Dev 2, If 0, Class=(Defined at Interface level), Driver=usbfs, 1.5M <-- X10 Wireless Technology, Inc. ActiveHome (ACPI-compliant)
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M <-------------------- Slow port
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M <---------- Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter
|__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M <------- Future Technology Devices International, Ltd FT232 Serial (UART) IC
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M <------------------- Fast port
--- End code ---
...
--- End quote ---
I don't know if it's an issue, but your peripherals appear to be plugged
into slow speed (12 Mbits/sec) ports.
If I'm reading it correctly:
The X10 Wireless device is connecting at 1.5 Mbits/sec, which sounds fine.
The other 2 devices are connecting at 12 Mbits/sec, which may be taxing that slow speed bus.
The faster (480 Mbits/sec) port might be a better choice if it
provides external USB ports.
--- End quote ---
Well…it’s a low power low spec computer from 2008. 500MHz single core. So it’s definitely not fast.
There is not much choice on ports. There are only 3 on the outside and I’m using all 3.
The 480M port is NOT available on the outside. Could this be the compact flash drive?
The system does not have harddisk but a compact flash card as persistent at storage.
Speed however is not a big thing.
- the serial port reads my energy meter that spits out a data block of 500 bytes each second.
- the X10 interface controls the lights in the house. That’s blocks of about 20 bytes each time a light gets switched.
- the 1 wire is the only time critical thing. It is a constant stream of data. 1 wire protocol allows bit-length to be 75us so that is still only 13kHz. Keeping that thing at full speed is important. It currently takes 250ms to Do a “all sensor read” of the house. That should not get longer.
System still running since start yesterday afternoon.
Stefann:
For those interested,
manual for this 18yr old computer is still online (amazing!):
https://ftp.emacinc.com/LegacyProducts/EmbeddedServers/ebox-4300/Manual/ebox_4300_manual.pdf
I have version with 1G ram.
I have it currently with 8G compact flash as persistent storage.
It runs on a low power (1 watt) 500MHz 32bit single core Via Eden x86 based processor
I donot have the (optional) serial port
Rich:
Hi Stefann
--- Quote from: Stefann on March 29, 2026, 02:19:32 AM --- ... Speed however is not a big thing. ...
--- End quote ---
Agreed. I does not appear like any of those devices would tax the USB ports.
--- Quote --- ... - the serial port reads my energy meter that spits out a data block of 500 bytes each second. ...
--- End quote ---
You haven't mention the baud rate you are using and whether your
USB to RS-232 cable contains a transmit FIFO, so I decided to do a
little math.
Assuming:
8 data bits, 1 parity bit, 1 start bit, 2 stop bits (12 bits).
Baud rate of 9600 (~104 uSecs/bit).
Data bursts of 500 bytes.
12 bits * 0.000104 secs = 0.001248 secs
500 bytes * 0.001248 secs = 0.624 secs
This assumes zero gap time between transmitted bytes.
The RS-232 spec does not specify min/max gap times.
Rich:
Hi Stefann
Is the USB to RS-232 cable you are using listed here:
https://ftdichip.com/product-category/products/cables/usb-rs232-cable-series/
Stefann:
Hi,
its difficult to say as I bought the cable 17 years ago.
I just went through my notes.
I cannot find a literal order, but my notes indicate that I was intending to buy: "FTDI TTL-232R (5V)".
From the website you shared that is close to this one:
https://ftdichip.com/products/usb-rs232-we-5000-bt_5-0/
But my usb-connector is black, not transparant.
I can see I saved screenshots from "FTDI FT prog" that configures the cable. So it looks like I kind of have that one.
For the record: it's still running. About 24hrs now.
logging is coming in. But to be honest, not much interesting. Just crontabs getting fired.
It's nice that the logging is now on a separate network connected system. That also means that in case of a crash I can check the logging before starting the crashed system.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version