From mboxrd@z Thu Jan 1 00:00:00 1970 From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni) Date: Thu, 16 Jul 2015 17:14:48 +0200 Subject: Linux on Armada 370 In-Reply-To: References: Message-ID: <20150716171448.59eb45e5@free-electrons.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hello, On Thu, 16 Jul 2015 01:24:59 +0300, Constantine Shulyupin wrote: > I want to run the mainstream Linux on Armada 370 and then contribute to it. > > I use custom board derived from DB-88F6710-BP > Now I successfully run Marvell's linux-3.2.54-2014_T1.1 with u-boot > "Marvell version: v2011.12 2013_Q1.0p2" > U-boot and Linux are patched by our OEM according HW changes. > > I unsuccessfully tried to to run linux-4.2 with armada-370-db.dts. > > Can you please tell me, were can I find the latest Linux, which runs > on Armada 370? > What is proper configuration etc? Most likely you're hitting the internal register issue. Can you make sure you have either an A0 or B0 stepping or the 370 (it's shown in the U-Boot messages at boot), and then check whether your internal registers are at 0xd0000000 or 0xf1000000. To achieve this, please run: md 0xd0020080 md 0xf1020080 One of the two may crash the system. If the first command returns 0xd0000000, then your internal registers are at that location. If the second command returns 0xf1000000, then your internal registers are at that location. I suspect that you might be using an old U-Boot that still maps registers at 0xd0000000. You have two choices: 1/ Update your U-Boot. This is the best option obviously. An updated U-Boot is available for the Armada 370 DB. 2/ Change the kernel armada-370-db.dts to use the internal registers at 0xd0000000. Basically, you can revert commit 4f054d445139d63868f931328f897ac5ef87242e. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com