• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 1593 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Reboot command not working with custom board based on OMAP4460

sanjay c
Intellectual 290 points
Other Parts Discussed in Thread: TWL6032, TWL6030, TMP102, 4430

Hello,

I am working on a custom board based on OMAP4460. I am working with android ICS software release 4AI-1.4.

If we enter reboot command in the prompt the board does not reboot and just freezes with the following dmesg

root@android:/ # reboot
[ 71.123291] SysRq : Emergency Remount R/O
[ 71.174499] Emergency Remount complete
[ 71.297332] PVR: PVRSRVDriverShutdown(pDevice=c78a5c00)
[ 71.315734] PVR: SysSystemPrePowerState: Entering state D3
[ 71.336944] PVR: Uninstalling device LISR on IRQ 53 with cookie c732b100
[ 71.368286] PVR: DisableSystemClocks: Disabling System Clocks
[ 71.444122] Restarting system.
[ 71.447570]
[ 71.449249] Restarting Linux version 3.0.21-00003-OMAP-Android+ (sanjay@mistral-Veriton-Series) (gcc version 4.4.1 (Sourcery G++ L
ite 2010q1-202) ) #6 SMP PREEMPT Tue Nov 27 14:22:01 IST 2012
[ 71.449249]

We have used a PMIC (TWL6030B1AACMR) with primary watchdog timer and charger watchdog enabled.

We observed that after reboot command, WARM reset is asserted from OMAP and VMMC goes to 1.8V  and never comes back to 3V.

Any pointers would be helpful.

Thank you for your time.

Regards,

Sanjay

  • 0
    TI__Genius 10545 points

    There is this post that talks for similar issue,

    http://e2e.ti.com/support/omap/f/849/t/227658.aspx

    and what version of Android SDK or ADB are you using? is the one from?

    /mydroid/out/host/linux-x86/bin

    sometimes using older ADB version makes it to fail.

  • 0 in reply to Manuel Contreras
    Intellectual 290 points

    Hello Manuel Contreras,

    Thank you very much for the reply.

    The patch mentioned in the other thread is part of my x-loader, also in my case after reboot x-loader does not start.

    I am not using ADB, i am using UART for serial communication.

    Regards,

    Sanjay

  • 0 in reply to sanjay c
    TI__Genius 10545 points

    Ok thanks, let me check it then, are you adding some other change apart from 4AI.1.4?

  • 0 in reply to Manuel Contreras
    Intellectual 340 points

    Hi all,

    We have exactly the same problem. But we're using custom board with omap4430 and twl6032. This board is running Android 4AJ.1.1 and Kernel version is 3.0.31.

    We have no problems with the "cold reset" which is used in u-boot. 

    When warm reset is issued by the "reboot" command kernel goes to prm44xx.c:omap4_prm_global_warm_sw_reset function and hangs after omap4_prm_write_inst_reg(v, OMAP4430_PRM_DEVICE_INST,OMAP4_RM_RSTCTRL);

    Also we have a button connected to the SYS_NRESWARM line. Pressing a button leads to exactly the same results.

    Regards,

    Alexey

  • 0 in reply to Alexey Firago
    TI__Genius 10545 points

    I am not able to reproduce the issue using my local setup and 4AI1.4 release.

    For debugging and issue tracing it could help to identify the issue using the commands in this post

    http://e2e.ti.com/support/omap/f/849/p/225255/794196.aspx#794196

    and find where system is hanging, comparing logs it seems to completely shutdown the system and hang just before starting at x-loader.

    For what I know mentioned patch must be the solution for regular issue, but there are some other changes involved that could be affecting.

    Alexey,

    for the issue about OMAP4430 and TWL6032,you have this other post

    http://e2e.ti.com/support/omap/f/849/t/229132.aspx

    by cross referencing the information I found next post talking about OMAP4470 and TWL6032,

    http://e2e.ti.com/support/omap/f/849/p/213437/754051.aspx#754051

    for OMAP4430 it is used TWL6030, other post talks about supporting OMAP4460 and TWL6032, but it requires some changes,

    Kernel patches:
    http://review.omapzoom.org/#/c/23569/
    http://review.omapzoom.org/#/c/23568/
    x-loader patch:
    http://review.omapzoom.org/#/c/23479/

    in first patch 23569 is a comment in next file that could require some check up for OMAP4430 or some other changes,

    http://review.omapzoom.org/#/c/23569/4/drivers/staging/thermal_framework/sensor/tmp102_temp_sensor.c

    One another options is this forum PMU Forum where you can ask about TWL6032 issues or compatibilities.

  • 0 in reply to Manuel Contreras
    Intellectual 340 points

    Manuel,

    Thanks for the detailed answer. Issue from http://e2e.ti.com/support/omap/f/849/t/229132.aspx is resolved and the reason of this issue is not twl6032.

    Regarding changes to use twl6032: I've made some changes in kernel similar to these patches, but not all of them. And I didn't made any changes in xloader. I'll try these patches.

    Thanks,

    Alexey

  • 0 in reply to Manuel Contreras
    Intellectual 290 points

    Hello Manuel Contreras,

    We were able to fix this issue by changing the OMAP boot strap.

    The initial boot strap setting was 0b010110 which corresponds to USB(1), UART, MMC1, MMC2

    Later we changed it to 0b000101 which corresponds to USB(1), MMC1.

    Can you please explain as to why soft reboot works with second OMAP boot strap settings.

    We observed similar behavior with the Blaze Board.

    Thank you for your time.

    Regards,

    Sanjay

  • 0 in reply to sanjay c
    TI__Genius 10545 points

    It looks related to the note in section 27.2.4.2 Booting Device Order Selection, this for 4430 TRM.

    The note mentions that in warm reset non permanent boot devices are skipped, in second configuration MMC1 is marked as permanent and in first it is not. Permanent boot devices are marked in bold for table 27-7.