Rafael Hernández

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Modem Lock-up Issue #7569
    Rafael Hernández
    Participant

    Digging a little bit deeper /usr/sbin/radio-reset-h5 is a simple script:

    rmmod ohci_hcd
    mts-io-sysfs store radio-reset 0
    sleep 8
    modprobe ohci_hcd

    It already contains the “mts-io-sysfs store radio-reset 0” instruction!

    On the other hand, be careful with the environment when you invoke radio-reset-h5, it assumes you have a PATH correctly initialized (which, for instance, may not be true in tasks triggered by cron).

    /usr/sbin/radio-reset-h5: line 11: rmmod: not found
    /usr/sbin/radio-reset-h5: line 12: mts-io-sysfs: not found
    /usr/sbin/radio-reset-h5: line 14: modprobe: not found

    So, maybe, this is the reason why radio-reset-h5 does not always recover the modem.

    in reply to: Modem Lock-up Issue #7568
    Rafael Hernández
    Participant

    Mark, what I see from the logs is this:

    When the modem doesn’t work on startup, it is not because the mtcdp doesn’t recognize it. It does recognize it and sets it up correctly. The problem comes a few seconds after that: there is an entry in the messages log stating

    mtcdp user.info kernel: usb 1-1: USB disconnect, address XX

    and then it is rediscovered again

    mtcdp user.info kernel: usb 1-1: new full speed USB device using at91_ohci and address YY

    The rediscovery process enters an endless loop. Externally you may see that the LS led blinks once every 7 seconds.
    Should this happen, the two instructions

    /usr/sbin/mts-io-sysfs store radio-reset 0
    /usr/sbin/radio-reset-h5

    solve the situation

    in reply to: Modem Lock-up Issue #7538
    Rafael Hernández
    Participant

    I’ll try to catch some for you.
    It is true that the sequence

    old-radio-reset + reboot

    does not always work. In some cases, my mtcdp needs 2-3 retries before detecting the modem again.

    in reply to: Modem Lock-up Issue #7510
    Rafael Hernández
    Participant

    Hello,
    I am having the same issue. What I used to do after detecting the modem’s lock up was to reboot the MTCDP. In a number of cases a soft reboot was not enough to to get the modem back to work. It needs a power down.
    Playing around I discovered a way to recover the modem: perform an old-fashion reset before calling radio-reset-h5:

    
    /usr/sbin/mts-io-sysfs store radio-reset 0
    /bin/sleep 5s
    /usr/sbin/radio-reset-h5
    

    In my devices, I’m still rebooting them instead of issuing a radio-reset-h5.

    in reply to: Permanently changing eth0 MAC-address #6795
    Rafael Hernández
    Participant

    MultiTech support has given me the solution:
    u-boot setenv ethaddr XX:XX:XX:XX:XX:XX

Viewing 5 posts - 1 through 5 (of 5 total)