[beagleboard] Serial debug cable

[faimbs]

Hello!

I want to debug the boot sequence. 
But I unterstand not exactly the requirements.
Can I connect from my PC via RS232 on the Pin 1,4,5?

Or is this a special RS232?

Thank you!

-- 
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.

[beagleboard] Re: BBB Power supply over pin Header

[faimbs]

Found this in manual:
VDD_5V is the main power supply from the DC input jack. This voltage is not 
present 
when the board is powered via USB. The amount of current supplied by this 
rail is 
dependent upon the amount of current available. Based on the board design, 
this rail is 
limited to 1A per pin from the main board. 
The SYS_5V rail is the main rail for the regulators on the main board. When 
powered 
from a DC supply or USB, this rail will be 5V. The available current from 
this rail 
depends on the current available from the USB and DC external supplies.

and:
DO NOT APPLY VOLTAGE TO ANY I/O PIN WHEN POWER IS 
NOT SUPPLIED TO THE BOARD. IT WILL DAMAGE THE 
PROCESSOR AND VOID THE WARRANTY. 
NO PINS ARE TO BE DRIVEN UNTIL AFTER THE SYS_RESET 
LINE GOES HIGH.

I´m not sure what it means.
Have I use 5V on VDD or SYS?
And when I try to use an input, I must boot the BBB before the Input Pin is 
going high? This is unpossible. Because when the Input is high and the BBB 
lost Power it damaged?

Thanks for helping a newbie!

-- 
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.

[beagleboard] BBB Power supply over pin Header

[faimbs]

Hello!

Can I use two pins for power supply?
I want to made a cape for own powersupply.

If yes, which pins are + and -
And which voltage?

Thank you!

-- 
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.

[beagleboard] BBB (DATA ABORT ERROR)

[NISSIN]

Hi all,

I'm using arm-linux-gnueabi toolchain for compiling a simple asm program 
senda character over the uart. My linker file content is as shown


linker.ld
*
MEMORY
{
ram : ORIGIN = 0x8020, LENGTH = 0x1
}
 
SECTIONS
{
.text : { *(.text*) } > ram
}


assemblypgm.asm
**
#UART base locations from the TRM
.equ UART1.BASE, 0x4806A000
.equ UART2.BASE, 0x4806C000
#According to the Beagleboard-xM System Reference Manual, UART3 is 
connected to the serial port.
# vv USE ME USE ME HARD vv
.equ UART3.BASE, 0x4902
# ^^ USE ME USE ME HARD ^^
.equ UART4.BASE, 0x49042000
 
#We need to be in ARM mode - we may branch to Thumb mode later if desired.
.arm
_start:
   ldr r0,=UART3.BASE
   mov r1,#'A'
   strb r1,[r0]
  

_hang:
   b _hang



Makefile
**
ARMGNU = arm-none-eabi
AOPS = --warn --fatal-warnings
COPS = -Wall -Werror -O2 -nostdlib -nostartfiles -ffreestanding 
 
boot.bin: boot.asm
$(ARMGNU)-as assemblypgm.asm -o boot.o
$(ARMGNU)-ld -T linker.ld boot.o -o boot.elf
$(ARMGNU)-objdump -D boot.elf > boot.list
$(ARMGNU)-objcopy  boot.elf -O srec boot.srec
$(ARMGNU)-objcopy  boot.elf -O binary boot.bin
   


My problem is that after copying to the BBB using loady - y-modem protocol 
and then pressing any key I'm getting a Data Abort Error and the board 
restarts. The kernel is stored in eMMC and there is no sd card inserted in 
it.

The log of error in my BBB
***

U-Boot# go 
0x8020   
## Starting application at 0x8020 
...   
data 
abort  


MAYBE you should read 
doc/README.arm-unaligned-accesses 


pc : [<80200010>]  lr : 
[<9f35b2d4>]
sp : 9f238e10  ip : 000f fp : 
9f2397b8  
r10: 0002  r9 : 9f3ae150 r8 : 
9f238f40  
r7 : 9f2397c8  r6 : 8020 r5 : 0002  r4 : 
9f2397cc   
r3 : 8020  r2 : 9f2397cc r1 : 0021  r0 : 
4902   
Flags: nZCv  IRQs off  FIQs on  Mode 
SVC_32 
Resetting CPU ...   


How can I overcome it  ??


Reagrds
NISSIN  

-- 
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.

Re: [beagleboard] root password BBB ubuntu

[William Hermans]

Sid, if you've ever used Ubuntu, then you should already know what Robert
is saying. Root by default on Ubuntu is disabled. That does not mean there
is no root account, it means the root account is DISABLED.

To boot, information about this is all over the web, one simple google
search would have provided more than enough information to figure the
problem out . . .

On Tue, Oct 14, 2014 at 6:11 PM, Sid Boyce  wrote:

> On 14/10/14 01:01, Robert Nelson wrote:
>
>> On Mon, Oct 13, 2014 at 6:48 PM,   wrote:
>>
>>> Hi,
>>>
>>>   After installing ubuntu console on BBB from here:
>>> http://elinux.org/BeagleBoardUbuntu#Trusty_14.04 and connecting with
>>> Putty
>>>
>>> login as: ubuntu
>>> ubuntu@192.168.7.2's password:
>>> Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)
>>>
>>>   * Documentation:  https://help.ubuntu.com/
>>> Last login: Wed Aug 13 18:11:23 2014 from 192.168.7.1
>>> ubuntu@arm:~$ sudo passwd root
>>> [sudo] password for ubuntu:
>>>
>>> what is the [sudo] password, root password?
>>>
>>> How can I login as root? change password for root?
>>>
>> It's ubuntu, by "default" there is no "root" user..
>>
>> This is the way ubuntu has been since 2006, if you want a root user
>> you need to enable/create it.
>>
>> Regards,
>>
>>  With every Ubuntu version I have used, there is a root user just that a
> password is not set for it during install as is the case with other distros.
>
> At no stage do you need to do "useradd root".
>
> login as ubuntu
> "sudo su" and give the ubuntu passwd "temppwd"
> "passwd root" and set the root password.
> Regards
> Sid.
>
> --
> Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
> Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
> Senior Staff Specialist, Cricket Coach
> Microsoft Windows Free Zone - Linux used for all Computing Tasks
>
>
> --
> 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.
>

-- 
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.

Re: [beagleboard] RobertCNelson Tree

