Linux flashing, no device connected under Windows XP

Take a Look here in the FAQ section.RIoTboard Platform Glossary

Take a Look here in the FAQ section.RIoTboard Platform Glossary

Problem is that the USB HID isn't listed at all...not visible under WinXP under Parallels nor under OSX...

And yes..DIP switches are set correctly...the OTG conenctor is the one besides the LAN port, right?

If the driver isn´t recognized just by plugging the board in, then you have to do it manually. (No additional Driver needed from WindowsXP and onwards.)

I described this here: Re: Riotboard not recognized in Device Manager

(The deccription can change a bit since you have XP)

Also you maybe have to remove some old drivers.
I´ve written something about this in the same thread here: Re: Re: Riotboard not recognized in Device Manager

(This applies to all Windows Versions from XP onwards.)

The FAQ points to this thread, that´s why I´ve written that first.

Not the driver isn'r recognized...

The USB isn't listed at all....OSX shows under "Profile" all USB devices connected...regardless if they have a driver or not...

So it seems the USB OTG isn't initialized properly as a HID....

I don´t understand what your problem is.

Look into your device manager in Windows and look for an unknown device.

If you have that after plugging in th riotboard, you have to follow the steps I´ve written in the thread.

Windows does NOT recognize devices as USB if it can´t install a driver for it. It´s just an unknown device.

Let me explain again (o;

There is NO USB device recognized when plugging in the USB cable...just like no USB device is attached at all...

Nothing to do with drivers, Windows, or any other OS....

That's confusing because you have written in your first post that an USB device is recognized in Windows XP.

Only thing you can do is switch the cable or try another pc.

Also check the dip switches if they work correctly.

Stupid me ;-)

In the manual the DIP switches are labelled from left to right for S1 - S8 with a picture of the DIP switch below...but the DIP switches start from right to left...so it never entered the device mode...

Loads now the OS but fails in writing the rootfs:

Serial console output:

tar: short read

MfgTool error:

"Push" error, file="C:\Dokumente und Einstellungen\Administrator\Desktop\Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\Profiles\MX6DL Linux Update\OS Firmware\files\oneiric.tgz"

Is this the error from the log file?

If not look into the log file if you have some more info.

You´re the first with such an error.

This is the content of the log file:

ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 1

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:1, Volume->_diskNumber:1

ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 00BA1AF0

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 3

ModuleID[2] LevelID[10]: VolumeDeviceClass::AddUsbDevice() successful E add to current list, retrycount: 0

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 3

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT-Disk(E), Hub:2-Port:3

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT, Notify

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive

ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.

ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1

ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 1

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is send

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ tar xf $FILE

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ sh mksdcard.sh /dev/mmcblk0

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is send

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ dd if=$FILE of=/dev/mmcblk0 bs=512 seek=2 skip=2 conv=fsync

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ dd if=/dev/zero of=/dev/mmcblk0 bs=512 seek=1536 count=16

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is send

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ dd if=$FILE of=/dev/mmcblk0 bs=1M seek=1 conv=fsync

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ mkfs.ext3 -j /dev/mmcblk0p1

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ mkdir -p /mnt/mmcblk0p1

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ mount -t ext3 /dev/mmcblk0p1 /mnt/mmcblk0p1

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is pipe tar --numeric-owner -zxv -C /mnt/mmcblk0p1

ModuleID[2] LevelID[1]: PortMgrDlg(0)--MSCDevice--Command Push(file) excute failed

ModuleID[2] LevelID[10]: CmdOperation[0], current command executed failed, so SetEvent(hDevCanDeleteEvent)

ModuleID[2] LevelID[10]: CCmdOpreation[0] thread is Closed

ModuleID[2] LevelID[10]: CCmdOpreation[0] thread is Closed

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - EVENT_KILL

ModuleID[2] LevelID[10]: CMyExceptionHandler::OnMsgExceptionEvent() - KillExceptionHandlerThread

ModuleID[2] LevelID[10]: Exception Handler thread is closed

ModuleID[2] LevelID[1]: delete MxHidDeviceClass

ModuleID[2] LevelID[10]: Device Manager thread is closed

Same info...

Only says push of the file failed...

Maybe the file is damaged?

Try to overwrite the file "Profiles\MX6DL Linux Update\OS Firmware\files\oneiric.tgz" with a freshly unpacked.

Also there should be another "oneiric.tgz" in the downloaded zip in the folder "image_SVN2487".

(They´re double in the zip file. Could save half of the file size if it wasn´t there...)

Try to overwrite the one in the profile folder with that one.

Or if you already did that and you get that error, overwrite it with the one in the Profile folder in the zip.