First Build - White screen to RetroPie logo to white

[polytrigon]

Is the front green light still on?
Can you connect HDMI to see what the Freeplay CM3 is doing at that time?
Are you able to SSH into the machine?

Either HDMI or SSH will let you know if the machine is still running, and it would be interesting to know what's on the HDMI screen when the LCD goes white.

There is a new problem with the Freeplay Zero when running on RetroPie 4.4.  We have a fix for that, but it didn't seem to be necessary on the CM3.  I guess it's possible that the fix needs to be implemented for some CM3s.  Perhaps your SD card changes the boot speed or something.

If you can SSH in (or use a keyboard + HDMI), you could test this fairly easily by adding a "sleep 6" in /etc/init.d/fbcp.sh
sudo nano /etc/init.d/fbcp.sh

Change this function:

Code:

do_start()
{
        # Return
        #   0 if daemon has been started
        #   1 if daemon was already running
        #   2 if daemon could not be started
        start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
                || return 1
        start-stop-daemon --start --quiet --background --make-pidfile --pidfile $PIDFILE --exec $DAEMON -- \
                $DAEMON_ARGS \
                || return 2
}

to

Code:

do_start()
{
        # Return
        #   0 if daemon has been started
        #   1 if daemon was already running
        #   2 if daemon could not be started
        start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
                || return 1
        sleep 6
        start-stop-daemon --start --quiet --background --make-pidfile --pidfile $PIDFILE --exec $DAEMON -- \
                $DAEMON_ARGS \
                || return 2
}

Will give this a try when I get a chance. The green light is on when it is white screening. I left the unit on for 2 hours to see if it needed time to process - still white screen.

Tried using a third SD card just to rule out that it's not an issue with the cards I had. Still with the same behavior.

What is the possibility that my CM3 module is defective?