2019-12-03 08:41 AM
Hello,
Could you explain the reason why Android is not supported on the STM32MP157C-DK2?
I can't find any instructions how to install an Android image on the target? The following example references the coprocessor example for A7 and M4 cores, but misses how this is done:-
https://wiki.st.com/stm32mpu/wiki/STM32MP1_Developer_Package_for_Android
2019-12-03 08:49 AM
Hi @moredatalesscenter
Android does not fit to DK2 because there is not enough DDR ( 1GB required) .
Guideline to install Android on target is there :
https://wiki.st.com/stm32mpu/wiki/How_to_populate_boards_for_Android
Olivier
2019-12-03 08:52 AM
Ah. The board features suggest it's 4 Gbit DDR3L, 16 bits.
2019-12-03 08:54 AM
Indeed ..which mean 512MBytes. ;)
2019-12-05 02:21 AM
Can packages be selectively removed to create a barebones distribution that will fit into 0.5GB?
2019-12-05 06:35 AM
Android from AOSP can work with 512MBytes but with an impact on the overall performance (swap has a huge impact).
It's then required to limit the memory usage to the maximum:
1- limit the display resolution on the device
2- limit the number of packages started (remove all unnecessary packages which can means patching the system server to avoid starting them (ex: Telecom))
3- applications (packages) including the Launcher shall be developed considering memory usage (no animation, simple layouts (ex: use ConstrainLayout), avoid too much activity swap...)
At the end, it depends on the kind of device targeted (ex: wear device with small screen can work easily with 512MBytes DDR)