APIX2 on EVO HW2.3 ID5/ID6 script fix

[superwofy]

There's an issue on the Jacinto bootloader side that prevents APIX2 screens from working correctly on SPI/MII on EVO HW2.3 when flashed for ID5/6.

I have not been able to figure out exactly why. At first it appeared that the apix conf files are different and also the baud rate in spi1-apix2.cfg. I've played around with these extensively and was not able to pinpoint the issue to them - this is SPI that I am referring to.

I was not able to get MII to work and did not spend much time on it.

I was able to determine that multiple resets with binary "apixconfig" of the screen when in the "NO SIGNAL" state would bring it back.

This can be replicated by running commands (usually multiple times):

on -f hu-jacinto apixconfig -t 14 -w 2F 01

Or

on -f hu-jacinto apixconfig -f /etc/apix/hh-apix2-spi-long-out1.conf

Coding values I use are:

CID_APIX_MODE
    apix2
CID_COLOR_DEPTH
    24
CID_COM_MODE
    spi

To make it somewhat permanent I wrote a shell script and baked into the existing "/bin/start_screen.sh" on OMAP. It tracks the status of the screen and resets only as needed. Too many resets and you end up with "NO SIGNAL" also.


I attached my modified "start_screen". Tested with HU 6829104 18-03 and CID 6822626. Also tested with 24-07 I-level.

Obvious disclaimers about bricking things apply...
Would welcome feedback.

 

[zomboi09]

I'm curious whether it will happen again or not?

 

[zomboi09]

I will have to delete the original file in HU with winscp and then replace the post's file there, it should work, right? , thanks

 

[superwofy]

I will have to delete the original file in HU with winscp and then replace the post's file there, it should work, right? , thanks

These are the commands I would use:

mount -uw /fs/sda0 && \
cp /fs/usb0/start_screen.sh /bin/ && \
echo > /net/hu-jacinto/var/opt/sys/APIX_I2C_MONITORING_OFF && \
sleep 5 && \
mount -ur /fs/sda0 && sleep 5

Be careful and remember that you are responsible if you brick it - and this can happen since start_screen.sh is part of the early boot process. You can spam "steuern_rescue_mode", use serial or failing everything, recover the emmc directly.

 

[zomboi09]

Do you have any way to fix WDBI_PLAIN not being able to detect cafd when from id4 flash to id5 6? currently i'm stuck at this step, i can just edit each parameter and then write it down

These are the commands I would use:

mount -uw /fs/sda0 && \
cp /fs/usb0/start_screen.sh /bin/ && \
echo > /net/hu-jacinto/var/opt/sys/APIX_I2C_MONITORING_OFF && \
sleep 5 && \
mount -ur /fs/sda0 && sleep 5

Be careful and remember that you are responsible if you brick it - and this can happen since start_screen.sh is part of the early boot process. You can spam "steuern_rescue_mode", use serial or failing everything, recover the emmc directly.

 

[superwofy]

Do you have any way to fix WDBI_PLAIN not being able to detect cafd when from id4 flash to id5 6? currently i'm stuck at this step, i can just edit each parameter and then write it down

No, never encountered that, sorry.

 

[Euroaddicts8]

Hi

I did ran this problem exactly. I have hu hw 2.3. Flash using 18-03 btld. Using either apix1 or apix2 , always shows no signal

How to run this command sir ? Directly in ssh ( putty ) ?

I need your help to solve this problem. Thank you so much

 

[superwofy]

I've lived with it for a few months and thought I'd share the updates I made to it. Before it took a few seconds for the NO SIGNAL message to disappear. Now it doesn't appear anymore.

I'm currently using this script on 24-07 but it's the same for all ilevels I've seen.

I have not been able to make "MII" work or to make it permanent on the Jacinto side. Perhaps it would work with an old ifs from ID4. I have dumps but I'm not very motivated to try that sort of fix since this works so well.



P.S, if you're modifying the script I highly recommend running "echo > /var/opt/sys/wdgprobeoff" to disable the watchdog first.