Hi Steve

You need to install device tree compiler. I suggest you compile it from 
source yourself, as there is a patch you need to apply. Here's my 
instructions from a manual I wrote a while ago:

BBB> git clone git://git.kernel.org/pub/scm/utils/dtc/dtc.git
BBB> cd dtc
BBB> git reset --hard f8cb5dd94903a5cfa1609695328b8f1d5557367f
BBB> wget https://patchwork.kernel.org/patch/1934471/raw/ -O 
dynamic-symbols.patch
BBB> git apply dynamic-symbols.patch
BBB> make
BBB> sudo cp dtc /usr/local/bin


On Friday, November 28, 2014 9:04:48 PM UTC+7, Steve G wrote:
>
> I'm trying to do this on my BBB with Debian but I'm getting a compile 
> error:
>
> debian@bbblack:~/dtb-rebuilder$ make
>   DTC     src/arm/am335x-base0033.dtb
> /bin/sh: 1: dtc: not found
> make[1]: *** [src/arm/am335x-base0033.dtb] Error 127
> make: *** [all_arm] Error 2
> debian@bbblack:~/dtb-rebuilder$ 
>
> I followed the custom dtb directions in the link.
>
> On Friday, November 14, 2014 4:12:22 PM UTC-5, RobertCNelson wrote:
>>
>> http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb
>>
>> The pins aren't mixed to the peripheral.
>>
>> Example enable this
>>
>>
>> https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-boneblack.dts#L78
>>
>> And run...
>>
>> make ; sudo make install ; sudo reboot
>> On Nov 14, 2014 2:46 PM, <m.jafa...@gmail.com> wrote:
>>
>>> I've been playing around with my BBB for about a month now and got 
>>> everything up and running. Today I spent the whole day to get UART loopback 
>>> to work on Debian. It simply doesn't work! Tried with Qt (cross-compiled 
>>> and all samples are working), QSerialPortInfo::availablePorts().count() 
>>> returns zero. At first I thought it can be a QtSerialPort issue. So I did a 
>>> loop back on UART1 and UART2 (P9.21 connected to P9.26 and P9.22 connected 
>>> to P9.24). Then opened "minicom -b 9600 -D /dev/ttyO1" and "minicom -b 9600 
>>> -D /dev/ttyO2" in two separate terminals. I expected to see whatever I type 
>>> in each one of the terminals on the other one. But that wasn't the case. 
>>> Nothing happens! Any idea what's wrong?
>>>
>>> Here's some info about my setup:
>>>
>>> *Fresh install of 
>>> "BBB-eMMC-flasher-debian-7.7-console-armhf-2014-10-29-2gb.img.xz". Didn't 
>>> modify anything. *
>>>
>>> *"uname -a": *
>>> Linux arm 3.14.22-ti-r31 #1 SMP PREEMPT Fri Oct 24 20:50:46 UTC 2014 
>>> armv7l GNU/Linux
>>>
>>> *"dmesg | grep ttyO":*
>>> [    0.000000] Kernel command line: console=ttyO0,115200n8 
>>> root=UUID=a52b5fd5-953d-458c-94d0-0cf2ff1c7115 ro rootfstype=ext4 rootwait 
>>> fixrtc quiet init=/lib/systemd/systemd
>>> [    2.799292] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88, 
>>> base_baud = 3000000) is a OMAP UART0
>>> [    2.800424] console [ttyO0] enabled
>>> [    2.802247] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89, 
>>> base_baud = 3000000) is a OMAP UART1
>>> [    2.803710] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90, 
>>> base_baud = 3000000) is a OMAP UART2
>>> [    2.805198] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61, 
>>> base_baud = 3000000) is a OMAP UART4
>>> [    2.806622] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62, 
>>> base_baud = 3000000) is a OMAP UART5
>>>
>>> *"ls -al /dev/ttyO*":*
>>> crw-rw---- 1 root tty     249, 0 Oct 29 19:06 /dev/ttyO0
>>> crw-rw---T 1 root dialout 249, 1 Nov 14 17:41 /dev/ttyO1
>>> crw-rw---T 1 root dialout 249, 2 Nov 14 17:41 /dev/ttyO2
>>> crw-rw---T 1 root dialout 249, 4 Jan  1  2000 /dev/ttyO4
>>> crw-rw---T 1 root dialout 249, 5 Jan  1  2000 /dev/ttyO5
>>>
>>>
>>> I appreciate anything that might help! :)
>>>
>>> -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to beagleboard...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to