[beagleboard] Re: Can't seem to get pinmux working

2016-03-07 Thread Delbert Martin 
Ok it works after I disabled the HDMI option cause the pins the hdmi uses 
shares pins with the PRU1 r30_x bits. mystery solved. I was confused 
because all of the remarks made about disabling the HDMI cape. I 
disregarded this because there was no HDMI cape listed in cape mgr. 


On Monday, March 7, 2016 at 3:42:49 PM UTC-5, Delbert Martin wrote:
>
> Ok, think I kind of maybe figured it out. 
> looks like the nxp hdmi interface apparently uses these pins as well... so 
> I have to disable it... 
> are the HDMI and eMMC really that hard tied together?
> I couldn't find a way to disable one with out the other, or maybe I'm just 
> an idiot. 
> anyway off to pull a new image, and flash to an SD card, so I can boot 
> without eMMC. and a serial console...
>
>
>
> On Monday, March 7, 2016 at 1:22:43 PM UTC-5, Delbert Martin wrote:
>>
>> Trying to enable PRUs and set P8 45,46 to output just to test some IO 
>> toggle using R30 on PRU1
>> OVERLAY: project-00A0.dts:
>> /dts-v1/;
>> /plugin/;
>> /{
>> compatible = "ti,beaglebone","ti,beaglebone-black";
>> part-number = "project";
>> version = "00A0";
>>
>> exclusive-use = 
>> "P8.45",
>> "P8.46";
>> fragment@0 {
>> target = <_pinmux>;
>> __overlay__ {
>> bone_project_pins: pinmux_project_pins {
>> pinctrl-single,pins=<0x0a0 0x05 0x0a4 0x05>;
>> };
>> };
>> };
>> fragment@1 {
>> target = <>;
>> __overlay__ {
>> project {
>> compatible = "bone-pinmux-helper";
>> status = "okay";
>> pinctrl-names = "default";
>> pinctrl-0 = <_project_pins>;
>> };
>> };
>> };
>> fragment@2 {
>> target = <>;
>> __overlay__ {
>> status = "okay";
>> };
>> };
>> };
>>
>> /sys/devices/platform/bone-capemgr/slots:
>>  0: PF  -1 
>>  1: PF  -1 
>>  2: PF  -1 
>>  3: PF  -1 
>>  5: P-O-L-   0 Override Board Name,00A0,Override Manuf,project
>>
>> From /sys/kernel/debug/pinctrl/44e10800.pinmux/pins
>> ...
>> pin 40 (44e108a0.0) 0008 pinctrl-single 
>> pin 41 (44e108a4.0) 0008 pinctrl-single 
>> pin 42 (44e108a8.0) 0008 pinctrl-single 
>> pin 43 (44e108ac.0) 0008 pinctrl-single 
>> ...
>>
>> Just saying I would expect these to be set to 0x05 instead of 0x00, 
>> Stranger yet, I'm sure there is some kind of non-obvious reason that in 
>> the overlay file, you reference the pin as offset 0x0a0/0x0a4 when their 
>> real offsets are 0x44310800... wait, i see it there.. nevermind. 
>> anyway should pins be showing the value of 8 instead of 5?
>>
>>
>>
>>

-- 
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: LCD touch screen is not saved after reboot

2016-03-07 Thread Bremenpl 

  
  
Hello, thank you for answer.
Is there a way to actually manually read the calibrated points? You
calibration points are near, but still not as exact as when I do
manual calibration. I would apreciate further help.

W dniu 2016-03-02 o 08:10, Radovan
  Chovan pisze:


  
/usr/share/X11/xorg.conf.d
  - create file 99-calibration.conf with content:
  Section
"InputClass"

  Identifier "calibration"

  MatchProduct "ti-tsc"

  Option "Calibration" "145
  4001 346 3937"
 Option
  "SwapAxes" "0"
EndSection



  
  -- 
  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/nQPsVPl-S5o/unsubscribe.
  To unsubscribe from this group and all its topics, send an email
  to beagleboard+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.


-- 
Bremenpl
  




-- 
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 seem to get pinmux working

