Bug#706735: installation-reports: [armhf] Installing an i.MX53 loco
On Thu, Dec 10, 2015 at 02:29:12PM -0800, Martin Michlmayr wrote:
> * Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de> [1970-01-01 01:46]:
> > Image version: http://ftp.de.debian.org/debian/dists/wheezy/main/installer-armhf/current/images/mx5/netboot/efikamx/uI{mage,nitrd}
> > Date: 2013-05-03
> >
> > Machine: Freescale i.MX53 LOCO
> >
> > Comments/Problems:
> >
> > * I booted the efika kernel+initrd on my Loco board. I had to overwrite the
> > uImage's load address because the i.MX53 on the Loco doesn't have RAM at
> > 0x90000000.
> > * I didn't test it (because I don't have physical access to the system) but
> > I think the automatic installation would have overwritten the boot loader.
> > But I admit it's hard to detect where the bootloader is.
> > * With the original uInitrd the installer fails to select a kernel to install.
> > The patch for http://bugs.debian.org/706643 fixes that though.
> > * Again with the original uInitrd one of the last dialogs tells:
> > You will need to boot manually with the kernel on partition
> > /dev/mmcblk1p1 and root=/dev/mmcblk1p2 passed as a kernel argument.
> > This is wrong, because there was no kernel installed.
> > * I installed via a serial connection (on ttymxc0). It would have been nice
> > if the installed system had a getty running on that serial line.
> >
> > Other than that I'm very satisfied with the overall installation.
>
> I just saw your install report from 2013 that nobody responded to.
>
> I hope all of these issues have been addressed. I've copied Karsten
> Merker who might know.
I don't have access to an i.MX53 LOCO board, so I cannot test
that, but I think that all points above should have been
addressed in the meantime:
- The i.MX53 LOCO is nowadays supported by the armmp kernel; the
old platform-specific MX5 kernel isn't used anymore.
Flash-kernel nowadays generates a uImage for the i.MX53 LOCO
with the proper load address (0x70008000).
- Kernel selection should work without problems; with support in
the multiplatform kernel there is no need to determine a
board-specific subarch anymore.
- Regarding the getty: as long as the system is booted with
"console=ttymxc0,115200", systemd should automatically spawn a
getty there.
HTH,
Karsten
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Reply to: