AM335x Boot Device 6 (NAND?)
Hi Tom,
we have equipped some of our am335x boards (draco from mainline U-Boot) with NAND devices from Hynix. And as it seems, the BootROM passes now a different bootdevice number to SPL. Its not 5 as it used to be for NAND but 6 instead. So SPL hangs of course as this boot-device is not "supported".
Could you please let me know what this boot-device == 6 means / represents? Should it be handled identical as the "normal" NAND boot-device (5)?
Just to make this clear. This is the code that I'm referring to:
arch/arm/cpu/armv7/omap-common/boot-common.c:
/* * rom_params can be type casted to omap_boot_parameters and * used. But it not correct to assume that romcode structure * encoding would be same as u-boot. So use the defined offsets. */ gd->arch.omap_boot_params.omap_bootdevice = boot_device = *((u8 *)(rom_params + BOOT_DEVICE_OFFSET));
BTW: U-Boot can handle this Hynix NAND (same layout as the other NAND chips we use) without any problems.
Thanks,
Stefan
Quoted 11 lines · Stefan Roese
Hi Tom,
we have equipped some of our am335x boards (draco from mainline U-Boot) with NAND devices from Hynix. And as it seems, the BootROM passes now a different bootdevice number to SPL. Its not 5 as it used to be for NAND but 6 instead. So SPL hangs of course as this boot-device is not "supported".
Could you please let me know what this boot-device == 6 means / represents? Should it be handled identical as the "normal" NAND boot-device (5)?
Well, my guess is that you've wired it up, or at least selected SYSBOOT pins saying that this is a "NAND+I2C" device where the geometry is stored on an i2c eeprom (see 26.1.7.4 of the TRM). Is this really what you wanted is my first question. :)
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141111/685b6385/attachment.pgp>