Installation Aos on EBOX-2300

[BohdanT]

eBox-2300 is a revolutionary device designed for application with limited space and temperature concern.
http://www.embeddedpc.net/eBox4300/tabid/110/Default.aspx

I'm try boot from USB-CDROM, and get next:

Aos 30.05.2008 (Revision 1234)
Single-processor
Kernel: Initialized and started.
{P cpuid= 0, pid= -1 PCI: Bus interface initialized.}
AosATADisks: Force PIO mode for ATAPI devices
AosATADisks: Scanning PCI bus for IDE & SATA class devices ...
AosATADisks: Found PCI device on bus 0, device 0, function 1
AosATADisks: Adding controller 01F0, 03F0, FF00, IRQ: 14: IDE0..1, Bus-master enabled
AosATADisks: Adding controller 0170, 0370, FF08, IRQ: 15: IDE2..3, Bus-master enabledAosATADisks: Could not select device
AosATADisks: Could not select device

IDE0: 3823MB, LBA, ATA/ATAPI-4, Ultra DMA 2, TRANSCEND, ver 4.0
AosDiskFS: Index not found on RAM0
AosDiskFS: Scanning RAM0... marking     0 files
AosDiskFS: 31992K of 32000K available on RAM0
AosConsole: Mount failed on BootVol2
{P cpuid= 0, pid= -1 AosDisplayLinear.Obx not found}
{P cpuid= 0, pid= -1 AosKeyboard.Obx not found}
{P cpuid= 0, pid= -1 AosDriverDatabase.Obx not found}
{P cpuid= 0, pid= -1 WindowManager.Obx not found}
{P cpuid= 0, pid= -1 AosLoopback.Obx not found}
{P cpuid= 0, pid= -1 Autostart.Obx not found}
{P cpuid= 0, pid= -1 AosInitNet.Obx not found}

if booting from USB Flash:

Aos 30.05.2008 (Revision 1234)
Single-processor
Kernel: Initialized and started.
{P cpuid= 0, pid= -1 AosUsb: USB driver loaded.}
AosUsb: Driver UsbHub (USB Hub Driver) has been added.
{P cpuid= 0, pid= -1 PCI: Bus interface initialized.}
{P cpuid= 0, pid= -1 AosOhci: Initialised USB Open Host Controller at base 0DFFF7000, Irq: 11}
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): 3 ports detected.
AosUsb: Driver UsbStorageBoot (USB Mass Storage Boot Driver) has been added.
{P cpuid= 0, pid= -1 AosUsbStorageBoot: Booting from USB. Awaiting device USB0...}

Please help me!!!

[staubesv]

Cool hardware!

USB-CDROM: To be able to boot AOS from a USB CD-ROM device, you would need a AOS CD with a USB boot image (AosUSB.Bin - the one you used is the IDE boot image - AosIDE.Bin). In fact, Andre Fischer and me successfully booted from such a AOS CD a few weeks ago. You could build one yourself by modifying "Step 3" in the AosBuild.Tool file, but I would not recommend you to invest time here - it's very unlikely that your system boots from a USB CD-ROM device but not from a USB flash device.

USB-Flash: The next thing that should happen is that the USB flash device is recognized. The log output does, unfortunately, not provide any hints why the device is not detected. Attached (log on to see it) you find a USB debug boot image. Please install it on an AosFS formatted USB flash memory using the Partition Tool (Bluebottle -> UpdateBootFile, or another UpdateBootFile command) and post the log output here again.

[BohdanT]

Hi Sven!
Thank you very much for helping!
   
I successfully loaded with CF-card. http://oberon.ho.ua/files/09-06-08_1838.jpg (sorry for the quality of the image)
You can add Vortex86 processor to Hardware Compatibility list

With the installation on card, because I used CardReader, had the following parameters:
boot image - AosIDE.Bin
BootVol1=AOS AosFS IDE0#01
   

it's very unlikely that your system boots from a USB CD-ROM device but not from a USB flash device.

I absolutely agree, simply thought that the so fast get boot! 
   
If there is interest, continued attempt to boot from a USB-Flash.
New USB-Flash boot log:

Aos 02.06.2008 (Revision 1239)
Single-processor
Kernel: Initialized and started.
{P cpuid= 0, pid= -1 AosUsb: USB driver loaded.}
AosUsb: Driver UsbHub (USB Hub Driver) has been added.
{P cpuid= 0, pid= 3 AosUsb: Check connected devices for available device drivers}
{P cpuid= 0, pid= -1 PCI: Bus interface initialized.}
AosUsbOhci: Looking for PCI Open Host Controllers...
AosUsbOhci: Starting host controller initialization...
AosUsbOhci: Host Controller initialization: SMM driver found
AosUsbOhci: Host Controller initialization: OwnerShipChangeRequest succeeded.
AosUsbOhci: Starting host controller...done.
{P cpuid= 0, pid= -1 AosOhci: Initialised USB Open Host Controller at base 0DFFF7000, Irq: 11}
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller):  Capabilities:
    Compound device: No, Port indicator control: No, Power switching support: Global, Overcurrent protection: n/a
    Power On 2 Power Good: 2 ms, Control logic current: 0 mA, Think time: 2 ms
    Number of downstream ports: 3
        Port 0: [Enabled][LowSpeed][DevicePresent][Powered]
        Port 1: [Disabled][ConnectChange][Powered]
        Port 2: [Enabled][FullSpeed][DevicePresent][Powered]

AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Enable power on all ports
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Port 1: Set feature 8
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Port 2: Set feature 8
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Port 3: Set feature 8
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): 3 ports detected.
AosUsb: Registered USB device driver: UsbHub00
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Handling port status change for port 1
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Disable port 1
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Port 1: Clear feature 1
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Handling port status change for port 2
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Disable port 2
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Port 2: Clear feature 1
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Handling port status change for port 3
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Disable port 3
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Port 3: Clear feature 1
AosUsb: Driver UsbStorageBoot (USB Mass Storage Boot Driver) has been added.
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Handling port status change for port 1
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Handling port status change for port 2
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Handling port status change for port 3
{P cpuid= 0, pid= 3 AosUsb: Check connected devices for available device drivers}
{P cpuid= 0, pid= -1 AosUsbStorageBoot: Booting from USB. Awaiting device USB0...}

[staubesv]

Ahh... in the case that a SMM driver had control over the host controller, the hand-over from SMM to AOS HC driver is done, but the host controller is just "software-reset" (not H/W-reset). This means that the root hub (and therefore the status of the root ports) is not reset which again causes the hub driver to not recognize the devices correctly.

-> You have found a bug in AosUsbOhci.Mod 

Attached you find an optimistic USB boot image assuming that this was the only problem (AosUSB.Bin, revision 1239, no trace output, fixed issue) and a pessimistic one (AosUSBDebug.Bin, revision 1239, even more trace output, one issue fixed).

Please report whether this fix solves your problem.

[BohdanT]

thanks Sven!
Tomorrow, be sure to check:)

[staubesv]