[tcmichals]

>
>
> pru is enabled in the 3.14-ti tree: 
>
> http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Capes 
>
> Use bb.org_defconfig 

 for 
the default config file?  

I guess this will be the kernel moving forward?  I see from the uio_pruss.c 
 they 
are not using any device tree support.  I guess these fixes are not going 
forward into the mainline? 

Thank you for your help,

Tim 

-- 
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.

Re: [beagleboard] root password BBB ubuntu

[Sid Boyce]

On 14/10/14 01:01, Robert Nelson wrote:

On Mon, Oct 13, 2014 at 6:48 PM,   wrote:

Hi,

  After installing ubuntu console on BBB from here:
http://elinux.org/BeagleBoardUbuntu#Trusty_14.04 and connecting with Putty

login as: ubuntu
ubuntu@192.168.7.2's password:
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)

  * Documentation:  https://help.ubuntu.com/
Last login: Wed Aug 13 18:11:23 2014 from 192.168.7.1
ubuntu@arm:~$ sudo passwd root
[sudo] password for ubuntu:

what is the [sudo] password, root password?

How can I login as root? change password for root?

It's ubuntu, by "default" there is no "root" user..

This is the way ubuntu has been since 2006, if you want a root user
you need to enable/create it.

Regards,

With every Ubuntu version I have used, there is a root user just that a 
password is not set for it during install as is the case with other distros.


At no stage do you need to do "useradd root".

login as ubuntu
"sudo su" and give the ubuntu passwd "temppwd"
"passwd root" and set the root password.
Regards
Sid.

--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

--
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.

Re: [beagleboard] RobertCNelson Tree

[tcmichals]

>
>
>
> PRU: 
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/267588.html 
>
> "capemgr": 
> Waiting for overlays/etc... 
> https://lkml.org/lkml/2014/7/23/756 
>
> PM: Beg/borrow/steal from: 
> http://git.ti.com/ti-linux-kernel/ti-linux-kernel/commits/ti-linux-3.12.y 
> http://git.ti.com/ti-linux-kernel/ti-linux-kernel/commits/ti-linux-3.14.y 
>
> Is there a solution to support the PRU in 3.14+? 

-- 
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.

[beagleboard] BBB symbol/footprint for gEDA

[Britton Kerin]

In case anyone else is designing capes with gEDA, I updated my bone
symbol for the black:

   http://brittonkerin.com/beaglebone_symbol/

The footprint shows where are the sockets are now too.

-- 
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.

[beagleboard] how to gate input GPIO during powerup? also BBB SRM problems

[Britton Kerin]

The System Reference Manual (SRM) says you're supposed to gate all GPIO
(and other inputs) such that they aren't driven until either the SYS_RESET
line goes high (according to SRM section 7.1, 8.0, and possibly others) or
until the VDD_3V3B rail is up (according to SRM 8.6.2).  Are these conditions
identical in practice?  If not which is the right one?

Is there a good tested way (appropriate IC I guess) to gate such signals?

Also, the reference manual section 8.3.1 says this:

 If you plan to use any of these signals, then on power up, these pins
 should not be driven.  If you do, it can affect the boot mode of the
 processor and could keep the processor from booting or working correctly.

while not wrong this paragraph is going to create a dangerous wrong impression
for most readers: that the boot pins are special and are the ones you have to
worry about driving early.  I think it would be good to change this paragraph
or add a pointer to the other warnings that apply to all pins or something.

Finally, section 8.6.2 says this:

 3) Do not apply any voltages that are generated from external sources.

which if the ground is common and solid and the voltage source is behaving
I can't believe.  Can someone explain how the bone can tell the difference
in this case?  Is it so sensitive that any tiny ground flow can fry things
or what?

-- 
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.

Re: [beagleboard] RobertCNelson Tree

[Robert Nelson]

On Tue, Oct 14, 2014 at 6:52 PM, tcmichals  wrote:
>>
>>
>> The three biggest subsystems missing on mainline are:
>>
>> PRU:
>>
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/267588.html
>>
>> "capemgr":
>> Waiting for overlays/etc...
>> https://lkml.org/lkml/2014/7/23/756
>>
>> PM: Beg/borrow/steal from:
>> http://git.ti.com/ti-linux-kernel/ti-linux-kernel/commits/ti-linux-3.12.y
>> http://git.ti.com/ti-linux-kernel/ti-linux-kernel/commits/ti-linux-3.14.y
>>
>
> Is there any status update on PRU being supported in the 3.14+ kernel?

pru is enabled in the 3.14-ti tree:

http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Capes

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
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.

Re: [beagleboard] RobertCNelson Tree

[tcmichals]

>
>
>
> The three biggest subsystems missing on mainline are: 
>
> PRU: 
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/267588.html 
>
> "capemgr": 
> Waiting for overlays/etc... 
> https://lkml.org/lkml/2014/7/23/756 
>
> PM: Beg/borrow/steal from: 
> http://git.ti.com/ti-linux-kernel/ti-linux-kernel/commits/ti-linux-3.12.y 
> http://git.ti.com/ti-linux-kernel/ti-linux-kernel/commits/ti-linux-3.14.y 
>
>
Is there any status update on PRU being supported in the 3.14+ kernel?  

-- 
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.

Re: [beagleboard] help needed with kernal GPIO Interrupts via device tree overlay

[William Lear]

On Tuesday, October 14, 2014 6:57:24 PM UTC-4, RobertCNelson wrote:
>
> On Tue, Oct 14, 2014 at 5:48 PM, William Lear  > wrote: 
> >> 
> >> 
> >> > reg = <0x38>; 
> >> > interrupt-parent = <&gpio2>; 
> >> 
> >>  interrupt-parent = <&gpio3>; /* really gpio2 in v3.8.x 
> */ 
> >> 
> >> Regards, 
> >> 
> >> -- 
> >> Robert Nelson 
> >> http://www.rcn-ee.com/ 
> > 
> > 
> > That would explain a lot. I am running the 3.8 kernel/Debian. I 
> backported 
> > an updated version of the driver from the 3.15 kernel.  I was not aware 
> of 
> > the indexing issue.   Do you think I will need to change anything in the 
> > driver source to accommodate this, or is it strictly a  device tree 
> issue? 
>
> It's strictly in the gpio/pinctrl driver.. Off hand i don't remember 
> which commit/kernel version it was fixed in. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

