2017-01-03 14:33 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>:
> One reason why I2C configuration is wrong in nand mode could be the fact > that I have CONFIG_TI_I2C_BOARD_DETECT variable is undefined (because I do > not have that eeprom). But it looks that do_board_detect runs > enable_i2c0_pin_mux() that I do not run separately. On the other hand, that > does not explain why mmc boot works. Now I did this I2C0 configuration separately prior to running i2c_probe(). Nand boot went further now. However, main u-boot did not start properly. I got following messages Trying to boot from NAND The Expected Linux image was not found. Please check your NAND configuration. Trying to start u-boot now... ........ more messages .... Press SPACE to abort autoboot in 2 seconds Card did not respond to voltage select! Card did not respond to voltage select! Card did not respond to voltage select! Card did not respond to voltage select! Card did not respond to voltage select! data abort pc : [<8ff70f94>] lr : [<8ff701dd>] reloc pc : [<8081df94>] lr : [<8081d1dd>] sp : 8ef28678 ip : 8ff5891d fp : 00000003 r10: 8ffb3af8 r9 : 8ef32ed8 r8 : 8ef41e40 r7 : 8ff584bd r6 : 8ef39478 r5 : 8ef39500 r4 : 47810000 r3 : 8ff70f85 r2 : 00000d8d r1 : 00000000 r0 : 8ef39500 Flags: nZCv IRQs off FIQs on Mode SVC_32 Resetting CPU ... resetting ... And game over.... So, it's not quite sure that voltage adjustments went through even though I2C did not complain anymore. There could be something wrong with nand settings, too. I need to check where these complaints are coming. Thanks anyway for your comments, Matti _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