It would be very nice to have the components of the eBox2300 in the hardware compatibility list on the OCP wiki (http://www.ocp.inf.ethz.ch/wiki/Documentation/HardwareCompatibility#toc16). To get the full details on the CPU, use AosCPUID.ShowDetailed ~. For details on the PCI devices, AosPCITools.Scan is useful.

[BohdanT]

http://oberon.ho.ua/files/AosUSBDebug.zip
   
I am not sure that this is a complete log. Perhaps pending Terminal, which I use.
In WinAos Terminal generally took little information: (
Probably, I write (or find) program that will better cope with this task.

[BohdanT]

AosCPUID.ShowDetailed~

Standard Function 0: Processor Vendor and Largest Standard Function:
   Vendor: SiS SiS SiS
   Largest Standard Function: 1
Standard Function 1: Family, Model, Stepping Identifiers:
   Family: 05H, Model: 00H, Stepping: 05H
   Local APIC Initial ID: 0, Logical processor count: 0
   CLFLUSH line size: 0 Bytes, BrandId: 0
   Features: [MMX][CMPXCH8B][TSC][FPU]
Extended Function 0: Largest Extended Function:
   Largest Extended Function: 0

AosPCITools.Scan~

PCI bus enumeration:
Bus 0, device 0, function 0: class/rev 06000001, vendor/device 10390550, status/cmd 22100007
   Class: Bridge, Sub-class: Host bridge
   Vendor: Silicon Integrated Systems [SiS], Device: 550 Host
   Driver: n/a
      8MB 32-bit memory at E0000000-E07FFFFF
Bus 0, device 0, function 1: class/rev 010180D0, vendor/device 10395513, status/cmd 00000005
   Class: Mass storage controller, Sub-class: IDE interface
   Vendor: Silicon Integrated Systems [SiS], Device: 5513 [IDE]
   Driver: AosATADisks.Install
      16B I/O at 0000FF00-0000FF0F
Bus 0, device 1, function 0: class/rev 06010000, vendor/device 10390008, status/cmd 0200000F
   Class: Bridge, Sub-class: ISA bridge
   Vendor: Silicon Integrated Systems [SiS], Device: SiS85C503/5513 (LPC Bridge)
   Driver: n/a
Bus 0, device 1, function 2: class/rev 0C031007, vendor/device 10397001, status/cmd 02800117
   Class: Serial bus controller, Sub-class: USB Controller, ProgIntfc: OHCI
   Vendor: Silicon Integrated Systems [SiS], Device: USB 1.0 Controller
   Driver: AosUsbHubDriver.Install;AosUsbOhci.Install
      IRQ11, INTD
      4KB 32-bit memory at DFFF7000-DFFF7FFF
Bus 0, device 1, function 4: class/rev 04010000, vendor/device 10397019, status/cmd 02900007
   Class: Multimedia controller, Sub-class: Multimedia audio controller
   Vendor: Silicon Integrated Systems [SiS], Device: SiS7019 Audio Accelerator
   Driver: n/a
      IRQ10, INTB
      256B I/O at 0000DC00-0000DCFF
      16KB 32-bit memory at DFFF8000-DFFFBFFF
Bus 0, device 2, function 0: class/rev 06040000, vendor/device 10390001, status/cmd 00000007
   Class: Bridge, Sub-class: PCI bridge, ProgIntfc: Normal decode
   Vendor: Silicon Integrated Systems [SiS], Device: Virtual PCI-to-PCI bridge (AGP)
   Driver: n/a
Bus 1, device 0, function 0: class/rev 03000000, vendor/device 10395315, status/cmd 02B00003
   Class: Display controller, Sub-class: VGA compatible controller, ProgIntfc: VGA controller
   Vendor: Silicon Integrated Systems [SiS], Device: 550 PCI/AGP VGA Display Adapter
   Driver: n/a
      IRQ0, INTA
      128MB prefetchable 32-bit memory at D0000000-D7FFFFFF
      128KB 32-bit memory at DFEE0000-DFEFFFFF
      128B I/O at 0000BC00-0000BC7F
Bus 0, device 13, function 0: class/rev 02000010, vendor/device 10EC8139, status/cmd 02800107
   Class: Network controller, Sub-class: Ethernet controller
   Vendor: Realtek Semiconductor Co., Ltd., Device: RTL-8139/8139C/8139C+
   Driver: AosRTL8139.Install;AosInitNet.Init
      IRQ5, INTA
      256B I/O at 0000D800-0000D8FF
      256B 32-bit memory at DFFF6F00-DFFF6FFF
8 devices found   

[staubesv]

Thanks for reporting!

The OHCI host controller fix has been checked in (revision 1244).
The hardware components of eBox2300 have been added to the Hardware Compatibility list.

[BohdanT]

I'm cant compare revision 1239 and 1244 therefore send log:
Boot with optimistic USB boot image (AosUSB.Bin, revision 1239).

Aos 02.06.2008 (Revision 1239)
Single-processor
Kernel: Initialized and started.
{P cpuid= 0, pid= -1 AosUsb: USB driver loaded.}
AosUsb: Driver UsbHub (USB Hub Driver) has been added.
{P cpuid= 0, pid= -1 PCI: Bus interface initialized.}
{P cpuid= 0, pid= -1 AosOhci: Initialised USB Open Host Controller at base 0DFFF7000, Irq: 11}
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): 3 ports detected.
AosUsb: Driver UsbStorageBoot (USB Mass Storage Boot Driver) has been added.
{P cpuid= 0, pid= -1 AosUsbStorageBoot: Booting from USB. Awaiting device USB0...}
AosUsbHubDriver: Warning: Connected high-speed capable device to low-/full-speed controller.
AosUsbHubDriver: USB Mass Storage Device attached to USBHC0 port 1.
AosUsbStorage: Storage device USB0 (JetFlash TS128MJF110) is now accessible.
{P cpuid= 0, pid= -1 AosUsbStorageBoot: Boot device USB0 connected.}
AosUsbHubDriver: Root Hub USBHC0 (USB Open Host Controller): Couldn't get device qualifier.
AosUsbHubDriver: Logitech USB-PS/2 Optical Mouse attached to USBHC0 port 2.
AosDiskFS: 36516K of 127324K available on USB0#1
{P cpuid= 0, pid= -1 AosMemCache incompatible with Machine/MaxCPU}
Default font installedOpenType 0.45 BBPort /3.12.2004  eos, pl

PS:
   
If boot from CF-card, a USB-mouse must replug, what would it work
perhaps it is because the old used AosUsbOhci?

[staubesv]

The problem in the trace output is "AosMemCache incompatible with Machine/MaxCPU". This indicates that the modules linked into the boot image are not compatible with the object files on the file system. (Machine.MaxCPU has been changed from 6 to 8 in revision 1237, but from your first trace output in this topic, it seems that you use object files of revision 1234).

To solve the problem, copy AosUsbOhci.Mod (revision 1244) to your system and compile it (the interface is still the same, therefore it's enough to just compile this one module). Then, create a new USB boot image using the Linker.Link command found in Release.Tool:

Code:

Linker.Link \PAOS: \.Obx AOS:AosUSB.Bin 0100000H 1000H Kernel Traps
AosUsbHubDriver AosUsbEhci AosUsbUhci AosUsbOhci AosUsbStorageBoot
AosDiskVolumes AosDiskFS AosConsole ~

and use that boot image.

Yes: Using the new AosUsbOhci, you will not have to re-plug USB devices that have been connected before the AOS USB driver has been loaded anymore.

[BohdanT]

Okay, thank you.
Tomorrow will try 

[BohdanT]

Thanks Sven!
All happened!
The mouse no longer needed reconnection 
   
Now the new challenge to run Aos on eBox4300 with VIA Eden ULV 500MHz processor