Home > Internal Error > Internal Error 0x50 Gettext .c

Internal Error 0x50 Gettext .c

peter247, Jun 10, 2014 #33 TomFreudenberg Member Joined: May 12, 2014 Messages: 56 Likes Received: 2 Re: getting i2c_1 working Hi Peter, maybe you should completly drop the src files and For the last bit I`ve been using the LVDS socket method which I know is temporary , but does work quite well. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.8/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../src/configure -v --with-pkgversion='Debian 4.8.2-16' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --disable-libitm --disable-libquadmath --enable-plugin After working with some smaller ARM boards, it feels kind of luxurious to have one that can host its own development toolchain. check over here

I`ve tried that :- My next step is to recompile the kernel on Debian Wheezy to disable the GPIOs on JP5 pins 1/2.Click to expand... From my records this is what I did to compile the kernel just I case I`m using the wrong method. I also downloaded i2c-tools. In my original recompile all I did was comment out lines 0480 and 0481.

Additionally the input mode of the original GPIOs must be disabled in the array mx6dl_set_in_inputmode[] by commenting out those lines (0480 and 0481). and not just a copy of the chip manufactures work without any understanding. fetcher, Jun 10, 2014 #35 peter247 New Member Joined: Mar 10, 2014 Messages: 263 Likes Received: 0 Re: getting i2c_1 working It does seem like something might have become corrupted in COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.6/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../src/configure -v --with-pkgversion='Debian 4.6.3-14' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --disable-sjlj-exceptions

Nor .txt, on renaming them to that... What output does 'gcc -v' give? Please note the lines that are labeled as "not set." These have my attention for the moment as potential sources of the problem. /arch/arm/configs/UDOO_defconfig Line 0277: CONFIG_IMX_HAVE_PLATFORM_IMX_I2C=y Line 1462: CONFIG_I2C=y Line All edits should be marked with a "// jnh" comment.

I am going to change some lines (specified below) and recompile the kernel. peter247, Jun 9, 2014 #29 fetcher Member Joined: Mar 9, 2014 Messages: 136 Likes Received: 2 Re: getting i2c_1 working peter247 said: I will have to try and compile the kernel Simple test code to Serial executes properly. http://www.udoo.org/forum/threads/solved-ish-getting-i2c_1-working.1380/page-2 The manual portion I am referring to is Chapter 6 i.mx6 Pin Muxing.

I think I just did 'make -j4 uImage && make -j4 modules && make modules_install'. It seems the folks who posted the first two posts may have missed what I missed. However I did get i2c working on J5 pins 20/21 on SAM3 using Arduino Wire library. The line numbers below refer to the dual file.

peter247, Jun 10, 2014 #40 (You must log in or sign up to reply here.) Show Ignored Content Page 2 of 3 < Prev 1 2 3 Next > Share This https://android.googlesource.com/platform/system/core/+/be61f39a6b3b92fd6f0a9d1e732f59fa08e95da6%5E2..be61f39a6b3b92fd6f0a9d1e732f59fa08e95da6/ To date I have not been able to see any activity in this configuration. I can only wonder if the udoo team have every tried to see if it does really work ? Next I programmed the SAM3 via Arduino to look for activity on the SCL/SDA ports.

Log in or Sign up UDOO Forum Forums > Operating Systems & Applications > Kernels > SOLVED-ish - getting i2c_1 working Discussion in 'Kernels' started by peter247, May 8, check my blog I'll try putting them in a ZIP ... So basically what I have is activity on the targeted pins but processed via SAM3 rather than desired imx6. I keep downloading a new copy of the kernel source tree.

This was done using Linaro Beta. Ekirei test [ 0.777811] failed to get MX6_SECO_UDOO_LVDS_BLT_CTRL: -16 [ 0.783341] failed to get MX6_SECO_UDOO_LVDS_PNL_CTRL: -16 [ 0.794986] Resetting ethernet physical layer. [ 0.837766] hw-breakpoint: found 6 breakpoint and 1 watchpoint peter247, Jun 8, 2014 #26 larryhartman50 New Member Joined: Jun 6, 2014 Messages: 6 Likes Received: 0 Re: getting i2c_1 working Peter, I am happy to report success on Linaro Beta this content apt-get install build-essential libncurses5-dev apt-get install git apt-get install uboot-mkimage git clone https://github.com/UDOOboard/Kernel_Unico kernel make ARCH=arm UDOO_defconfig make menuconfig make -j4 ARCH=arm uImage modules make -j4 ARCH=arm INSTALL_MOD_PATH=..

