AR6000: Set async interrupt delay clock as 2. EXT4-fs (mmcblk2p12): Ignoring removed nomblk_io_submit option Console: switching to colour dummy device 80x25 watchdogd: watchdogd started (interval 10, margin 20)! audit: type=1400 audit(1545213107.196:4): avc: denied for pid=1 comm="init" capability=2 scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=capability permissive=0 PID hash table entries: 4096 (order: 3, 32768 bytes) device-mapper: init: will configure 1 devices Built 1 zonelists, mobility grouping on. Speculative Store Bypass Disable mitigation not required CPU features: enabling workaround for ARM erratum 845719 random: get_random_bytes called from start_kernel+0xa8/0x414 with crng_init=0 psci: Using standard PSCI v0.2 function IDs psci: probing for conduit method from DT. *** Warning - bad CRC, using default environment
ADVANCED MCE REMOTE MAPPER TOOL LOAD MC ANDROID
There seems to be a problem with this pre-built Android image.ĬPU: Freescale i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz)ĬPU: Commercial temperature grade (0C to 95C) at 55C It behaves a similar way and it didn't boot either.
ADVANCED MCE REMOTE MAPPER TOOL LOAD MC SERIAL
I also downloaded a new Android image (android_p9.0.0_1.0.0-ga_image_) and I downloaded it to the board using serial download tool. According to serial terminal they tried to start Android, but booting fails and board reboots itself after a while. I received this week two 8MMINILPD4-EVK kits and both of them are not booting to Android out of the box.
0 kommentar(er)
