From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-eopbgr780104.outbound.protection.outlook.com ([40.107.78.104] helo=NAM03-BY2-obe.outbound.protection.outlook.com) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hLmXl-0003XU-Fm for barebox@lists.infradead.org; Wed, 01 May 2019 10:32:55 +0000 From: "Barbier, Renaud" Date: Wed, 1 May 2019 10:32:47 +0000 Message-ID: Content-Language: en-US MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: cortex-a9 boot issue To: "barebox@lists.infradead.org" I have added support for a cortex-a9 off the master branch. I am seeing an issue to boot to the prompt found in the function hyp_install. The assembly code is as follows: mrs r12, cpsr and r12, r12, #MODE_MASK @ Save the initial CPU state adr r0, .L__boot_cpu_mode_offset ldr r1, [r0] str r12, [r0, r1] ===> I get an exception here because the register r12 is being written to [r0 + r1] which points to the SPI NOR boot flash. Commenting out the call to all functions calling hyp_install, barebox does get to the prompt. Is there something I could be missing that would put the __boot_cpu_mode variable in a writable area? Cheers, Renaud _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox