reboot forces poweroff and vice versa

    I noticed that the commands reboot and poweroff seems to be switch on the current fsimx8mp version.


    When I try to reboot the system on the command line interface via "reboot" the system stops and halts, but mainly never somes up (see [1]). Sporadically I noticed a reboot.

    On the other side when I try to perform a poweroff to shut down the system, its starting again right away.



    I am the only one with this issue? What can be done to fix this behavior?



    [1]:

    Code
    1. …
    2. kvm: exiting hardware virtualization
    3. reboot: Restarting system


    ------------ freeze ------------------



    [2]:

    Hello,


    the second case [2] with the reboot at shutdown / poweroff is related to the post. Thank you for referencing it.

    The commit for the ATF is pushed on our Github and will be in the upcoming release: Fix poweroff command and ON/OFF button in imx_system_off() · FSEmbedded/atf-fus@2465c76 · GitHub


    The first case [1] is currently unknown and I can't reproduce it. I am trying it with the release fsimx8mp-2023.09. Do you use a baseboard of your own or are you using a starterkit of ours? If you are using a starterkit the revision of it would be good to know too.



    Your F&S Support Team

    I updateed NBOOT from NBoot: 2023.09 to NBoot: 2024.06. I still get the freeze while running "reboot". But the command "poweroff" now successfully halts the system (see [1]).


    Thanks.


    [1]:

    # poweroff

    # fec 30be0000.ethernet testernetwork: Link is Down

    EXT4-fs (mmcblk2p2): re-mounted. Opts: (null). Quota mode: none.

    The system is going down NOW!

    Sent SIGTERM to all processes

    Sent SIGKILL to all processes

    kvm: exiting hardware virtualization

    reboot: Power down


    ------------- freeze ------------

    Hello,


    could you provide some additional information on the reboot issue?

    Is this happening regularly or just some times?

    If you connect the board to your PC via UBS-Device, does the board get recognized by your PC after the issue occures?

    This would hint to a problem with the Bootselect pin.


    Your F&S Support Team

    Hello,


    thanks for the question about details. I have carried out a reboot test on our prototype with a new base board and with the SKIT.


    Prototype with new base board:

    I ran a test to reboot the system per command in a loop and after 30 loops every thing went fine. The module every time rebooted.

    SUCCESS


    SKIT:

    Than I ran the reboot loop test with the SKIT and after 11 loops the SKIT freezes and did not reboot. I than checked vie USB if my system recognize the board: see [1].

    FAIL



    [1]:

    $ lsusb

    …

    Bus 001 Device 019: ID 1fc9:0146 NXP Semiconductors

    …


    $ dmesg -w

    …

    [1296107.274894] usb 1-4.2.1: new high-speed USB device number 19 using xhci_hcd

    [1296107.403837] usb 1-4.2.1: New USB device found, idVendor=1fc9, idProduct=0146, bcdDevice= 0.02

    [1296107.403869] usb 1-4.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

    [1296107.403886] usb 1-4.2.1: Product: SE Blank 865

    [1296107.403899] usb 1-4.2.1: Manufacturer: NXP SemiConductor Inc

    [1296107.409724] hid-generic 0003:1FC9:0146.0046: hiddev2,hidraw4: USB HID v1.10 Device [NXP SemiConductor Inc SE Blank 865 ] on usb-0000:00:14.0-4.2.1/input0

    …

    Hello,


    good to hear that it works with your baseboard.


    There might be an supply issue on our baseboard that may cause a sporadic trigger on the boot select line when doing a soft reset under certain conditions.


    We will investigate that further.


    Your F&S Support Team