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

Internal Error 0x50 Gettext .c

Could you catch any specifics from the kernel panic, maybe by logging serial console output? What kernel are you using ? I followed the steps in the manual to remark the relevant GPIO pins and recompile the kernel. I did some digging in the kernel source code and wish to call attention to a few lines. news

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 I also downloaded i2c-tools. I have 1.1 sitting on another SD card, but had postponed upgrading to it since so many customizations need to be moved over. 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 =>

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 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 Normally something like that would cause errors during the compile attempt, though. The manual portion I am referring to is Chapter 6 i.mx6 Pin Muxing.

What output does 'gcc -v' give? 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 The line numbers below refer to the dual file. My next step is to recompile the kernel on Debian Wheezy to disable the GPIOs on JP5 pins 1/2.

May take a day or so before I know for sure the results. 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 My goal is to use i2c on the J5 pins 1/2 (labled 20/21 on the board) with the imx6 processor. modules_install I compiled the kernel native , did you do it cross platform ?

Nor .txt, on renaming them to that... I`ve tried again still kernel panic with your files ... , I added the arch = arm after it didn`t boot , So that was a try it and see . Simple test code to Serial executes properly. I understand what I should be gone from the manual , but there is something clearly wrong when you try it.

  • The sam side works ( wire and wire1 ), but is missing parts of the library ,eg the ack don`t work.
  • I missed something, reread the manual, and gained some understanding.
  • After working with some smaller ARM boards, it feels kind of luxurious to have one that can host its own development toolchain.
  • As a phrase goes , tried that , gone that , all I got was a kernel panic and I non booting system !!!!!
  • 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
  • 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...
  • No, create an account now.
  • Code: Starting kernel ... [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.0.35-g6559a52-dirty ([email protected]) (gcc version 4.8.2 (Debian 4.8.2-16) ) #1 SMP PREEM PT Tue Jun 10 12:20:04 BST

I keep downloading a new copy of the kernel source tree. https://android.googlesource.com/platform/system/core/+/be61f39a6b3b92fd6f0a9d1e732f59fa08e95da6%5E2..be61f39a6b3b92fd6f0a9d1e732f59fa08e95da6/ I do not see any activity on this port with the Wire1 commands. I think I just did 'make -j4 uImage && make -j4 modules && make modules_install'. 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

larryhartman50, Jun 6, 2014 #22 peter247 New Member Joined: Mar 10, 2014 Messages: 263 Likes Received: 0 Re: getting i2c_1 working My support ticket is now a month ago without reply, navigate to this website Curious has anyone determined if these issues exist on Android variant? This was done using Linaro Beta. Wonder if this is significant?

I'll try to attach my board-mx6qd_seco_UDOO.h and board-mx6_seco_UDOO.c files, in case those are of any help. The left pane is the the "before" changes are made and the right pane is the "after" changes are made. maybe that will pacify the silly thing. http://colvertgroup.com/internal-error/internal-error-0x50-hp-1415.php 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.

Good luck Tom TomFreudenberg, Jun 10, 2014 #34 fetcher Member Joined: Mar 9, 2014 Messages: 136 Likes Received: 2 Re: getting i2c_1 working I'd go with Tom's suggestion also. peter247, Jun 10, 2014 #38 fetcher Member Joined: Mar 9, 2014 Messages: 136 Likes Received: 2 Re: getting i2c_1 working Ah, I'm still on the 1.0 release. fetcher, Jun 10, 2014 #39 peter247 New Member Joined: Mar 10, 2014 Messages: 263 Likes Received: 0 Re: getting i2c_1 working I`m going to start with a fresh sd version of

I am going to change some lines (specified below) and recompile the kernel.

I know it works if I don`t make any changes to the board-mx6qd_seco_UDOO.h file , so what I`m trying now so edit the board-mx6qd_seco_UDOO.h file without making any real changes , I can only wonder if the udoo team have every tried to see if it does really work ? 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=.. Mine is $ gcc -v Using built-in specs.

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 The coding example provided (for changing UART pins) with a left pane and right pane is not easy to read due to tab spacing and formatting. I will check back here every couple of days to lend assistance where I can. click site when I did a dry run kernel without any changes I didn`t had any problem , but after changing the pads , no boot kernel panic ...

[email protected]:/mnt/kernel# gcc -v Using built-in specs. For the last bit I`ve been using the LVDS socket method which I know is temporary , but does work quite well. 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). However I did get i2c working on J5 pins 20/21 on SAM3 using Arduino Wire library.

Next I programmed the SAM3 via Arduino to look for activity on the SCL/SDA ports. 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 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