Hello, I looked at the docs [1] with no luck.. I would like to use the UART_1 with an external Sensor instead of connecting it to arduino. While using python I can write but not read (the script is working on other boards). What is the meaning of "serial debug" ? Ideas what I am missing ? Thanks! [1] http://udoo.org/docs-neo/Hardware_&_Accessories/Uart_serial.html
Dear Pilif, the serial debug is a communication channel for debugging. The serial debug module for NEO allows you to interface with the serial debug. UART 1 is assigned to A9 by default, so you can't do what you aim. What you have to do instead is recompiling the kernel, then you can do what you aim to do.
Thank you @Andrea Rovai, I guess i have to look and follow at [1] , but what do I have to change to unset/set UART1 ? 2. how can one use UART_6 ? Thanks! [1]http://www.udoo.org/docs-neo/Kernel_Hacking/Compile_the_kernel.html EDIT: following the wiki links and searching through git I guess that I have to edit line 501 in https://github.com/UDOOboard/linux_...b7e45552c/arch/arm/configs/udoo_neo_defconfig which is CONFIG_CMDLINE="noinitrd console=ttymxc0,115200" ? If yes what about line 502 - CONFIG_CMDLINE_FROM_BOOTLOADER=y can I not just add a new console= ttymxcX (in uboot I guess )for example and edit so the values set in line 501?
Use UART6 for external sensor/etc. by enabling it in dtweb (Udoobuntu RC1). But there's a kernel patch to apply, see the following post for details: http://udoo.org/forum/threads/a9-uart6-and-udoobuntu.3196/
Thanks @bander! I saw that and did patch and compile like in http://www.udoo.org/docs-neo/Kernel_Hacking/Compile_the_kernel.html but can you write in two sentences what do I have to do next I mean now I have a binary but do I only have to put it in the /boot what about the folder Modules ? Thanks
Good. Sounds like you are almost there. * arch/arm/boot/zImage from the build goes in /boot (there's already a zImage that you probably want to backup, in case you need to go back). * Then, yes, you also need to copy over the modules directory to /lib/modules, which has to match the running kernel version exactly ('uname -r'). Use tar, for example: 'cd modulesdir/lib/modules && tar -cf 3.14.56-g3fa3d71-modules.tar 3.14.56-g3fa3d71', when INSTALL_MOD_PATH from the last step was defined as 'modulesdir'. The 'g3fa3d71' part will be different for you, since it reflects the git hash of the repo at build time.
thank you @bander. I did it ... now messed my Wifi but I think i did that with installing connman (it didn't finish properly) and then the wifi was soft blocked so "sudo rfkill unblock wifi; sudo rfkill unblock all" and now the board hangs after/in boot .. I wanted to format the SD card any way.
@bander, @Andrea Rovai I took the latest iso, patched serial tty (+ && !sport->dma_is_inited + && !sport->port.flags == UPF_LOW_LATENCY)), enabled uart6 (+ status = "okay" compiled like above described and still nothing. which kernel version were you using? More important when I used the tree editor after that I could not boot till I removed 'use_custom_dtb=true' from uEnv.txt . What am I missing?
@Pilif You need more than status = 'okay'. Either enable in dtweb on Udoobuntu RC1, or fiddle with patch to dts that I posted in uart6 thread before I figured out the low-latency patch.
aha .. ok I missed Code: @@ -28,10 +28,10 @@ MX6SX_PAD_CSI_DATA01__GPIO1_IO_15 MX6SX_PAD_CSI_DATA02__GPIO1_IO_16 MX6SX_PAD_CSI_DATA03__GPIO1_IO_17 - MX6SX_PAD_CSI_DATA04__GPIO1_IO_18 - MX6SX_PAD_CSI_DATA05__GPIO1_IO_19 - MX6SX_PAD_CSI_DATA06__GPIO1_IO_20 - MX6SX_PAD_CSI_DATA07__GPIO1_IO_21 +// MX6SX_PAD_CSI_DATA04__GPIO1_IO_18 +// MX6SX_PAD_CSI_DATA05__GPIO1_IO_19 +// MX6SX_PAD_CSI_DATA06__GPIO1_IO_20 +// MX6SX_PAD_CSI_DATA07__GPIO1_IO_21 soo ok I will compile again and try the dtweb .. if it doesn't work again I will patch (also with dies) the dts .. Thank you @bander