Curious has anyone determined if these issues exist on Android variant? AboutTeam Press Review Press and Media Privacy SupportForum FAQ Customer Care Contact Us ResourcesDocs Tutorials Download Images Other Resources Made with ❤ in Italy Copyright© 2016 SECO USA Inc | 111 I conducted a successful test on i2c0 with i2cdetect and was able to access the port write data to it and read it back using python smbus(0).

As a phrase goes , tried that , gone that , all I got was a kernel panic and I non booting system !!!!!

Edit: the goofy board software here doesn't allow upload of files with a *.h or *.c extension! fetcher, Jun 9, 2014 #28 peter247 New Member Joined: Mar 10, 2014 Messages: 263 Likes Received: 0 Re: getting i2c_1 working I will have to try and compile the kernel again Interestingly I still cannot get the SAM3 J21 SDA/SCL pins to talk on i2c via the Arduino Wire library. Looking at your command sequence, I did nearly the same thing except for copying the default config manually (cp arch/arm/configs/UDOO_defconfig .config from kernel-tree root), and I didn't specify ARCH=arm to any

These contain other changes unrelated to I2C, like enabling all UARTS, SDHC1 (secondary SD card), exporting some GPIOs not brought out to pin headers, and reducing reserved GPU memory to 16MB Maybe I should take them out to remove the unusable /sys/class/gpio/gpio85 and gpio92 ('unexporting' those from userland would work too), but those aren't interfering, especially being set as inputs (and the I think I may have missing some obvious steps like cd - ing into the directory . have a peek at these guys Page 2 of 3 < Prev 1 2 3 Next > TomFreudenberg Member Joined: May 12, 2014 Messages: 56 Likes Received: 2 Re: getting i2c_1 working J21 PIN 9/10 - SCL1/SDA1

ONLY WHEN ENABLED IN KERNEL HDMI CN8 - KEY_COL3/ROW3 - I2C2 SCL/SDA - iMX6 ONLY => smbus(1) CN13 PIN 12/19 - CN11 PIN 11/15 - I2C3 SCL/SDA - iMX6 ONLY => Code: MX6Q_PAD_CSI0_DAT13__GPIO_5_31, // pin 19 // MX6Q_PAD_CSI0_DAT13__UART4_RXD, // MX6Q_PAD_EIM_D28__GPIO_3_28, // pin 20 MX6Q_PAD_EIM_D28__I2C1_SDA, // MX6Q_PAD_EIM_D21__GPIO_3_21, // pin 21 MX6Q_PAD_EIM_D21__I2C1_SCL, // MX6Q_PAD_EIM_D21__SPDIF_IN1, MX6Q_PAD_DISP0_DAT6__GPIO_4_27, // pin 22 MX6Q_PAD_DISP0_DAT7__GPIO_4_28, // pin 23 I guess I will redo this the correct way and report back the outcome. those text files are apparently too dangerous!

peter247, Jun 6, 2014 #23 larryhartman50 New Member Joined: Jun 6, 2014 Messages: 6 Likes Received: 0 Re: getting i2c_1 working My Debian Wheezy compile worked ok but no joy on [email protected]:/mnt/kernel# gcc -v Using built-in specs. larryhartman50, Jun 8, 2014 #25 peter247 New Member Joined: Mar 10, 2014 Messages: 263 Likes Received: 0 Re: getting i2c_1 working I think there is a fault somewhere in the kernel modules_install I compiled the kernel native , did you do it cross platform ?

I can send and receive i2c data with the Wire commands. Attached Files: udoo-kernel-files.zip File size: 12.9 KB Views: 13 fetcher, Jun 9, 2014 #30 peter247 New Member Joined: Mar 10, 2014 Messages: 263 Likes Received: 0 Re: getting i2c_1 working Thanks There's also no need to mess with the MX6{Q,DL}_PAD_EIM_D2*__GPIO_MODE lines in the *UDOO.h file-- those are still set at their defaults on my board, and aren't interfering with I2C function.