I guess you have to set that set of commands each time. In that case, you haven't created boot.scr. Do following: - create a file (e.g. boot.script) containing those boot commands, - use following command to generate boot.scr: mkimage -A arm -T script -C none -n "My Boot.scr" -d PATH_TO_BOOT_SCRIPT/boot.script /PATH_WHERE_YOU_WANT_IT_GENERATED/boot.scr - copy boot.scr to the root of your UDOO - in u-boot, check if environment variable "script" is set to "boot.scr" It should boot now.
Thank you very much for your help. You were right, it was the "HDMI to DVI" adapter. With "HDMI to VGA" I finally got output. I tried two 19" LCD monitors and it basically works with both but only in resolution 640x480. I tried to change frame buffer settings to support 800x600 or 1024x768 resolution but that didn't work. Do you have any idea why? What I tried is following: fbset -g 800 600 800 600 32. After I do that, I get black screen If I return it to 640x480, I get the output again. Do you know what changes are needed in order to support other resolutions? I also tried to change boot command but it always runs in 640x480 no matter what I set in the kernel boot command. In return for your help (I don't have anything else to offer), here is a nice joke I heard this morning: Why was 6 afraid of 7? Because 7 ate 9
It reverts to 640x480 because there was no EDID values detected, some HDMI to VGA adapters require additional power to make them work correcty. Did you try adding the resolution to boot.scr, if yes can you pastebin the uboot/kernel output.
Hi jas-mx, I tried to give it additional power (via USB) but that didn't help. Please find attached uboot_kernel_output.zip. You will see there that I tried to set (manually) 800x600 resolution in u-boot. Thanks, Ivan
You are setting the resolution for fb1 NOT fb0 in your uboot script: Code: video=mxcfb1:dev=hdmi,800x600M@60,bpp=32 It should be: Code: video=mxcfb0:dev=hdmi,800x600M@60,bpp=32 BTW next time can you provide a dump via pastebin.
Are you considering working on 3.14 as well? Is this dts-file required? Because on my ubuntu-for-udoo-image there's no dts file to be found. The 2013uboot is probably integrated in ubuntu 12.04 v2.1 right?
Not at the moment. For later kernel releases dts file(s) are required as they replace the inconsistency of creating "board specific files" for every ARM device. Not sure because I have not deployed/used it. If you have serial console output then you can easily verify because the uboot version is displayed.
Has anyone been able to access the udoo camera on this kernel, I loaded the modules but for the life of me I can't create a device node for it.
Thats because the MIPI interface is not configured in the dts file, if you know what your doing then you can try configuring it to the dts file. As I don't own any of the official UDOO peripherals hence can't test, I haven't configured them in the dts.
I can try and get my hands dirty, tho I doubt it's as easy as getting the configuration from the sabre/nitrogen or wandboard and it would just work on the udoo. Need to do some reading on dts and i2c. Any pointers?
Hi, jas-mx Great work, I am very interested in this debian distribution with support for camera (well i'm on computer vision projects with embedded boards), in udooDebianarmhf I have installed opencv but no usb webcamera works ("I think the driver") I dont know why??. I'm try installing with the steps from this tutorial but it didn't work (for me ), so I follow this instructions, next I will try to install opencv and if i have success I will upload instructions first install some dependencies: Code: sudo apt-get install git build-essential wget u-boot-tools zlib1g-dev ncurses-dev cmake gcc-arm-linux-gnueabihf libc-dev-armhf-cross g++-arm-linux-gnueabihf pkg-config-arm-linux-gnueabihf build-essential checkinstall cmake pkg-config lzop 1. linux kernel deploy workpath ~/ or better your workpath Code: git clone git://github.com/mtx512/linux-imx.git cd linux-imx git checkout -b imx_3.10.17_1.0.0_beta-udoo origin/imx_3.10.17_1.0.0_beta-udoo make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- udoo_defconfig make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- dtbs make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- -j4 uImage LOADADDR=0x12000000 make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- INSTALL_MOD_PATH=output modules make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- INSTALL_MOD_PATH=output modules_install 2. Build Uboot and deploy to SD card. ~/ Code: git clone git://git.denx.de/u-boot.git cd u-boot/ git checkout v2014.04 -b tmp patch Code: wget -c https://raw.github.com/eewiki/u-boot-patches/master/v2014.04/0001-udoo-uEnv.txt-bootz-n-fixes.patch patch -p1 < 0001-udoo-uEnv.txt-bootz-n-fixes.patch make Code: make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- distclean make CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- udoo_quad_config make CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- Setup microSD/SD card , Erase microSD/SD card, Install Bootloader: ~/u-boot/ (is good to have a formated sdcard) export DISK=/dev/sd* Code: export DISK=/dev/sdb sudo dd if=/dev/zero of=${DISK} bs=1M count=16 sudo dd if=~/u-boot/u-boot.imx of=${DISK} bs=512 seek=2 and Create Partition Layout: Code: sudo sfdisk --in-order --Linux --unit M ${DISK} <<-__EOF__ 1,48,0x83,* ,,,- __EOF__ Format Partitions and Mount Partitions: Code: sudo mkfs.ext2 ${DISK}1 -L boot sudo mkfs.ext4 ${DISK}2 -L rootfs sudo mkdir -p /media/boot/ sudo mkdir -p /media/rootfs/ sudo mount ${DISK}1 /media/boot/ sudo mount ${DISK}2 /media/rootfs/ Create uEnv.txt based bootscript ~/uEnv.txt Code: #optargs= #mmcroot=/dev/mmcblk0p2 ro #mmcrootfstype=ext4 rootwait fixrtc #video= #Quad: fdtfile=imx6q-udoo.dtb #Dual: #fdtfile=imx6dl-udoo.dtb Copy uEnv.txt to the boot partition: Code: sudo cp -v ./uEnv.txt /media/boot/ 3. Extract debian rootfs onto ext4 partition on SD card Code: cd path/to/roofts.tar.gz sudo tar -zxvf ./jessie-3.10.17_beta.tar.gz -C /media/rootfs/ 4. Copy kernel/modules and dts to ext4 parition: Kernel Image: Code: sudo cp -v ./linux-imx/arch/arm/boot/zImage /media/boot/zImage Kernel Device Tree Binaries: Code: sudo mkdir -p /media/boot/dtbs/ sudo cp ./linux-imx/arch/arm/boot/dts/imx6q-udoo.dtb /media/boot/dtbs/ Kernel Modules: Code: sudo cp -r ./linux-imx/output/lib/modules/3.10.17-xxxx /media/rootfs/lib/modules 5. Edit: /etc/fstab Code: sudo nano /media/rootfs/etc/fstab copy: Code: /dev/mmcblk0p2 / auto errors=remount-ro 0 1 /dev/mmcblk0p1 /boot/uboot auto defaults 0 2 6. Edit: /etc/network/interfaces Code: sudo nano /media/rootfs/etc/network/interfaces copy Code: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp 7. Serial Login Code: sudo nano /media/rootfs/etc/inittab copy: Code: T0:23:respawn:/sbin/getty -L ttymxc1 115200p 8. Remove microSD/SD card: Code: sync sudo umount /media/boot sudo umount /media/rootfs references from RobertNelson and jas-mx http://eewiki.net/display/linuxonarm/UDOO viewtopic.php?f=19&t=693
Updated rootfs to 3.10.17 GA release, see original post for link. You need to create a new kernel with my udoo patches from my beta branch.
Hi Jas-mx, I would like to submit a patch to fix the cpufreq_interactive scheduling issue. Probably a race on the notifier chains. To which mailing list should I send the patch. Could you suggest me some. -Anand Moon
Hi there, Do someone have updated the "bossac" driver (Processor part) for this kernel ? See the original one (3.0.35) : https://github.com/UDOOboard/Kernel_Uni ... udoo_ard.c But It cant be used as it is. I tried to adapt it, but i have still some errors while inserting module : Serial debug info : Unknown symbol __gpio_get_value (err 0) udoo_ard: Unknown symbol gpio_free (err 0) udoo_ard: Unknown symbol __gpio_to_irq (err 0) udoo_ard: Unknown symbol gpio_direction_output (err 0) udoo_ard: Unknown symbol gpio_direction_input (err 0) udoo_ard: Unknown symbol __gpio_set_value (err 0) udoo_ard: Unknown symbol gpio_request (err 0) udoo_ard: Unknown symbol __alloc_workqueue_key (err 0) udoo_ard: Unknown symbol local_clock (err 0) udoo_ard: no symbol version for module_layout cmd line error: $ sudo insmod ./misc/udoo_ard.ko [sudo] password for ####: Error: could not insert module ./misc/udoo_ard.ko: Unknown symbol in module Thanks
Hi folks, Could anyone guide me through how to enable the Uart 3 and 5 on this kernel? It appears that it has the Uart 2 and 4 turned on by default (used by the imx chip). In the original UDOO kernel_unico, I would set the proper pins in the board-mx6qd_seco_UDOO.h and .c files. But now I have no clue where I can set the proper pins. I need a newer kernal 3.4+ and two UART pins for the project that I am currently working on. Any help would be appreciate it. Thanks in advance
what are the exact differences between the "Udoo" kernel and the mainline kernel? Am i able to use mainline? (their github repo was setup poorly as a fresh repo instead of a fork, making it hard to tell the exact changes as well as making it hard for the udoo project to keep up-to-date with mainline)
For those who are testing, I am interested to see if the I2C buses work alongside Dallas one-wire library w1-gpio and w1-therm. Seems to be a conflict on the 3.0.35 kernel that causes an error when module w1-gpio is loaded. rPi forums discuss the issue and seems to be resolved on this platform. Larry
You can have a look at my repository: https://github.com/chrta/kernel-udoo/co ... doo_3.0.35 It shows the differences to the freescale kernel 3.0.35. I reworked the initial commit (https://github.com/chrta/kernel-udoo/co ... 5a3a89a32d), so i can see the diff to the freescale kernel 3.0.35.
