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

Internal Error 0x50 Gettext .c

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 . 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 , May take a day or so before I know for sure the results. If you do get it to compile and get i2c working , can you post your kernel / modules ? http://mttags.com/internal-error/internal-error-0x50-hp-1415.php

They will be a bit different in the quad version. /arch/arm/mach-mx6/board-mx6sdl_seco_UDOO.h Line 0127: static iomux_v3_cfg_t mx6sdl_seco_UDOO_pads[] = { Line 0345: MX6DL_PAD_EIM_D28__GPIO_3_28 Line 0346: // MX6DL_PAD_EIM_D28__GPIO_I2C1_SCL Line 0347: MX6DL_PAD_EIM_D21__GPIO_3_21 Line 0348: // What kernel are you using ? Edit: the goofy board software here doesn't allow upload of files with a *.h or *.c extension! Normally something like that would cause errors during the compile attempt, though. http://h30434.www3.hp.com/t5/Printer-Software-and-Drivers/PCL-XL-error-LaserJetPro-CM1415fnw/td-p/1066289

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 The Arduino HFP compiles on Debian Wheezy but still flashes some errors. I think I may have missing some obvious steps like cd - ing into the directory . Total pages: 256000 [ 0.000000] Kernel command line: console=ttymxc1,115200 root=/dev/sda1 fbmem=24M video=mxcfb0:dev=hdmi,[email protected],b pp=32 [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries:

  • The sam side works ( wire and wire1 ), but is missing parts of the library ,eg the ack don`t work.
  • 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
  • Mine is $ gcc -v Using built-in specs.

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. Wonder if this is significant? In my original recompile all I did was comment out lines 0480 and 0481. I followed the steps in the manual to remark the relevant GPIO pins and recompile the kernel.

I can only wonder if the udoo team have every tried to see if it does really work ? For the last bit I`ve been using the LVDS socket method which I know is temporary , but does work quite well. The left pane is the the "before" changes are made and the right pane is the "after" changes are made. look at this web-site No, create an account now.

I'm still running 3.0.35, checked out from the git repository back in March or so... 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. 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 I think I just did 'make -j4 uImage && make -j4 modules && make modules_install'.

another fact which I don`t know if it`s involved is that I`m running headless via ssh and its booting off sata. Preferrably python with smbus but would be happy to see it work on C++. 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 The line numbers below refer to the dual file.

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 ... http://mttags.com/internal-error/internal-error-0x50-hp-1536.php I have 1.1 sitting on another SD card, but had postponed upgrading to it since so many customizations need to be moved over. From my records this is what I did to compile the kernel just I case I`m using the wrong method. 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.

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 My goal is to use i2c on the J5 pins 1/2 (labled 20/21 on the board) with the imx6 processor. I'll try putting them in a ZIP ... http://mttags.com/internal-error/internal-error-0x50-hp-printer.php [email protected]:/mnt/kernel# gcc -v Using built-in specs.

Interestingly I still cannot get the SAM3 J21 SDA/SCL pins to talk on i2c via the Arduino Wire library. I did some digging in the kernel source code and wish to call attention to a few lines. fetcher, Jun 9, 2014 #32 peter247 New Member Joined: Mar 10, 2014 Messages: 263 Likes Received: 0 Re: getting i2c_1 working I think my udoo hates me.

I keep downloading a new copy of the kernel source tree.

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, 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 However I did get i2c working on J5 pins 20/21 on SAM3 using Arduino Wire library. Also, if possible, create a second and very simple (minimized) installation SD-Card based on debian or ubuntu-core and try again.

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). After working with some smaller ARM boards, it feels kind of luxurious to have one that can host its own development toolchain. 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 news Lastly I programmed the SAM3 via Arduino to look for activity on the J5 pins 1/2 ports.

Stay logged in UDOO Forum Forums > Operating Systems & Applications > Kernels > Discover Get Started NEO Get Started QUAD/DUAL UDOO NEO UDOO QUAD/DUAL Community Blog Forum Resources Docs NEO 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 ... To date I have not been able to see any activity in this configuration. I missed something, reread the manual, and gained some understanding.

Yes, my password is: Forgot your password? modules_install I compiled the kernel native , did you do it cross platform ? The manual portion I am referring to is Chapter 6 i.mx6 Pin Muxing. 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 am going to change some lines (specified below) and recompile the kernel. So basically what I have is activity on the targeted pins but processed via SAM3 rather than desired imx6. 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 peter247, Jun 9, 2014 #31 fetcher Member Joined: Mar 9, 2014 Messages: 136 Likes Received: 2 Re: getting i2c_1 working I built my kernel directly on the Udoo also.

At present I am unconcerned with the LVDS and HDMI i2c ports. I know it never going to work on my system now.