8 replies to this topic

[Admin]

To test that the embedded controller is set up properly and the connection to a host system is established you can follow the steps:

1. Disconnect the USB to UART cable from your PC, if already connected
2. Connect the USB to UART adapter to the Embedded Controller, align the dot on the connector to pin 1 on JP2
3. Instert the USB dongle into one of the USB ports (if provided)
4. Connect the power supply to the Embedded Controller
5. Connect the USB cable to your PC
6. Start HyperTerminal if using Windows from Start -> Programs -> Accessories or if using Linux start minicom
7. Select the COM port of the USB cable or serial adapter and 115200 baud, 8 bits, None, 1, Handshake: None

You should be able to see the controller booting up.

[dangs]

To test that the embedded controller is set up properly and the connection to a host system is established you can:

1.Start HyperTerminal (if using Windows) from Start -> Programs -> Accessories
2. Select the COM port of the USB cable or serial adapter and 115200 baud, 8 bits, None, 1
parity
3. Insert the Squidge Kingston USB key into one of the USB ports on the
controller board and connect it to the power

You should be able to see the controller booting up.

If you are using a linux host you can use usbview or hardware tool to find the name of the USB/COM port. ( in my case it is /dev/ttyUSB0 ).
Then set up minicom in the same manner as above.

[steve]

If you are using a linux host you can use usbview or hardware tool to find the name of the USB/COM port. ( in my case it is /dev/ttyUSB0 ).
Then set up minicom in the same manner as above.

This is the same for Mac OS X (which I based on unix so duh) but figured I'd throw it out there!

[steve]

Guess it would have been easier if I bought a cable to connect to this baby lol. I'm guessing it's not going to just go straight into DHCP and pull an IP.

Especially since I'm a tight bstard and coulda included it in the original postage fee. Plus the price is £3 more if bought without the controller. oopsy doopsy.

[pjd]

Just got my board today, I didn't bother with the uart cable either, the distro on the usb key (squidge) does not come with dhcp enabled, by default the squidge distro is setup to use 192.168.1.1 in bridge mode, this means you either set another computer to run on the 192.168.1.* range or you mount the usb stick and edit etc/config/network and change the ip from 192.168.1.1 to something in your networks range.

Note that when you login for the first time via telnet it tells you that you can set the root passwd and then telnet will be disabled and dropbear ssh will be enabled DO NOT DO THIS IF YOU ONLY HAVE NETWORK ACCESS TO THE BOARD!! The problem is that setting the root password will disable telnet (although the current session will continue) and it would enable dropbear ssh, however dropbear ssh is not installed so you will be locked out of the device! If you do get locked out then the only way to fix it is to mount the usb stick in another machine and either fix the telnet init.d script or restore the old passwd file in /etc ( mv etc/passwd- etc/passwd ).

It is possible to install the dropbear ssh package from /www/squidge/packages using ipkg however there appears to be no way to generate ssh keys in this distribution and without those dropbear will fail to start, dropbear does not come compiled to support key generation and ssh-keygen isn't available so it means that you need to generate ssh keys elsewhere and copy across unless someone else wants to post here a way to do it as I'm not spending much more time on this as I think I'm going to abandon squidge and run something else.

[Greg Wright]

If you are using a linux host you can use usbview or hardware tool to find the name of the USB/COM port. ( in my case it is /dev/ttyUSB0 ).
Then set up minicom in the same manner as above.

I've set up minicom as above (had to link /dev/ttyUSB0 to /dev/modem) and can watch the system booting. Once the system is ready I get the message "Please press Enter to activate this console." however the key press does not seem to be sent to the device so I never get as far as a login/root prompt. Looks to me like a problem with my minicom setup. Any thoughts?

[Ian Braithwaite]

I've set up minicom as above (had to link /dev/ttyUSB0 to /dev/modem) and can watch the system booting. Once the system is ready I get the message "Please press Enter to activate this console." however the key press does not seem to be sent to the device so I never get as far as a login/root prompt. Looks to me like a problem with my minicom setup. Any thoughts?

I've not tried minicom, but "cu -l ttyUSB0" is working fine for me.
No setup required...

[prioryjim]

Just got my board.
Loaded USB mini CD into my Vista PC. Plugged in cable and vista started to installed.
Eventually it found CD but reported some CRC error, tried again but same error.
Ejected CD and polished CD on my shirt.
Tried again and all went OK.
Vista doesn't have hyperterminal but I have putty which also allows serial connections.
Setup was simple and all went OK.
Powered on board and again all OK and I am logged on via serial cable.
Jim

[prioryjim]

Oh dear I set a password for root, and as above the net login has stopped.
Messed around for quite a while using serial login but couldn't fix telnet logins.
telnetd was running OK but rejected login.
So down loaded squidge and loaded up another USB on another linux server
See
http://squidge.sourc...mware-uploading section "Rootfs preparation"

Put in one USB slot and booted Omnima board.
Put old usb in other slot.
Copied /etc/passwd from one to the other
Removed new usb
And booted from original
It went OK
For ref original passwd file is ...

root:!:0:0:root:/root:/bin/ash
nobody:*:65534:65534:nobody:/var:/bin/false
daemon:*:65534:65534:daemon:/var:/bin/false
Jim