2016-03-07 Thread Delbert Martin 
Trying to enable PRUs and set P8 45,46 to output just to test some IO 
toggle using R30 on PRU1
OVERLAY: project-00A0.dts:
/dts-v1/;
/plugin/;
/{
compatible = "ti,beaglebone","ti,beaglebone-black";
part-number = "project";
version = "00A0";

exclusive-use = 
"P8.45",
"P8.46";
fragment@0 {
target = <_pinmux>;
__overlay__ {
bone_project_pins: pinmux_project_pins {
pinctrl-single,pins=<0x0a0 0x05 0x0a4 0x05>;
};
};
};
fragment@1 {
target = <>;
__overlay__ {
project {
compatible = "bone-pinmux-helper";
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_project_pins>;
};
};
};
fragment@2 {
target = <>;
__overlay__ {
status = "okay";
};
};
};

/sys/devices/platform/bone-capemgr/slots:
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
 5: P-O-L-   0 Override Board Name,00A0,Override Manuf,project

>From /sys/kernel/debug/pinctrl/44e10800.pinmux/pins
...
pin 40 (44e108a0.0) 0008 pinctrl-single 
pin 41 (44e108a4.0) 0008 pinctrl-single 
pin 42 (44e108a8.0) 0008 pinctrl-single 
pin 43 (44e108ac.0) 0008 pinctrl-single 
...

Just saying I would expect these to be set to 0x05 instead of 0x00, 
Stranger yet, I'm sure there is some kind of non-obvious reason that in the 
overlay file, you reference the pin as offset 0x0a0/0x0a4 when their real 
offsets are 0x44310800... wait, i see it there.. nevermind. 
anyway should pins be showing the value of 8 instead of 5?



-- 
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] USB to Ethernet not working after updating custom kernel.

2016-03-07 Thread vamsi krish 
Hello,

After updating with custom kernel, BBB is able to boot but USB-Ethernet is 
not working... 

any one please provide solution to solve this issues.


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.

Re: [beagleboard] Custom LCD on BB-G on Debian 7.9 (2015-11-12)

2016-03-07 Thread Robert Nelson 
On Mon, Mar 7, 2016 at 10:59 AM,   wrote:
> I've spent more than a day now trying to get a custom LCD cape to work with
> the latest BB-G Debian distribution (7.9, 3.8.13) and can't say I've really
> made any progress though I have learned a few things.
>
> The LCD is wired to be compatible with the 4D systems LCD7 though without
> the touchscreen, buttons, or LEDs.  If I enable BB-BONE-LCD7-01:00A3 on boot
> then I get a mouse pointer in the middle of the screen but this slowly fades
> to a completely black screen.  I was encouraged by this and figured I just
> had to change the timings in the device tree to match my specific LCD.
>
> I downloaded the overlay sources from github/bb.org-overlays and as a test
> just copied BB-BONE-LCD7-01-00A3.dts to BB-BONE-LCD7-01-00A7.dts, changed
> the version string, compiled (with the updated dtc), installed, enabled
> (uEnv.txt) and rebooted.  The overlay actually fails to load with a
> complaing that gpio0 is undefined.  This is just a hint that things aren't
> going to go well.  The gpio0 reference is for one of the buttons which I
> don't need.  I tried removing the entries for the touchscreen and buttons
> but then I just get complains that the 'display-timings' node is missing.
>
> The bottom line is that it doesn't appear that the device tree sources at
> https://github.com/beagleboard/bb.org-overlays are built to work correctly
> with my kernel.  In fact the notes at the bottom of the page all talk about
> 4.1 and no mention of 3.8.  Are there corresponding sources for the 3.8
> kernel or am I better off loading a 4.1 image?  I'd prefer to stay with 3.8
> as I have other hardware in this project that requires a driver that I
> haven't tried yet with 4.1 but I'm willing to try if that's the best way.

That repo is 4.1 only,

You can grab the 3.8 version from:

https://github.com/beagleboard/linux/tree/3.8/firmware/capes

Regards,

-- 
Robert Nelson
https://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] Custom LCD on BB-G on Debian 7.9 (2015-11-12)

