This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP5432evm issues

Hello all,

While using the omap5432evm we've encountered some issues that we haven't been able to solve.

Were using the 5AJ1.5.1 software found on the ti site.
Android version 4.2.2
linux kernel 3.4.48


Does anyone now how to fix the following issues:

- Command mode using the panel-taal.c driver has a slight delay. Video mode works perfectly so its not panel related. Is there a fix for this or a panel driver that works properly?

-USB doesn’t start always if not doing a cold start. When failing the following error repeats several times
ehci-omap echi-omap.0: port 2 reset error -110

- Terminal goes into some kind of sleep mode if no input is given and the first key entered after that will be ignored.

- When mounting an usb through the terminal the contents of this usb cannot be seen through a file viewer in android. This is probably because I dont have root access when using android through the android GUI. Is there a way to fix this without rebuilding android?

Any help would be appreciated.

Best regards,

Anthony

  • Hi  Anthony,

    As I said about the USB problem on the omap5 evm is because of misbehaviour of the hub chip itself. It occures from board to board, and various ways to fix it are available. Which are widely discussed in the forums.

    What application are you using for browsing the content of your usb device?

    Are you setting the following bootarg: no_console_suspend=1 ?

    Regards,

    Boyko

  • Hello Boyko,

    I should have mentioned that I already tried several fixes discussed on the forums for the USB but so far without result.

    For browsing the contents I tried the following:
    - ES_File_Explorer_3.0.5.apk
    - filemanager.apk
    Both of which can't see the contents of the usb flash drive.


    The command line I'm using is as follows:
    sudo ./mkbootimg --kernel zImage --ramdisk ramdisk.img --cmdline "no_console_suspend=1 console=ttyO2,115200n8 androidboot.console=ttyO2 omap_wdt.timer_margin=30 vmalloc=496M omapfb.fb_opt=-1,-1,-1,1,1080,1920 mem=1024M vram=128M omapfb.vram=0:60M,1:60M earlyprintk loglevel=7 omapdss.debug=y" --base 0x80000000 --output boot.img

    Best regards,

    Anthony

  • Hi Anthony,

    The key of resolving the usb issue is the status of the hub,

    it is dependable on your system when you init it or reset it after some particular event in order to resume the normal operation of the hub. The best way is to control the hub by its I2C lines.

    This is odd why your console  gets suspended.  I wasnt able to recreate that case. What is the status of the ADB session when this happens?

    Regards,

    Boyko

  • Hello Boyko,


    The terminal is running like it should
    Tthe whole boot sequence continues as it should but when trying to input something the first key is ignored
    Everything inputted after that one is accepted
    If there is no input for 5 seconds after the last one it then it ignores the first one again.

    Also all information coming from the board is accepted. Only the information that I input myself has this issue.

    Im using minicom for this maybe its related to this.
    Are you using a different one? If yes whats that one called?

    Best regards

    Anthony

  • Hi Anthony,

    I just realized that in my workflow the first thing i do is to press enter, so I have never observed this behaviour, till now.

    So indeed the console is still suspended despite it shouldn't be. I will check what might be the cause of it. 

    ( it might be coming from the FTDI chip)

    Regards,

    Boyko

  • Terminal goes into some kind of sleep mode if no input is given and the first key entered after that will be ignored.

    For this issue, it is because driver set console suspend timeout = 3 sec. you can modify arch/arm/mach-omap2/board-omap5evm-serial.c 

    set autosuspend_timeout from 3000 to -1 ( make sure your uart port number is correct, or you can set all uart port without autosuspend ) .

     

  • Hello Yi-chia lan,


    Thanks, this solved the issue.


    Best regards,

    Anthony