Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
APIX2 on EVO HW2.3 ID5/ID6 script fix
05-04-2024, 00:39 AM,
(This post was last modified: 09-04-2024, 23:14 PM by superwofy.)
Post: #1
|
|||
|
|||
APIX2 on EVO HW2.3 ID5/ID6 script fix
I wanted to share something I've been working on and possibly invite some discussion on the topic.
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 knew from here https://www.cartechnology.co.uk/showthre...?tid=36297 that multiple resets in SPI+APIX2 work and started my work here. 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): PHP Code: on -f hu-jacinto apixconfig -t 14 -w 2F 01 Coding values I use are: PHP Code: CID_APIX_MODE 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. It's by no means pretty but it does seem to work. I've still got to investigate if black screen happens. I believe it might and additional tracking should be added. PHP Code: mode_register=$(on -f hu-jacinto apixconfig -t 14 -r 2D) I attached my modified "start_screen". Tested with HU 6829104 18-03 and CID 6822626. Obvious disclaimers about bricking things apply... Would welcome feedback. |