2016-03-07 Thread mfallavol 
I've spent more than a day now trying to get a custom LCD cape to work with 
the latest BB-G Debian distribution (7.9, 3.8.13) and can't say I've really 
made any progress though I have learned a few things.

The LCD is wired to be compatible with the 4D systems LCD7 though without 
the touchscreen, buttons, or LEDs.  If I enable BB-BONE-LCD7-01:00A3 on 
boot then I get a mouse pointer in the middle of the screen but this slowly 
fades to a completely black screen.  I was encouraged by this and figured I 
just had to change the timings in the device tree to match my specific LCD.

I downloaded the overlay sources from github/bb.org-overlays and as a test 
just copied BB-BONE-LCD7-01-00A3.dts to BB-BONE-LCD7-01-00A7.dts, changed 
the version string, compiled (with the updated dtc), installed, enabled 
(uEnv.txt) and rebooted.  The overlay actually fails to load with a 
complaing that gpio0 is undefined.  This is just a hint that things aren't 
going to go well.  The gpio0 reference is for one of the buttons which I 
don't need.  I tried removing the entries for the touchscreen and buttons 
but then I just get complains that the 'display-timings' node is missing.

The bottom line is that it doesn't appear that the device tree sources 
at https://github.com/beagleboard/bb.org-overlays are built to work 
correctly with my kernel.  In fact the notes at the bottom of the page all 
talk about 4.1 and no mention of 3.8.  Are there corresponding sources for 
the 3.8 kernel or am I better off loading a 4.1 image?  I'd prefer to stay 
with 3.8 as I have other hardware in this project that requires a driver 
that I haven't tried yet with 4.1 but I'm willing to try if that's the best 
way.

Just hoping for a little insight before I spend another day going down the 
wrong path.

  -- Mike

-- 
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 get custom LCD to work on BB-G and latest Debian 7.9 (2015-11-12)

2016-03-07 Thread mfallavol 
I've spent a couple of days on this and can't say I've made any progress. 
 I have a custom LCD cape modeled after the 4D-Systems LCD7.  It has the 
same LCD connections, just doesn't have the touchscreen, leds or buttons 
(and no Enable line either).

If I enable BB-BONE-LCD7-01:00A3 I get a single screen worth of data, 
sometimes just the mouse pointer, sometimes the touch screen calibration 
but regardless of what it is, it fades away to either black or to a 
half-white / half-black screen.  I was encouraged by this and figured I 
just had to change the timings in the device tree to make it work.

I downloaded the latest overlays from git (bb.org-overlays) but what I've 
found is that if I simply copy BB-BONE-LCD7-01-00A3.dts to 
BB-BONE-LCD7-01-00A7.dts, change the version string in it from A3 to A7, 
rebuild, install and activate at boot (changing uEnv.txt) it won't load.

The error in dmesg is: of_resolve: Could not find symbol 'gpio0'.  This in 
and of itself is no big deal because the entry in question is for the 
'Enter' button which I don't need.  In fact I've removed the device tree 
entries for the touchscreen and the button GPIOs but that just shows other 
issues.  Significantly, I get complaints that the 'display-timings' node is 
missing, which it is not.

The bottom line is that the device tree sources in git bb.org-overlays are 
obviously not the ones compiled into the 7.9 distribution or I'm missing 
something.  The notes at https://github.com/beagleboard/bb.org-overlays 
only mention the 4.1 kernel.  Is there another source or branch for the 3.8 
kernel?.  I'd prefer the 3.8 kernel because this is just one component of a 
project that includes using other hardware and a driver that I don't yet 
have working on 4.1 but if I need to update to 4.1 then so be it.

I'm just looking for a little guidance before I spend even more time going 
down the wrong path.

Thanks.

   -- Mike Fallavollita

-- 
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] BBG fried. Hint needed to undestand why.

2016-03-07 Thread Jordi Segura 
No, no magic jack plugged in :)