Excellent.  I'll make the changes and report back one way or the other.
Thanks again,
Bill

-- 
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.

Re: [beagleboard] help needed with kernal GPIO Interrupts via device tree overlay

[Robert Nelson]

On Tue, Oct 14, 2014 at 5:48 PM, William Lear  wrote:
>>
>>
>> > reg = <0x38>;
>> > interrupt-parent = <&gpio2>;
>>
>>  interrupt-parent = <&gpio3>; /* really gpio2 in v3.8.x */
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>
>
> That would explain a lot. I am running the 3.8 kernel/Debian. I backported
> an updated version of the driver from the 3.15 kernel.  I was not aware of
> the indexing issue.   Do you think I will need to change anything in the
> driver source to accommodate this, or is it strictly a  device tree issue?

It's strictly in the gpio/pinctrl driver.. Off hand i don't remember
which commit/kernel version it was fixed in.

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
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.

Re: [beagleboard] help needed with kernal GPIO Interrupts via device tree overlay

[William Lear]

> 

> > reg = <0x38>; 
> > interrupt-parent = <&gpio2>; 
>
>  interrupt-parent = <&gpio3>; /* really gpio2 in v3.8.x */ 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

That would explain a lot. I am running the 3.8 kernel/Debian. I backported 
an updated version of the driver from the 3.15 kernel.  I was not aware of 
the indexing issue.   Do you think I will need to change anything in the 
driver source to accommodate this, or is it strictly a  device tree issue?

Thanks much!

Bill 

-- 
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.

Re: [beagleboard] help needed with kernal GPIO Interrupts via device tree overlay

[Robert Nelson]

On Tue, Oct 14, 2014 at 4:46 PM, William Lear  wrote:
> I am writing a device tree overlay file for a custom cape containing a
> touchscreen , and am having problems mapping a GPIO line as an interrupt to
> be handled by a device driver.
> I cannot get interrupt pulses on my GPIO line to invoke the ISR in the
> device driver.
>
> I have reached the limits of my BBB debug capabilities - I'm looking for any
> suggestions about how to find
> the disconnect  between the pin and the ISR.
>
> Thanks,
> Bill
> -
> What I have so far:
> My .dts file compiles, is loaded, configures the pins. the driver maps its
> ISR to the IRQ obtained from devm_request_threaded_irq(),
> and I have verified with a scope that the hardware is generating Interrupt
> requests on the correct pin.
>
> The applicable fragments from my overlay are:
>
> fragment@0 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> pinctrl-single,pins = <
> 0x90 0x37  /* INT   gpio2_2, MODE7, INPUT,
> PULLUP */
> 0x44 0x17  /* RESET gpio1_17,MODE7, OUTPUT,
> PULLUP */
>>;
>  };
> };
>
> fragment@1{
> target = <&i2c2>;
> __overlay__ {
> #address-cells = <1>;
> #size-cells = <0>;
> status = "okay";
>
> /* Capacitive Touch Panel */
> edt_ft5x06@38 {
> status = "okay";
> compatible = "edt,edt-ft5x06";
> /*compatible = "ft5x0x_ts";*/
> pinctrl-names = "default";
> pinctrl-0 = <&pharm_ctp_pins>;
>
> reg = <0x38>;
> interrupt-parent = <&gpio2>;

 interrupt-parent = <&gpio3>; /* really gpio2 in v3.8.x */

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
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.

Re: [beagleboard] help needed with kernal GPIO Interrupts via device tree overlay

[Robert Nelson]

On Tue, Oct 14, 2014 at 4:46 PM, William Lear  wrote:
> I am writing a device tree overlay file for a custom cape containing a
> touchscreen , and am having problems mapping a GPIO line as an interrupt to
> be handled by a device driver.
> I cannot get interrupt pulses on my GPIO line to invoke the ISR in the
> device driver.
>
> I have reached the limits of my BBB debug capabilities - I'm looking for any
> suggestions about how to find
> the disconnect  between the pin and the ISR.
>
> Thanks,
> Bill
> -
> What I have so far:
> My .dts file compiles, is loaded, configures the pins. the driver maps its
> ISR to the IRQ obtained from devm_request_threaded_irq(),
> and I have verified with a scope that the hardware is generating Interrupt
> requests on the correct pin.
>
> The applicable fragments from my overlay are:
>
> fragment@0 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> pinctrl-single,pins = <
> 0x90 0x37  /* INT   gpio2_2, MODE7, INPUT,
> PULLUP */
> 0x44 0x17  /* RESET gpio1_17,MODE7, OUTPUT,
> PULLUP */
>>;
>  };
> };
>
> fragment@1{
> target = <&i2c2>;
> __overlay__ {
> #address-cells = <1>;
> #size-cells = <0>;
> status = "okay";
>
> /* Capacitive Touch Panel */
> edt_ft5x06@38 {
> status = "okay";
> compatible = "edt,edt-ft5x06";
> /*compatible = "ft5x0x_ts";*/
> pinctrl-names = "default";
> pinctrl-0 = <&pharm_ctp_pins>;
>
> reg = <0x38>;
> interrupt-parent = <&gpio2>;
> interrupts = <2 1>;
>
> reset-gpios = <&gpio1 17 1>;
>
> touchscreen-size-x = <480>;
> touchscreen-size-y = <272>;
> };
>  };
> };
>
> The pins are properly configured as confirmed by
> /sys/kernel/debug/pinctrl/44e10800.pinmux/*
> Debug prints in the driver confirms its probe function runs cleanly, and the
> ISR is never called.
> /proc/interrupts confirms that an IRQ is assigned as GPIO to the driver
> (with either compatible driver).

This is on 3.14 (note the &gpioX index was one off in v3.8.x)

https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-bbb-exp-c.dtsi#L50

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
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.

[beagleboard] help needed with kernal GPIO Interrupts via device tree overlay

[William Lear]

I am writing a device tree overlay file for a custom cape containing a 
touchscreen , and am having problems mapping a GPIO line as an interrupt to 
be handled by a device driver.
I cannot get interrupt pulses on my GPIO line to invoke the ISR in the 
device driver.

I have reached the limits of my BBB debug capabilities - I'm looking for 
any suggestions about how to find
the disconnect  between the pin and the ISR.

Thanks,
Bill
-
What I have so far:
My .dts file compiles, is loaded, configures the pins. the driver maps its 
ISR to the IRQ obtained from devm_request_threaded_irq(), 
and I have verified with a scope that the hardware is generating Interrupt 
requests on the correct pin.

The applicable fragments from my overlay are:

fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
pinctrl-single,pins = <
0x90 0x37  /* INT   gpio2_2, MODE7, INPUT, 
PULLUP */
0x44 0x17  /* RESET gpio1_17,MODE7, OUTPUT, 
PULLUP */
   >;
 };
};

fragment@1{
target = <&i2c2>;
__overlay__ {
#address-cells = <1>;
#size-cells = <0>;
status = "okay";

/* Capacitive Touch Panel */
edt_ft5x06@38 {
status = "okay";
compatible = "edt,edt-ft5x06";
/*compatible = "ft5x0x_ts";*/
pinctrl-names = "default";
pinctrl-0 = <&pharm_ctp_pins>;

reg = <0x38>;
interrupt-parent = <&gpio2>;
interrupts = <2 1>;

reset-gpios = <&gpio1 17 1>;

touchscreen-size-x = <480>;
touchscreen-size-y = <272>;
};
 };
};

The pins are properly configured as confirmed by 
/sys/kernel/debug/pinctrl/44e10800.pinmux/*
Debug prints in the driver confirms its probe function runs cleanly, and 
the ISR is never called.
/proc/interrupts confirms that an IRQ is assigned as GPIO to the driver 
(with either compatible driver).



-- 
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.

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[jmelson]

On Monday, October 13, 2014 1:37:18 PM UTC-5, Greg Kelley wrote:
>
> Mine is still resetting one to three times a day. I have moved both 
> processes I was running on it (CUPS and weewx) over to my RasPi so it is 
> just sitting idle except for CRON jobs. No events in serial debug logs, 
> just a sudden reset and cold boot restart.
>
> I have used several Bone Blacks in projects.  One of them ran for about 3 
months without reboot.  Due to some other
software I am using, I used the machinekit distribution (which is based on 
the esteemed Robert Nelson distro, but
has Xenomai RT extensions on the kernel.)  So, you might try out the 
machinekit distro and see if this problem
goes away.

Jon

-- 
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.

[beagleboard] Re: Can't find /sys/class

[mrbarre7612]

I reinstalled Ubuntu 14.04 and now I can find the /sys/class directory. Not 
sure what caused the problem but at least it is working now. 

-- 
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.

Re: [beagleboard] Code Composer Studio 6 <--> Beaglebone black

[Gerald Coley]

Sounds like solution of some sort..

Gerald

On Tue, Oct 14, 2014 at 2:06 PM, John Syn  wrote:

>
> From: Gerald Coley 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Tuesday, October 14, 2014 at 8:20 AM
> To: "beagleboard@googlegroups.com" 
> Cc: 
> Subject: Re: [beagleboard] Code Composer Studio 6 <--> Beaglebone black
>
> The JTAG header is used by the emulators. You can install it without
> buying the emulators, certainly. However, you can't use it without the
> emulator. You have to connect something to it to use it.
>
> To use CCS, you have to have an emulator.BTW, the emulator is a piece of
> HW required for access to the JTAG.
>
> He can use GDBServer on the BBB and use GDB in CCSV6 to debug user
> applications on the BBB. He only needs JTAG emulator if he wants to debug
> kernel code.
>
> Regards,
> John
>
>
> You do not need CCS to right code on the board.
>
> Gerald
>
>
> On Tue, Oct 14, 2014 at 4:28 AM,  wrote:
>
>> Hello,
>>
>> I try to create, compile and download a small C program within Code
>> Composer Studio 6 (under Windows XP)
>> to Element14 Beaglebone black (rev. C).
>>
>> For a first try I am not interested in debugging; the c-code should just
>> execute.
>>
>> *Is it really the only way to populate the JTAG connector (P2) on BBB and
>> buy one of the emulators?*
>>
>> I have the BBB connected via Ethernet, USB and USB-232 FTDI cable (J1: 6
>> pin header on BBB).
>> Is it really true that none of these connections are sufficient to
>> download and run a c-code?
>> Does one really have to buy an emulator?
>> Is there no possibility to just download and run the code?
>>
>> Can someone please explain to me, how to create a c-code on windows and
>> run it on the beaglebone black board.
>>
>> Thank you!
>>
>>
>> --
>> 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.
>>
>
> --
> 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.
>
>  --
> 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.
>

-- 
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.

Re: [beagleboard] Code Composer Studio 6 <--> Beaglebone black

[John Syn]

From:  Gerald Coley 
Reply-To:  "beagleboard@googlegroups.com" 
Date:  Tuesday, October 14, 2014 at 8:20 AM
To:  "beagleboard@googlegroups.com" 
Cc:  
Subject:  Re: [beagleboard] Code Composer Studio 6 <--> Beaglebone black

> The JTAG header is used by the emulators. You can install it without buying
> the emulators, certainly. However, you can't use it without the emulator. You
> have to connect something to it to use it.
> 
> To use CCS, you have to have an emulator.BTW, the emulator is a piece of HW
> required for access to the JTAG.
He can use GDBServer on the BBB and use GDB in CCSV6 to debug user
applications on the BBB. He only needs JTAG emulator if he wants to debug
kernel code. 

Regards,
John
> 
> You do not need CCS to right code on the board.
> 
> Gerald
> 
> 
> On Tue, Oct 14, 2014 at 4:28 AM,   wrote:
>> Hello,
>> 
>> I try to create, compile and download a small C program within Code Composer
>> Studio 6 (under Windows XP)
>> to Element14 Beaglebone black (rev. C).
>> 
>> For a first try I am not interested in debugging; the c-code should just
>> execute.
>> 
>> Is it really the only way to populate the JTAG connector (P2) on BBB and buy
>> one of the emulators?
>> 
>> I have the BBB connected via Ethernet, USB and USB-232 FTDI cable (J1: 6 pin
>> header on BBB).
>> Is it really true that none of these connections are sufficient to download
>> and run a c-code?
>> Does one really have to buy an emulator?
>> Is there no possibility to just download and run the code?
>> 
>> Can someone please explain to me, how to create a c-code on windows and run
>> it on the beaglebone black board.
>> 
>> Thank you!
>> 
>> 
>> 
>> -- 
>> 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.
> 
> 
> -- 
> 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black C Not Recognized by Computer

[Robert Nelson]

On Tue, Oct 14, 2014 at 1:26 PM, Ben McDui  wrote:
> I have the same issue, more or less. See "You can't brick it".

Then reflash:

http://beagleboard.org/latest-images

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
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.

[beagleboard] Re: BeagleBone Black C Not Recognized by Computer

[Ben McDui]

I have the same issue, more or less. See "You can't brick it".

Op vrijdag 3 oktober 2014 06:14:12 UTC+2 schreef michaelkn...@gmail.com:
>
> Basically I've got a BeagleBone Black Revision C that I'm trying to 
> connect to my computer.
> I'm running Debian Linux all up to date on my laptop.  I've got the 
> BeagleBone plugged into the power and a usb cord running from the Beagle to 
> my laptop.  When I go to the URL http://192.168.7.2/ nothing comes up.  
> It just tries to load forever.
> When I plug the board in, nothing is showing up in dmesg either.
> Any ideas?
>

-- 
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.

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[DLF]

Hello,

I'm kind of a noob but willing to help investigate if needed.  

I once had random reboots and traced it to an overheating problem.  I don't 
know if log files trap overheating messages or not.  I had a blocked vent 
and once it was cleared, no probem.

On a second point, my BBB is stable running 3.14.17-ti-r15.  If you make an 
image send it to me, I could load it on my side and see if it crashes or 
not.  If it crashes, it sounds like software.  If it does not crash, it 
could be hardware (QA?) or environment related (EM?). - As I said, I am a 
noob, so perhaps this could be a waste of your time.

cheers,





On Tuesday, 14 October 2014 08:02:22 UTC+2, Thomas O wrote:
>
> We still have the same issues with reboots as well. we have had to move 
> our project to bbw for now instead. the bbw with the same kernel and no 
> reboots for two weeks. The BBB reboots on an average og 1-2 times per 24 
> hours independent of load.
>
> No serial messages. No kernel messages, no oops. We have also tried a 
> kernel wo watchdog support with no avail...
>
> Any suggestions is highly appreciated at this point..
>
> --Skjortan!
>
> On Mon, Oct 13, 2014 at 8:37 PM, Greg Kelley  > wrote:
>
>> Mine is still resetting one to three times a day. I have moved both 
>> processes I was running on it (CUPS and weewx) over to my RasPi so it is 
>> just sitting idle except for CRON jobs. No events in serial debug logs, 
>> just a sudden reset and cold boot restart.
>>
>>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/vgeh336p0P4/unsubscribe.
>> To unsubscribe from this group and all its topics, 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.

[beagleboard] Setting GPIO BeagleBoard xm

[jeissongrajales98898]

Hello:

I have a BeagleBoard XM with Archlinux and the next specifications:

Linux asarm 3.14.2-1-ARCH #1 SMP PREEMPT Tue Apr 29 18:48:53 MDT 2014 
armv7l GNU
/Linux

I don't know to setting my Beagleboard xm to use the GPIOS and i am new in 
this. 

I hope prompt response.

Thanks

YAO

-- 
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.

RE: [beagleboard] beaglebone black applications

[William Pretty Security]

Google !

 

Derek Molloy has several videos ….

 

"No one could make a greater mistake than he who did nothing because he could 
do only a little."

"All that is necessary for the triumph of evil is that good men do nothing" 
Edmond Burke (1729 - 1797)

http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book

 

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Ahmed Helmy
Sent: Tuesday, October 14, 2014 12:21 PM
To: beagleboard@googlegroups.com
Subject: [beagleboard] beaglebone black applications

 

i have a beaglebone black board , and i want to connect it with usb camera , 
and i'm using win 7 
the operating system is angstrom latest version 
and i don't know from where can i start ?
?could anyone 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4040/8387 - Release Date: 10/14/14

  _  

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4025/8299 - Release Date: 09/30/14
Internal Virus Database is out of date.

-- 
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.

Re: [beagleboard] Re: Cross compiling using Eclipse and Ubuntu 64bit 12.04

[Curt Carpenter]

Pretty much my experience too mrbar -- and I'm still trying to get up to 
speed on all of the parts involved in cross-compiling.  
Congratulations of getting everything to work!

On Monday, October 13, 2014 10:44:31 AM UTC-5, mrbar...@gmail.com wrote:
>
> I finally got it working. I deleted Eclipse and reinstalled it. I had two 
> issues. #1 When I created my project instead of using Cross Toolchain I 
> used Linux. In the Derek Molloy video when he creates his project he only 
> has the Linux Toolchain listed so not knowing much about Ubuntu or Eclipse 
> I followed the video. I also changed the toolchain to gneuabihf. Once I 
> made these two changes everything started working. The good news is I 
> learned a lot about Ubuntu and Eclipse during the process and now feel more 
> comfortable with both products. 
>
>
>
>

-- 
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.

Re: [beagleboard] Re: dts with #include ".dtsi" will not compile

[Robert Nelson]

On Tue, Oct 14, 2014 at 11:10 AM, Nic Cyn  wrote:
> Thank you.
>
> My dtc compiler version is exactly the same - not surprising since I am
> using your version installed as described on
> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Upgradedistro%22device-tree-compiler%22package
>
> So it must be the command line. What is in the DTC script. Can you please
> "cat DTC" for me.
>
> No doubt I am missing something simple.

https://github.com/RobertCNelson/dtb-rebuilder/tree/3.14-ti

https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/Makefile#L120

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
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.

[beagleboard] beaglebone black applications

[Ahmed Helmy]

i have a beaglebone black board , and i want to connect it with usb camera 
, and i'm using win 7 
the operating system is angstrom latest version 
and i don't know from where can i start ?
?could anyone 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: dts with #include ".dtsi" will not compile

[Nic Cyn]

Thank you. 

My dtc compiler version is exactly the same - not surprising since I am 
using your version installed as described on 
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Upgradedistro%22device-tree-compiler%22package

So it must be the command line. What is in the DTC script. Can you please 
"cat DTC" for me.

No doubt I am missing something simple. 

Much appreciated.


On Tuesday, 14 October 2014 16:46:26 UTC+1, RobertCNelson wrote:
>
> On Tue, Oct 14, 2014 at 10:40 AM, Nic Cyn  > wrote: 
> > Bump 
> > 
> > I am still struggling with this. If you can compile a dts file with a 
> > #include tag (for example the 3.14 kernel dts files) can you please tell 
> me 
> > the dtc compiler version you are using (dtc -version) and the command 
> line 
> > that works. 
> > 
> > All I ever get is a "FATAL ERROR: Unable to parse input tree" error and 
> I am 
> > really struggling with this. 
> > 
> > Your assistance is much appreciated. 
>
>   DTC src/arm/am335x-boneblack-base.dtb 
>   DTC src/arm/am335x-bone-4dcape-70t.dtb 
>   DTC src/arm/am437x-gp-evm.dtb 
>   DTC src/arm/am335x-bone-lcd7-01-00a3.dtb 
>   DTC src/arm/am335x-bone-can1.dtb 
>   DTC src/arm/am335x-bone-lcd4-01-00a1.dtb 
>   DTC src/arm/omap3-overo-storm-tobi.dtb 
>   DTC src/arm/am437x-sk-evm.dtb 
>   DTC src/arm/am335x-boneblack-audio-reva.dtb 
>   DTC src/arm/am335x-boneblack-ttyO2.dtb 
>   DTC src/arm/am335x-bone-audio-revb.dtb 
>   DTC src/arm/dra72-evm.dtb 
>   DTC src/arm/omap3-evm.dtb 
>   DTC src/arm/am335x-boneblack-rtc-01-00a1.dtb 
>   DTC src/arm/am3517-evm.dtb 
>   DTC src/arm/omap4-panda-es.dtb 
>   DTC src/arm/am335x-boneblack-bbb-exp-c.dtb 
>   DTC src/arm/dra7-evm.dtb 
> voodoo@hades:/opt/github/dtb-rebuilder$ cat 
> src/arm/am335x-boneblack-base.dts | grep include 
> #include "am33xx.dtsi" 
> #include "am335x-bone-common.dtsi" 
> #include "am335x-bone-common-pinmux.dtsi" 
> #include "am335x-boneblack-emmc.dtsi" 
> #include "am335x-boneblack-nxp-hdmi-audio.dtsi" 
> voodoo@hades:/opt/github/dtb-rebuilder$ dtc --version 
> Version: DTC 1.4.0-gf345d9e4 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
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.

Re: [beagleboard] Re: dts with #include ".dtsi" will not compile

[Robert Nelson]

On Tue, Oct 14, 2014 at 10:40 AM, Nic Cyn  wrote:
> Bump
>
> I am still struggling with this. If you can compile a dts file with a
> #include tag (for example the 3.14 kernel dts files) can you please tell me
> the dtc compiler version you are using (dtc -version) and the command line
> that works.
>
> All I ever get is a "FATAL ERROR: Unable to parse input tree" error and I am
> really struggling with this.
>
> Your assistance is much appreciated.

  DTC src/arm/am335x-boneblack-base.dtb
  DTC src/arm/am335x-bone-4dcape-70t.dtb
  DTC src/arm/am437x-gp-evm.dtb
  DTC src/arm/am335x-bone-lcd7-01-00a3.dtb
  DTC src/arm/am335x-bone-can1.dtb
  DTC src/arm/am335x-bone-lcd4-01-00a1.dtb
  DTC src/arm/omap3-overo-storm-tobi.dtb
  DTC src/arm/am437x-sk-evm.dtb
  DTC src/arm/am335x-boneblack-audio-reva.dtb
  DTC src/arm/am335x-boneblack-ttyO2.dtb
  DTC src/arm/am335x-bone-audio-revb.dtb
  DTC src/arm/dra72-evm.dtb
  DTC src/arm/omap3-evm.dtb
  DTC src/arm/am335x-boneblack-rtc-01-00a1.dtb
  DTC src/arm/am3517-evm.dtb
  DTC src/arm/omap4-panda-es.dtb
  DTC src/arm/am335x-boneblack-bbb-exp-c.dtb
  DTC src/arm/dra7-evm.dtb
voodoo@hades:/opt/github/dtb-rebuilder$ cat
src/arm/am335x-boneblack-base.dts | grep include
#include "am33xx.dtsi"
#include "am335x-bone-common.dtsi"
#include "am335x-bone-common-pinmux.dtsi"
#include "am335x-boneblack-emmc.dtsi"
#include "am335x-boneblack-nxp-hdmi-audio.dtsi"
voodoo@hades:/opt/github/dtb-rebuilder$ dtc --version
Version: DTC 1.4.0-gf345d9e4

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
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.

[beagleboard] Re: dts with #include ".dtsi" will not compile

[Nic Cyn]

Bump

I am still struggling with this. If you can compile a dts file with a 
#include tag (for example the 3.14 kernel dts files) can you please tell me 
the dtc compiler version you are using (dtc -version) and the command line 
that works. 

All I ever get is a "FATAL ERROR: Unable to parse input tree" error and I 
am really struggling with this.

Your assistance is much appreciated.

On Friday, 10 October 2014 17:41:48 UTC+1, Nic Cyn wrote:
>
> Hi All
>
> I have a flat dts file taken from the dtb file and it will re-compile just 
> fine with a command like
>
> dtc -I dts -O dtb bb.dts > test.dtb
>
> however if I edit the bb.dts file to use an include line like
>
> #include "foo.dtsi"
>
> I get an error "FATAL ERROR: Unable to parse input tree". This happens no 
> matter where I put the include line or whatever is in the .dtsi file 
> (including only comments). The dtc version is Version: DTC 1.4.0-gf345d9e4
>
> My understanding is that this include should work. Is there a special 
> version of dtc for this or something else I am missing?
>

-- 
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.

Re: [beagleboard] PWM, Servos, and the BBB

[Gerald Coley]

Please do not tie a 5VDC servo direct to the pins of the expansion header.

http://www.elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Usage

I doubt the servo, one that you have failed to define, can be driven by
6mA,which is the extent of the drive of the 3.3V pins on the board.



Gerald


On Mon, Oct 13, 2014 at 7:07 PM,  wrote:

> Hi everybody.
> I've got a Beaglebone Black Rev A6A here, and no matter what I do, I can't
> get a servo running. I've tried Adafruit's nice BBIO.PWM library (to no
> avail) and I've tried using Bonescript. I've grounded the servo to the BBB,
> and run 5VDC in from a regulated Elenco supply to the servo. No matter what
> I do, I can't get it to turn. If I ground the servo to the power supply's
> COM, then it simply whines, no matter the duty cycle. If I ground it to the
> bone, nothing happens.
>
> Thanks in advance.
>
> --
> 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.
>

-- 
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.

[beagleboard] Re: dts with #include ".dtsi" will not compile

[dle4482]

Bump

Got no responses to this. Is there nobody who can compile the 3.14 kernel 
dts files (which contain the #include tag)? 

If you can compile the dts files please tell me what version of the dtc 
compiler you are using ( dtc -version) and what command line you use. 

I am really struggling with this. All I ever get is a "FATAL ERROR: Unable 
to parse input tree"

Your assistance is much appreciated

On Friday, October 10, 2014 5:41:48 PM UTC+1, Nic Cyn wrote:
>
> Hi All
>
> I have a flat dts file taken from the dtb file and it will re-compile just 
> fine with a command like
>
> dtc -I dts -O dtb bb.dts > test.dtb
>
> however if I edit the bb.dts file to use an include line like
>
> #include "foo.dtsi"
>
> I get an error "FATAL ERROR: Unable to parse input tree". This happens no 
> matter where I put the include line or whatever is in the .dtsi file 
> (including only comments). The dtc version is Version: DTC 1.4.0-gf345d9e4
>
> My understanding is that this include should work. Is there a special 
> version of dtc for this or something else I am missing?
>

-- 
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.

Re: [beagleboard] Code Composer Studio 6 <--> Beaglebone black

[Gerald Coley]

The JTAG header is used by the emulators. You can install it without buying
the emulators, certainly. However, you can't use it without the emulator.
You have to connect something to it to use it.

To use CCS, you have to have an emulator.BTW, the emulator is a piece of HW
required for access to the JTAG.

You do not need CCS to right code on the board.

Gerald


On Tue, Oct 14, 2014 at 4:28 AM,  wrote:

> Hello,
>
> I try to create, compile and download a small C program within Code
> Composer Studio 6 (under Windows XP)
> to Element14 Beaglebone black (rev. C).
>
> For a first try I am not interested in debugging; the c-code should just
> execute.
>
> *Is it really the only way to populate the JTAG connector (P2) on BBB and
> buy one of the emulators?*
>
> I have the BBB connected via Ethernet, USB and USB-232 FTDI cable (J1: 6
> pin header on BBB).
> Is it really true that none of these connections are sufficient to
> download and run a c-code?
> Does one really have to buy an emulator?
> Is there no possibility to just download and run the code?
>
> Can someone please explain to me, how to create a c-code on windows and
> run it on the beaglebone black board.
>
> Thank you!
>
>
>  --
> 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.
>

-- 
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.

[beagleboard] PWM, Servos, and the BBB

[madprogrammi]

Hi everybody.
I've got a Beaglebone Black Rev A6A here, and no matter what I do, I can't 
get a servo running. I've tried Adafruit's nice BBIO.PWM library (to no 
avail) and I've tried using Bonescript. I've grounded the servo to the BBB, 
and run 5VDC in from a regulated Elenco supply to the servo. No matter what 
I do, I can't get it to turn. If I ground the servo to the power supply's 
COM, then it simply whines, no matter the duty cycle. If I ground it to the 
bone, nothing happens.

Thanks in advance.

-- 
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.

[beagleboard] Running x86 apps on ARM

[kambarg]

Startup Eltechs has launched virtual machine that allow to run x86 codes on 
ARM. They say ExaGear Desktop (http://eltechs.com/product/exagear-desktop/) 
can run even Wine and hence Windows apps on ARM-based devices. 

News on Phoronix: http://www.phoronix.com/scan.php?page=news_item&px=MTgwMzc

-- 
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.

[beagleboard] Code Composer Studio 6 <--> Beaglebone black

[reinharddaemon]

Hello,

I try to create, compile and download a small C program within Code 
Composer Studio 6 (under Windows XP) 
to Element14 Beaglebone black (rev. C).

For a first try I am not interested in debugging; the c-code should just 
execute.

*Is it really the only way to populate the JTAG connector (P2) on BBB and 
buy one of the emulators?*

I have the BBB connected via Ethernet, USB and USB-232 FTDI cable (J1: 6 
pin header on BBB).
Is it really true that none of these connections are sufficient to download 
and run a c-code?
Does one really have to buy an emulator?
Is there no possibility to just download and run the code?

Can someone please explain to me, how to create a c-code on windows and run 
it on the beaglebone black board.

Thank you!


-- 
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.

[beagleboard] Can't find /sys/class

[mrbarre7612]

I have Ubuntu 14.04 running, setup Eclipse and can cross compile the 
HelloWorld program to my Beaglebone (white). The Beaglebone is running 
Ubuntu 12.04. I then tried moving to the blinking LED program in Derek 
Malloy's tutorial for C++. When I type the command /sys$  cd class I get 
message that says the file or directory does not exist. I tried the command 
on my Beaglebone and also on my desktop. I assume there is some step in 
setting up Ubuntu that I missed. Any help will be appreciated. Thanks

-- 
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.

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[Lei Wang]

I've run into the BBB random reboot problem a while ago. We've eventually 
found out the root cause is the USB-OTG detection. The USB-OTG periodical 
probing actually caused the problem. Details and fix please the link below:
https://groups.google.com/forum/#!searchin/beagleboard/unexpected$20reset/beagleboard/xPxzYyNsA78/DOlXIlyYTqIJ

However my fix was based on the 3.2 kernel. I am not familiar with the 
kernels you are working with. And I don't know if the USB-OTG is root cause 
in your case.

BBB and BBW have different PMIC designs. You could take a look at the 
schematic.

If you really want to isolate out the hardware, you can try to patch and 
build from 3.2 kernel to see if BBB still reboots. I have mulitple systems 
running for months and never had any random reboot issues.

I hope this helps.

Lei Wang


On Tuesday, October 14, 2014 2:42:43 AM UTC-4, William Hermans wrote:
>
> I do not know what to tell you other than . ..
>
>
>
>
> *william@arm:~$ uptime 23:30:30 up 26 days,  6:34,  1 user,  load average: 
> 0.00, 0.01, 0.05*
> This board is also loading it's rootfs via NFS, so it is constantly using 
> the local network. SO, this has been an ongoing problem for you, and going 
> on longer than a month ? Well All i can say is that you better get busy and 
> finding your problem. I suggest you start from a scratch build, and 
> incrementally install what you need one bit of software at a time until 
> something starts misbehaving. This is very obviously a software issue, and 
> despite what you say about having watchdog disabled I'm still of the 
> opinion that this *has* to be watchdog related. Otherwise you'd be 
> broadcasting a system wide kernel signal.
>
>
>
> On Mon, Oct 13, 2014 at 11:02 PM, Thomas Olofsson  > wrote:
>
>> We still have the same issues with reboots as well. we have had to move 
>> our project to bbw for now instead. the bbw with the same kernel and no 
>> reboots for two weeks. The BBB reboots on an average og 1-2 times per 24 
>> hours independent of load.
>>
>> No serial messages. No kernel messages, no oops. We have also tried a 
>> kernel wo watchdog support with no avail...
>>
>> Any suggestions is highly appreciated at this point..
>>
>> --Skjortan!
>>
>> On Mon, Oct 13, 2014 at 8:37 PM, Greg Kelley > > wrote:
>>
>>> Mine is still resetting one to three times a day. I have moved both 
>>> processes I was running on it (CUPS and weewx) over to my RasPi so it is 
>>> just sitting idle except for CRON jobs. No events in serial debug logs, 
>>> just a sudden reset and cold boot restart.
>>>
>>>  -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/beagleboard/vgeh336p0P4/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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...@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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Lei Wang]

Andrew,

Thanks very much for the very detailed explanation on the character of the 
init.generic*.rc files pushing.

In regarding to the navigation bar, I am using an element14 BBB with 
Circuito LCD4. So I don't have leisure to change the resolution. However I 
can using the LCD panel on-board buttons to navigate back. So it is not a 
big deal at this moment.

As Adam Singer mentioned, I am really looking forward to the kernel 
3.10/3.14 version with SGX support. Because kernel 3.10 adds much improved 
robustness to the USB driver.

Thanks again!

Lei



On Sunday, October 12, 2014 10:41:47 PM UTC-4, Andrew Henderson wrote:
>
> One thing that I should note is that if you use ADB to push files over to 
> the BBB, you must be sure that the permissions of the file that you pushed 
> are set correctly after the transfer.  If you are pushing the 
> init.generic*.rc files over, you must do something like:
>
> $ adb shell
> root@beagleboneblack:/ # chmod 750 init.genericam33xx\(flatteneddevicetr.rc
>
> If the permissions are too "permissive", the "import" command in init.rc 
> will refuse to include the init.generic*.rc file because it is a security 
> risk.  If the init.generic*.rc file isn't included, then ADB won't start, 
> and you are effectively prevented from using ADB at that point.  You'll 
> have to mount the EXT4 partition under Linux to fix the permissions.  Be 
> careful!
>
> Andrew
>
> On Sunday, October 12, 2014 9:50:55 PM UTC-4, Andrew Henderson wrote:
>>
>> The "rootfs" filesystem (the / filesystem) is set to read-only once you 
>> reach the post-fs phase of boot.  This is why you can't ADB push to it.  
>> I've been on the fence as to whether I should remount this as read-write, 
>> and I suppose that I probably should.  Since I'm trying to open up this 
>> Android a bit to make it easier for people to experiment with, it is 
>> reasonable to do so.  It also allows the Windows people who can't easily 
>> mount EXT4 to make changes to their Android system via ADB.
>>
>> Look at your init.genericam33xx(flatteneddevicetr.rc file at around line 
>> 36:
>>
>> # we will remap this as /storage/sdcard0 with the sdcard fuse tool
>> mkdir /data/media 0770 media_rw media_rw
>> chown media_rw media_rw /data/media
>>
>> # Set indication (checked by vold) that we have finished this action
>> setprop vold.post_fs_data_done 1
>>
>> Right before that "# Set indication ..." line, add these two lines:
>>
>> # BBBAndroid: Remount the rootfs as rw for ADB push of files to /
>> mount rootfs rootfs / rw remount
>>
>> This will remount / as read-write.  The original remount to read-only 
>> occurs in init.rc, but you generally don't want to change the standard .rc 
>> files, so I override all of the defaults in the platform-specific .rc 
>> files.  I just pushed this change up to the repo: 
>> https://github.com/hendersa/bbbandroid-vendor-ti-beagleboneblack-aosp
>>
>> I have not checked into the nav bar issue, but I know that I have seen it 
>> in some resolutions and not in others.  Maybe try a different resolution?  
>> I'll see it at 720x480, for example, when using HDMI.  But I won't see it 
>> at the much higher resolutions (1920x1080, I think).  
>>
>> Andrew
>>
>>
>> On Monday, October 13, 2014 1:13:44 AM UTC, Lei Wang wrote:
>>>
>>> Hi Andrew,
>>>
>>> I rebuild the BBBAndroid and created my own image. The ADB USB does work 
>>> after I replaced those (3) files you attached earlier. It is a very good 
>>> news. 
>>> But I did find out that I couldn't push file thru the ADB push. I tried 
>>> both the eclipse ADT and command line. Neither works. I've got some 
>>> information like,
>>>
>>> E:\Program Files\Android\android-sdk\platform-tools>adb push 
>>> "init.genericam33xx
>>> (flatteneddevicetr.rc" /init.genericam33xx(flatteneddevicetr.rc
>>> failed to copy 'init.genericam33xx(flatteneddevicetr.rc' to 
>>> '/init.genericam33xx
>>> (flatteneddevicetr.rc': Read-only file system
>>>
>>> Another minor issue is that the navigation bar is not shown in the 
>>> interface. I double checked the images you attached. I couldn't find 
>>> navigation bar either. I had same issue with TI's stock image (Kernel 3.2 
>>> based). I added a line to the  
>>> init.am335xevm.rc: "setprop lcd.landscape true", which fixed the problem 
>>> (
>>> https://gitorious.org/rowboat/vendor-ti-am335xevm/commit/53391ade1b440e94c73db59444bf72529ce9ff32).
>>>  
>>> I did the same to the init.generic*.rc file. However it didn't work this 
>>> time. I wonder if you know how to bring the navigation bar back.
>>>
>>>
>>>
>>> Thanks a lot!
>>>
>>> Lei
>>>
>>>
>>> On Sunday, October 12, 2014 1:03:54 PM UTC-4, Andrew Henderson wrote:

 I'll have to make the next pre-made image a little smaller than the 
 full capacity of my microSD cards because so many of the manufacturers are 
 being very liberal on exactly how many bytes they consider 8GB to be...

 I have a Realtek RTL8188CUS USB wifi dongle sitt