recompile - i2c_1

Discussion in 'Kernels' started by igorvuk, Feb 20, 2015.

  1. igorvuk

    igorvuk New Member

    Joined:
    Feb 17, 2015
    Messages:
    4
    Likes Received:
    0
    Code:
    root@udoobuntu: /usr/src $ uname -a
Linux udoobuntu 3.0.35 #10 SMP PREEMPT Wed Jul 30 18:16:10 CEST 2014 armv7l armv7l armv7l GNU/Linux
    I try to enable i2c_1, but i stuck in kernel

    i folow http://udoo.org/download/files/Document ... 8_2013.pdf steps

    1. Download the latest revision from GitHub:
    git clone http://github.com/UDOOboard/Kernel_Unico kernel

    2. Move inside the folder kernel:
    cd kernel

    3. Set the default kernel configuration for UDOO by running the command:
    make UDOO_defconfig

    Code:
    root@udoobuntu: /usr/src/kernel/kernel $ make UDOO_defconfig
    make: *** No rule to make target `UDOO_defconfig'. Stop.

    what i'm doing wrong ?
     
    igorvuk, Feb 20, 2015
    #1
  2. vpeter

    vpeter Active Member

    Joined:
    Nov 29, 2014
    Messages:
    303
    Likes Received:
    62
    You are not in kernel folder.
     
    vpeter, Feb 20, 2015
    #2
  3. igorvuk

    igorvuk New Member

    Joined:
    Feb 17, 2015
    Messages:
    4
    Likes Received:
    0
    OK, tnx for folder hint.

    but next problem:

    i modify:

    <KERNEL_ROOT>/arch/arm/mach_mx6/board_mx6qd_seco_UDOO.h (QUAD)

    Code:
    		//MX6Q_PAD_EIM_D28__GPIO_3_28,							// pin 20 - LINE 303
	MX6Q_PAD_EIM_D28__I2C1_SDA,
		// MX6Q_PAD_EIM_D21__GPIO_3_21,							// pin 21 - LINE 305
	MX6Q_PAD_EIM_D21__I2C1_SCL,
    Code:
    //	MX6Q_PAD_EIM_D21__GPIO_MODE,   // LINE 422
//	MX6Q_PAD_EIM_D28__GPIO_MODE,   // LINE 423
    recompile kernel and no i2c-1 device at 0x48

    Code:
    root@udoobuntu: ~ $ i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: UU 51 52 53 54 55 56 57 -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
root@udoobuntu: ~ $ i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- 24 -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

    I check across forum and there is no precise HOW-TO for i2c-1 can somebody give a hint ?
     
    igorvuk, Feb 20, 2015
    #3
  4. fetcher

    fetcher Member

    Joined:
    Mar 9, 2014
    Messages:
    166
    Likes Received:
    20
    Linux calls the first i.MX6 bus, the one appearing on pins 20,21 "bus 0" (/dev/i2c-0) even though it's labeled I2C1 in the pinmux definitions. One of those count-from-0-vs-1 things...

    So, 'i2cdetect -y 0' is where your i2c targets should be showing up.

    Are you sure if the 0x48 address? What is that at 0x24? There are no i2c devices using this bus on board the Udoo itself, so if you have only one chip or sensor attached, that's probably it, just appearing at an unexpected/erroneous address.
     
    fetcher, Feb 20, 2015
    #4

Share This Page