El dilluns, 7 març de 2016 14:18:30 UTC+1, lazarman va escriure:
>
> You didn't have a magic jack plugged in did you? 
>
> Sent from Yahoo Mail on Android 
> 
>
> On Sun, Mar 6, 2016 at 6:11 PM, Jordi Segura
>  wrote:
>
> My BBGreen got fried (when I power it up it just dims once the power led 
> and that's all it does). 
>
>
>   an someone explain me what I did wrong so it won't happen to me or 
> others again? 
>
>
> Explanation of what I did: The BBG died after several days working 24/7, 
> powered up from a power supply 5V 2A, with an 3G usb dongle connected on 
> it, and (maybe that's my fault ...) I connected the Tx output of another 
> microcontroller to one Rx input of the BBG but also to one Rx input of a 
> BBB (I had both the BBG and the BBB receiving the same Tx signal from a 
> third micro)
> The same power supply was powering both systems (BBG and BBB) and I also 
> interconnected GNDs. The third micro sending the Tx signal was powered from 
> the BBB. BBB is working well so far. 
>
>
> Cheers. 
>
> -- 
> 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] BBG fried. Hint needed to undestand why.

2016-03-07 Thread Jordi Segura 
No, no magic jack plugged in :)

El dilluns, 7 març de 2016 14:18:30 UTC+1, lazarman va escriure:
>
> You didn't have a magic jack plugged in did you? 
>
> Sent from Yahoo Mail on Android 
> 
>
>
>

-- 
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: Finger touch/mouse left click stopped working on LCD Touchscreen 4DCape-70T for BeagleBoneBlack

2016-03-07 Thread Radovan Chovan 
cd /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0
cat in_voltage*

1. correct state:
456
2199
3258
3808
--
2. "stuck" state:
cat: in_voltage4_raw: Resource temporarily unavailable
cat: in_voltage5_raw: Resource temporarily unavailable
cat: in_voltage6_raw: Resource temporarily unavailable
cat: in_voltage7_raw: Resource temporarily unavailable


-- 
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 and resistiv touchscreen

2016-03-07 Thread Radovan Chovan 
Same issue here:
https://groups.google.com/forum/#!searchin/beagleboard/finger$20touch/beagleboard/yBofgnpHd5I/J-NgrW9VAAAJ

Dňa štvrtok, 11. júla 2013 23:26:45 UTC+2 kay...@gmail.com napísal(-a):
>
> Does anybody have experience of using touchscreen with BBB? Does it works 
> fine?
> I got a strange problem with Debian, 7" TFT  and touchscreen. I attached 
> it as per LCD7 cape schematics and at  the first look it works well.
> But, time to time, TS stop working - no ADC interrupts is generated and 
> only reboot helps. Any ideas are welcome.
>
> Sergey
>
>

-- 
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] BBG fried. Hint needed to undestand why.

2016-03-07 Thread 'Mark Lazarewicz' via BeagleBoard 
You didn't have a magic jack plugged in did you? 

Sent from Yahoo Mail on Android 
 
  On Sun, Mar 6, 2016 at 6:11 PM, Jordi Segura wrote:   
My BBGreen got fried (when I power it up it just dims once the power led and 
that's all it does). 





  an someone explain me what I did wrong so it won't happen to me or others 
again? 





Explanation of what I did: The BBG died after several days working 24/7, 
powered up from a power supply 5V 2A, with an 3G usb dongle connected on it, 
and (maybe that's my fault ...) I connected the Tx output of another 
microcontroller to one Rx input of the BBG but also to one Rx input of a BBB (I 
had both the BBG and the BBB receiving the same Tx signal from a third micro)
The same power supply was powering both systems (BBG and BBB) and I also 
interconnected GNDs. The third micro sending the Tx signal was powered from the 
BBB. BBB is working well so far. 





Cheers.


-- 
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] Debian img 8.3 lxqt boot indefinitely on some BBB

2016-03-07 Thread mpsoft . ch 
Hello,
After installing the bone-debian-8.3-;xqt-4gb-armhf-2016-01-24-4gb.img on a 
SD card, I'm able to boot this image on some BBB.
But on some other BBB, the boot process start with some text on the display 
(4DCAPE-70T) and suddently reboot, and this indefinitely...
What can be the problem please, in particular, what is the cause that the 
BBB reboot indefinitely?

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