Have a RIoTboard question?  Ask the expert, John McLellan

Hi John:

After installing Linux, everythig looked OK, but some days later, an extrange problem with screen detection, both HDMI (a common  PCscreen) and LVDS ( LCD8000-97C), avoids a normal start. I tested both screens, but not at the same time, changing environment according to the screen used.

I decided reinstall Linux.
The situation is:
If I stop autoboot (u-boot command line) then the installation tool freezes, else (autoboot time out) the installation tool stop recognizing the device, and installation fails.
SW1 is in the correct state for serial download.

Any idea for recovering the Riotbard?

@franchisco

an extrange problem with screen detection, both HDMI (a common  PCscreen) and LVDS ( LCD8000-97C),avoids a normal start.

blank screen  on LCD8000-97C display can be fixed by updating uboot params.

if you are still facing challenges on LVDS after configuring as above , please share the logs .

the installation tool stop recognizing the device, and installation fails.

I guess you are referring MFG tool as installation tool.

MFG needs two configuration files [ cfg.ini  & ucl2.xml ] to proceed with installation.

cfg.ini is available in MFGTools directory "/Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATE"  and has below contents in it.

[profiles]

chip = MX6DL Linux Update

 

[platform]

board = RIOT

 

[LIST]

name = i.MX6SOLO-ubuntu-RIOT-eMMC

the name (i.MX6SOLO-ubuntu-RIOT-eMMC) in "cfg.ini" is used a candidate for profile selection in the next step.

the other file is present as ucl2.txt in MFGTools directory "/Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER/Profiles/MX6DL Linux Update/OS Firmware".

rename the file from ucl2.txt  to ucl2.xml .

after renaming the MFGTools will be able to recognize the board.

the "ucl2.xml" contains the instructions to erase eMMC and install firmware (linux/android).

the instuctions are available under "i.MX6SOLO-ubuntu-RIOT-eMMC" (~line 934) and looks like below

<LIST name="i.MX6SOLO-ubuntu-RIOT-eMMC" desc="Choose eMMC as media"> 

    <CMD state="BootStrap" type="boot" body="BootStrap" file ="u-boot-mx6solo-riot.bin" >Loading U-boot</CMD>

    <CMD state="BootStrap" type="load" file="uImage" address="0x10800000"

MFG flasher will flash files in "/Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER/Profiles/MX6DL Linux Update/OS Firmware"  according to above instructions.

please check the ucl2.xml file to get more details.

 

SW1 is in the correct state for serial download.

after serial download  power down the board and configure the boot switch back to eMMC boot mode as shown in user manual (Table4.2, Pg46).

Any idea for recovering the Riotbard?

please elaborate on what state the  riotboard is stuck up and share the logs so that we can help to get your board up and running .

Thanks

Tushar

Tusharp:

Thank you for your response.

Yes, it is MFG Conf tool.

Both cfg.ini and ucl2.xml (renamed from txt to XML) are exactly as you say.

In fact, I did get Linux installed; although just only one time, when I tryed to reinstall it is when CFG tool failed.
So the configuration, image, etc.  files were correct. I don't know if they have been corrupter after the installation, but at least cfg.ini and ucl2.xml are correct.

please elaborate on what state the  riotboard is stuck up and share the logs so that we can help to get your board up and running .

the MFTool.log file is

DLL version: 2.2.3

Wednesday, April 09, 2014 23:51:01   Start new logging

ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running

ModuleID[2] LevelID[1]: new MxHidDeviceClass

ModuleID[2] LevelID[10]: new MxHidDevice[031FF550]

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

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

-riot.bin

ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is D:\Descargas\RIOTBoard\Linux\tools\Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\Profiles\MX6DL Linux Update\OS Firmware\uImage, address is 0x10800000

ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0

ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is D:\Descargas\RIOTBoard\Linux\tools\Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\Profiles\MX6DL Linux Update\OS Firmware\initramfs.cpio.gz.uboot, address is 0x10C00000

ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0

ModuleID[2] LevelID[10]: ExecuteCommand--Jump[WndIndex:0]

ModuleID[2] LevelID[10]: *********MxHidDevice[031FF550] Jump to Ramkernel successfully!**********

ModuleID[2] LevelID[10]: CmdOperation[0], current state command has been finished and the last command is successful, so SetEvent(hDevCanDeleteEvent)

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&PID_0061#5&36d49436&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&PID_0061#5&36d49436&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 1

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, devInstPathToFind: USB\VID_15A2&PID_0061\5&36D49436&0&1, _deviceInstanceID: USB\VID_15A2&PID_0061\5&36D49436&0&1

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, Find the device

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0061, Hub:5-Port:1

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_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 Remove

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

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

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent()-DEVICE_REMOVAL_EVT, hDevCanDeleteEvent has been set

ModuleID[2] LevelID[10]: delete MxHidDevice[031FF550]

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

As it seems that my first post was not clear, I'll try explaining it better:

