+# Flattened Device Tree blob at 2eff8a00 +Failed to load 'isatech-images/latest/boot.scr' +Model: Raspberry Pi Compute Module 3 Rev 1.0 Gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined +Loading 'u-boot.bin' to 0x80000 size 0x7ce20ĭevice tree loaded to 0x2eff8a00 (size 0x75f9) Gpioman: gpioman_get_pin_num: pin WL_ON not defined I can't make out any meaningful differences.Īt the very end It is visible how i2c-detect -l yields for the direct bootīoot.scr: if test "$ images/factory/boot.scr Lastly I recorded the boot process in both cases and constructed a diff. I use a first stage bootscript to source the actual boot.scr as part of a fallback system. Here only the kernel= line changes accordingly.įurthermore I have posted my boot script. In both cases i2c_dev module is loaded and I can't see any big differences. If the kernel is booted directly ( kernel=Image) everything is working like intended. But if the kernel is booted through U-Boot there is no I2C bus available. Meanwhile I googeled for "ll_entry_count" which specifies " returns the number of elements in the linker generated array" and I am not sure what is linker generated array.Īnd so I cannot guess what is the cause of this error.I'm building a custom linux with buildroot in combination with U-Boot on compute module 3(+).
So I wonder how the "max" variable differs in these two cases. This function is called from "arch/arm/lib/board.c" which is common to both sabrelite and sabresd and I guess no board specific confgiuration with respect to i2c is made before that function call. I put some debug messages there and found that the variable "max" is set to 0 in case of sabresd, but in the case of sabrelite it is 3.
Printf("Error, wrong i2c adapter %d max %d possible\n", Max = ll_entry_count(struct i2c_adapter, i2c) And i guess that the error we saw in the boot log is thrown from the file "drivers/i2c/i2c_core.c", in the function "i2c_set_bus_num()", line I took m圆qsabrelite in 2014.01 as reference (where i2c is working fine in sabrelite baord) and looked at it. Do I need any other configuration for "i2c" command to work properly? R3 : 00000083 r2 : 00000060 r1 : 00000000 r0 : 00000000įlags: nZCv IRQs off FIQs off Mode SVC_32Īs you can see, when I try for "i2c probe", the board is reset with "Error, wrong i2c adapter 0 max 0 possible" error message. MAYBE you should read doc/README.arm-unaligned-accesses Valid chip addresses:Error, wrong i2c adapter 0 max 0 possible *** Warning - bad CRC, using default environmentĮrror, wrong i2c adapter 0 max 0 possible MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2 I2C: Error, wrong i2c adapter 0 max 0 possible #define CONFIG_SYS_I2C_PORT I2C2_BASE_ADDRĪnd with this settings, I got the u-boot prompt with i2c command but it is not working properly.
ADDING I2C U BOOT COMMANDS CODE
For this, I added these lines in "include/configs/m圆sabresd.h" file (I referred LTIB BSP u-boot code which is 2009.08 version ) And I tried to bring up the "i2c" command.
But there is no "i2c" command by default. I am using sabresd with 2014.01 u-boot ("m圆qsabresd_config" configuration) and I got the u-boot prompt on the board.
0 kommentar(er)