• After installing Linux and working a couple of days, the RB generated this message while booting: "The system is running in low-graphics mode".
• In the options after pressing OK, I selected "Review the xserver log file", where line [26.137] says "No screen section available. Using defaults. The section, apparently should be in /usr/share/X11/xorg.conf.d
• Pressing OK and selecting "run in low-graphics mode for just one sesión" puts the screen in black with one blinking cursor top-left, and that's all in the screen, although I keep the control using the serial port terminal (putty).
• This error happens both using HDMI and LVDS outputs. Of course, after changing uboot environment parameters, according RB user manual, and repeating the whole process.
• As the error persisted, I tryed to reinstall Linux following the instructions of RB user manual pg 43 and next.
• I connected both USB and serial port to my PC. Changed SW1 and started MFG configuration tool.
• The MFG showed a HID compliant device, and stated downloading the files.
• But as soon MFG reach "jumping to OS image" the serial port start showing the booting process.
• Then I have two options:
  • Let the boot continue: then MFG Tool cahnge to "No device connected" and after finishing the boot, I get the same error in the screen: "The system is runnig in low graphics mode"
  • Interrupt it by pressing a key before the three second time-out period and entering in U-boot command line. In this case MFG conf tool freezes and never end the download.

So, this is the problem: Linux is only available through serial port terminal, and a new installation is not possible.

Thank you again, Francisco

Tusharp:

Thank you for your response.

Yes, it is MFG Conf tool.

Both cfg.ini and ucl2.xml (renamed from txt to XML) are exactly as you say.

In fact, I did get Linux installed; although just only one time, when I tryed to reinstall it is when CFG tool failed.
So the configuration, image, etc.  files were correct. I don't know if they have been corrupter after the installation, but at least cfg.ini and ucl2.xml are correct.

please elaborate on what state the  riotboard is stuck up and share the logs so that we can help to get your board up and running .

the MFTool.log file is

DLL version: 2.2.3

Wednesday, April 09, 2014 23:51:01   Start new logging

ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running

ModuleID[2] LevelID[1]: new MxHidDeviceClass

ModuleID[2] LevelID[10]: new MxHidDevice[031FF550]

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

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

-riot.bin

ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is D:\Descargas\RIOTBoard\Linux\tools\Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\Profiles\MX6DL Linux Update\OS Firmware\uImage, address is 0x10800000

ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0

ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is D:\Descargas\RIOTBoard\Linux\tools\Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\Profiles\MX6DL Linux Update\OS Firmware\initramfs.cpio.gz.uboot, address is 0x10C00000

ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0

ModuleID[2] LevelID[10]: ExecuteCommand--Jump[WndIndex:0]

ModuleID[2] LevelID[10]: *********MxHidDevice[031FF550] Jump to Ramkernel successfully!**********

ModuleID[2] LevelID[10]: CmdOperation[0], current state command has been finished and the last command is successful, so SetEvent(hDevCanDeleteEvent)

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&PID_0061#5&36d49436&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&PID_0061#5&36d49436&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 1

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, devInstPathToFind: USB\VID_15A2&PID_0061\5&36D49436&0&1, _deviceInstanceID: USB\VID_15A2&PID_0061\5&36D49436&0&1

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, Find the device

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0061, Hub:5-Port:1

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_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 Remove

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

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

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent()-DEVICE_REMOVAL_EVT, hDevCanDeleteEvent has been set

ModuleID[2] LevelID[10]: delete MxHidDevice[031FF550]

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

As it seems that my first post was not clear, I'll try explaining it better:

• After installing Linux and working a couple of days, the RB generated this message while booting: "The system is running in low-graphics mode".
• In the options after pressing OK, I selected "Review the xserver log file", where line [26.137] says "No screen section available. Using defaults. The section, apparently should be in /usr/share/X11/xorg.conf.d
• Pressing OK and selecting "run in low-graphics mode for just one sesión" puts the screen in black with one blinking cursor top-left, and that's all in the screen, although I keep the control using the serial port terminal (putty).
• This error happens both using HDMI and LVDS outputs. Of course, after changing uboot environment parameters, according RB user manual, and repeating the whole process.
• As the error persisted, I tryed to reinstall Linux following the instructions of RB user manual pg 43 and next.
• I connected both USB and serial port to my PC. Changed SW1 and started MFG configuration tool.
• The MFG showed a HID compliant device, and stated downloading the files.
• But as soon MFG reach "jumping to OS image" the serial port start showing the booting process.
• Then I have two options:
  • Let the boot continue: then MFG Tool cahnge to "No device connected" and after finishing the boot, I get the same error in the screen: "The system is runnig in low graphics mode"
  • Interrupt it by pressing a key before the three second time-out period and entering in U-boot command line. In this case MFG conf tool freezes and never end the download.

So, this is the problem: Linux is only available through serial port terminal, and a new installation is not possible.

Thank you again, Francisco