[beagleboard] Debian 9.1.0 with VirtualBox unable to "sudo apt-get install crossbuild-essential-armhf"

[Patrick Ireland]

I am attempting to install the Debian 9.1.0 system to support 
BeagleBoneBlack on my Windows 10 system.

I am following the Derek Molloy blog site and until I tried to load the 
"sudo apt-get install libicu-dev:armhf", everything was moving smoothly 
(within limits of my Linux knowledge).

http://exploringbeaglebone.com/chapter7/

However, the step to install the libraries fails.

"Some packages could not be installed. This may mean that you have 
requested an impossible situation or if you are using the unstable 
distribution that some required packages have not yet been created or been 
moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libicu-dev:armhf : Depends : libc6-dev:armhf but it is not going to be 
installed or libc-dev:armhf"

This message leads me to believe that the libicu-dev:armhf is not available 
with Debian 9.1.0 (Stretch).

Am I doing something wrong or is cross library linking not supported on 
Debian 9.1.0 yet?

Assuming that it is not yet supported, any expected date for availability?

Is my only viable solution to reload using Jessie?

TIA,

Pat





-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/af7590d6-51ea-4da0-a83b-fca0850d684b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Looking for Fritzing drawing for BeagleBone Blue

[Michael Caughey]

This contains the library file for Eagle Cad:
https://github.com/jadonk/beaglebone-blue/tree/master/EAGLE

On Thursday, July 27, 2017 at 8:30:07 AM UTC-4, Mark A. Yoder wrote:
>
> Has anyone created a Fritzing drawing for the Blue?  I'm planning on using 
> the Blue in my class this fall and it's time to start writing the 
> instructions.
>
> --Mark
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/08babab6-8147-4805-bc9d-dd9e1d0a267f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Blue booting as Robot controller vs. booting as Linux computer

[Mark A. Yoder]

I'm missing a "Big Picture" idea here.  Let's see if I can ask with right 
questions.

How can I tell with device tree file my Bone is booting with?
Where can I find it's source?
How do I compile and install it?

Right now I'm trying to get a st7735 SPI-based LCD display working again on 
my Black.  This[1] used to work, but the make no longer works.
What do I need to do so this:
config-pin -a P9_30 spi # Data out
config-pin -a P9_31 spi # Clock 
will work?  First I want it to work on the Black, then on the Blue.

--Mark

[1] 
https://github.com/MarkAYoder/BeagleBoard-exercises/blob/master/displays/st7735/install.sh
 

On Saturday, August 5, 2017 at 12:16:29 PM UTC-4, Hugh Briggs wrote:
>
> I found Jason's hint to be a bit short on explanations, so here is what 
> Robert Nelson led me through. It is was I reported that I did with a BBB + 
> Robotic Cape but didn't know if it would work with a Blue. I take Jason's 
> answer to be yes it will work with a Blue.
> On July 11 Robert wrote in my earlier email stream titled "where is 
> capemgr?"
>
> It's not a service file, it's the device tree binary: 
>
>
> https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x-boneblack-roboticscape.dts#L19
>  
>
> Change: 
>
> #include "am335x-bone-common-no-capemgr.dtsi" 
>
> to: 
>
> #include "am335x-bone-common.dtsi"
>
> He also led me through how to compile it and boot it, etc. I won't try to 
> repeat that here from memory.
> Then do the usual capemgr boot line directive with partno=BB-ADC
>
> I still believe that this configuration can live with the rc_* apps and 
> services, as long as you only use one at a time.
> Turns out we haven't been hearing from James (the rc_* creator) on this 
> because he is way way way out of the county for the summer.
> Clark
>
>
>
> On Thursday, August 3, 2017 at 9:25:18 PM UTC-7, Jason Kridner wrote:
>>
>>
>>
>> On Aug 3, 2017, at 4:57 PM, Mark A. Yoder  wrote:
>>
>> Sounds like a good idea.  How do I turn on the ADC drivers?
>>
>>
>>
>> https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x-boneblack-custom.dts#L56
>>
>>
>> --Mark
>>
>> On Thursday, August 3, 2017 at 2:45:44 PM UTC-4, Jason Kridner wrote:
>>>
>>>
>>>
>>> On Aug 3, 2017, at 2:32 PM, Mark A. Yoder  wrote:
>>>
>>> It looks like when the Blue comes out of the box, running a current 
>>> image it's all set up to run the Robotics stuff. You can access the ADCs, 
>>> servos, etc. through the robot interface.
>>>
>>> When I teach my Embedded Linux class I would also like my students to 
>>> access the ADCs, PWM, etc in the Linux way.  
>>>
>>> *How do I configure the Blue to boot up in "Embedded Linux" mode rather 
>>> than "Robot Linux" mode*?
>>>
>>>
>>> If we get the integration right, IMO, we'll boot up so that we can use 
>>> the Linux userspace interfaces and the libroboticscape interfaces. The 
>>> libroboticscape setup should do whatever is needed to disable Linux kernel 
>>> drivers at runtime in order to enable its userspace accesses. 
>>>
>>> Turn on the ADC kernel drivers and look how libroboticscape fails. Then, 
>>> report that as a bug. 
>>>
>>>
>>>
>>> --Mark
>>>
>>>
>>> On Wednesday, August 2, 2017 at 11:15:40 AM UTC-4, Mark A. Yoder wrote:

 It sounds like I can either have a Blue that boots as a robot, or boots 
 as an embedded processor, but not both at the same time.
 I need to see what it would take to remove the ADC from the robots 
 control.

 --Mark

 On Tuesday, August 1, 2017 at 4:57:09 PM UTC-4, Hugh Briggs wrote:
>
> I have lived on BBB + Robotics Cape in James' world for some time. 
> While I haven't done this with a Blue, I suspect what I did can work 
> there 
> too. I did do his installation (for a Rev C BBB and a Rev D Robotics 
> Cape). 
> With Robert's help I put the Capemgr back in the DTs and added the 
> capemgr 
> partno boot line for BB-ADC.  This seems to be a workable combination of 
> the two worlds. My premise is that I don't try to do both at once.  That 
> is, I don't run any of the rc_* apps or services while trying to read the 
> ADCs from /sys/bus/iio. So far it seems to work for me.
> Hugh
>
> On Monday, July 31, 2017 at 11:44:09 AM UTC-7, Mark A. Yoder wrote:
>
>> Yup, this is the Blue.
>> In there short term is there an easy way to turn off the robotics 
>> stuff and get easy access to the analog in?
>>
>> In the long term, what will it take to convert James' robot stuff to 
>> libiio?  I might take a shot at it if it isn't too hard.
>>
>> --Mark
>>
>> On Friday, July 28, 2017 at 5:56:30 PM UTC-4, RobertCNelson wrote:
>>>
>>> On Fri, Jul 28, 2017 at 4:40 PM, Mark A. Yoder  
>>> wrote: 
>>> > How do I read AIN on the latest images?  I don't know where to 
>>> find it in 
>>> > /sys/ 
>>>
>>> Hi Mark, 

[beagleboard] Re: "What Was I Thinking" and Learning How Sensors Might Work/Seth

[Mala Dies]

Hello Mr. Dennis,

I am going over the book, "Programming the BeagleBone Black," (Monk 2014) 
and I found on page 110 a TMP36 software example with relating a P9 Header 
layout/diagram. I think I am connecting things correctly. I have done this 
example before but currently I am having trouble with the 2GB BBB and 
Debian Stretch.

Seth

P.S. I am trying to read a TMP36 temp. sensor to tell me Celsius and 
Fahrenheit on my command prompt. 

On Thursday, August 10, 2017 at 9:26:54 AM UTC-5, Dennis Lee Bieber wrote:
>
> On Thu, 10 Aug 2017 01:48:41 -0700 (PDT), Mala Dies 
>  declaimed the following: 
>
> >Hello, 
> > 
> >Okay... 
> > 
> >TMP36 to BBB: 
> > 
> >Pin 3 to 3.3v 
> > 
> >Pin 2 to P9_40 (GPIO/Analog) 
> > 
> >Pin 1 to P9_34 (GND_ADC/Low noise GND) 
> > 
> >I think this should help. I am making a temperature sensor tell me what 
> the 
> >temp. is inside for now. 
> > 
>
> You still haven't answered the real question: why did you choose 
> THAT 
> set of connections? 
>
> In my library, four (out of seven) Beaglebone books and two (out 
> of 
> nine) Arduino books used the TMP36 (a few others used the LM35 which has a 
> similar pin-out but different sensor range). I also downloaded the spec 
> sheet from your earlier post. 
>
> NONE of these books show anything similar to your proposed 
> connections. 
> -- 
> Wulfraed Dennis Lee Bieber AF6VN 
> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/30e398f0-7da8-4ab7-bda3-057bb93049ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: My overlay can't find clk_mcasp0

[Mike Davis]

I managed to get this working, thanks to a post on the alsa-devel forum:
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-September/098022.html

By loading the overlay *before* the sound drivers, rather than after it now 
works.
from /boot/uEnv.txt:
##Example v4.1.x
#cape_disable=bone_capemgr.disable_partno=
cape_enable=bone_capemgr.enable_partno=BB-BONE-AUDI-02


On Wednesday, August 9, 2017 at 3:27:56 PM UTC-4, Mike Davis wrote:
>
> I have the same issue.
> I am running kernel debian with kernel 4.4.52-bone16
> I pulled down RobertCNelson's dtb-rebuilder from 
> https://github.com/RobertCNelson/dtb-rebuilder 
> ,
>  
> branch 4.4.x and rebuilt all the arm dtbs and installed them.
> Then added then updated my *base* dtb, which 
> is am335x-boneblack-emmc-overlay.dtb with the clock definitions 
> in am335x-boneblack-audio.dts, 
> as per 
> https://github.com/RobertCNelson/dtb-rebuilder/blob/4.1-ti/src/arm/am335x-boneblack-audio.dts#L17-L28
>  
> 
>
> Reboot, then install the audio: sudo sh -c "echo BB-BONE-AUDI-02 > 
> /sys/devices/platform/bone_capemgr/slots"
>
> All seems ok in dmesg:
> [  411.768801] bone_capemgr bone_capemgr: part_number 'BB-BONE-AUDI-02', 
> version 'N/A'
> [  411.768866] bone_capemgr bone_capemgr: slot #4: override
> [  411.774250] bone_capemgr bone_capemgr: Using override eeprom data at 
> slot 4
> [  411.774295] bone_capemgr bone_capemgr: slot #4: 'Override Board 
> Name,00A0,Override Manuf,BB-BONE-AUDI-02'
> [  411.811080] bone_capemgr bone_capemgr: slot #4: dtbo 
> 'BB-BONE-AUDI-02-00A0.dtbo' loaded; overlay id #0
>
> but speaker-test and aplay both fail with:
> [ 2632.788052] davinci-mcasp 48038000.mcasp: stream has more channels (2) 
> than are enabled in mcasp (0)
> [ 2632.788110] davinci-mcasp 48038000.mcasp: ASoC: can't set 
> 48038000.mcasp hw params: -22
>
>
> On Wednesday, July 19, 2017 at 12:21:09 PM UTC-4, engka...@gmail.com 
> wrote:
>>
>> This might be an old thread but I got a question. I was able to compile 
>> and load the modified device tree. I then loaded my overlay for the audio. 
>> I built this circuit base from 
>> http://elinux.org/CircuitCo:Audio_Cape_RevB. The only difference with 
>> mine is that I am using I2C1. I can see the it is using address 0x18 dmesg 
>> has:
>> [  135.176315] asoc-simple-card sound: tlv320aic3x-hifi <-> 
>> 48038000.mcasp mapping ok
>>
>> However, when I call on the speaker-test, this error appears: 
>>
>>
>> Unable to set hw params for playback: Invalid argument
>> Setting of hwparams failed: Invalid argument
>>
>> Checking dmesg:
>> [  617.051387] davinci-mcasp 48038000.mcasp: stream has more channels (2) 
>> than are enabled in mcasp (0)
>> [  617.051781] davinci-mcasp 48038000.mcasp: ASoC: can't set 
>> 48038000.mcasp hw params: -22
>>
>> Has anyone encountered the same problem?
>>
>>
>>
>>
>> On Monday, April 4, 2016 at 5:48:01 PM UTC+8, Rick M wrote:
>>>
>>> I'm trying to get my audio cape to work (which is nearly identical to 
>>> the cape that was available for sale). I've had it working to some level of 
>>> success with past kernels (3.1.18), but now I'm on 4.4.6. My existing DTS 
>>> didn't work, so I'm looking at how the BB-BONE-AUDI-02 DTS is written. 
>>>
>>> One of the differences is that it doesn't explicitly call out the McASP 
>>> clock frequency like the older one did. Instead, it seems to refer to 
>>> clk_mcasp0. But when I copy the same code into my DTS, I get: 
>>>
>>> [  103.180866] of_resolve_phandles: Could not find symbol 'clk_mcasp0' 
>>> [  103.187269] bone_capemgr bone_capemgr: slot #4: Failed to resolve 
>>> tree 
>>>
>>> I found it defined by grepping /boot/dtbs. It's in 
>>> /boot/dtbs/4.4.6-bone-rt-r6/am335x-abbbi.dtb. Where can I find the source 
>>> files for these DTBs? 
>>>
>>> Is this dtb part of what's loaded by default in 4.4.6-bone-rt-r6? If 
>>> not, can I copy the definition into my 
>>>
>>> FWIW, here's my DTS and some output from dmesg: 
>>> http://pastebin.com/niDkWdWV 
>>>
>>> Thanks, 
>>>
>>>
>>> -- 
>>> Rick Mann 
>>> rm...@latencyzero.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/bb4cb2e9-6c2b-46f4-874f-cc0af41b5ad9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unable to manually load dtbo to bone_capemgr slots

[Robert Nelson]

On Thu, Aug 10, 2017 at 8:11 AM, Marco Thome  wrote:
> Hi,
>
> I started Reading about dts files a few days ago and wrote my own to set
> P8.42, P8.43, P8.44 and P8.46 as gpio outputs. I compiled it and tried to
> echo it to /sys/devices/platform/bone_capemgr/slots, but I get no response
> (my terminal just stops).
>
> Here's what I get on dmesg's last lines:
> [  407.020467] bone_capemgr bone_capemgr: part_number 'bb-gpio', version
> 'N/A'
> [  407.020531] bone_capemgr bone_capemgr: slot #4: override
> [  407.033061] bone_capemgr bone_capemgr: slot #4: auto loading handled by
> U-Boot

"auto loading handled by U-Boot" see the directions here:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYggxez4UAUY3GnWtv8kThMnTDE91C7mFW_ocodYXzbgnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to manually load dtbo to bone_capemgr slots

[Marco Thome]

Hi,

I started Reading about dts files a few days ago and wrote my own to set 
P8.42, P8.43, P8.44 and P8.46 as gpio outputs. I compiled it and tried to 
echo it to /sys/devices/platform/bone_capemgr/slots, but I get no response 
(my terminal just stops).

Here's what I get on dmesg's last lines:
[  407.020467] bone_capemgr bone_capemgr: part_number 'bb-gpio', version 
'N/A'
[  407.020531] bone_capemgr bone_capemgr: slot #4: override
[  407.033061] bone_capemgr bone_capemgr: slot #4: auto loading handled by 
U-Boot

And here's my custom dts:

/dts-v1/;
/plugin/;
/ {
 compatible = "ti,beaglebone", "ti,beaglebone-black";
 /* identification */
 part-number = "bb-gpio";
 version = "00a0";
 /* state the resources this cape uses */
 exclusive-use =
 "P8.42",
 "P8.43",
 "P8.44",
 "P8.46",
 "gpio2_11",
 "gpio2_8",
 "gpio2_9",
 "gpio2_7";
 fragment@0 {
  target = <_pinmux>;
  __overlay__ {
   bb_gpio_pins: pinmux_bb_gpio_pins {
pinctrl-single,pins = <
0x0b4 0x0f /* P8_42 GPIO2_11 */
0x0a8 0x0f /* P8_43 GPIO2_8 */
0x0ac 0x0f /* P8_44 GPIO2_9 */
0x0a4 0x0f /* P8_46 GPIO2_7 */
>;
   };
  };
 };
 fragment@1 {
  target = <>;
  __overlay__ {
   bbgpio : gpio {
pinctrl-names = "default";
pinctrl-0 = <_gpio_pins>;
status = "okay";
/*oe {
 gpio-name = "oe";
 gpio = < 11 0x00>;
 output;
};
clk {
 gpio-name = "clk";
 gpio = < 8 0x00>;
 output;
};
le {
 gpio-name = "le";
 gpio = < 9 0x00>;
 output;
};
sdi {
 gpio-name = "sdi";
 gpio = < 7 0x00>;
 output;
};*/
   };
  };
 };
};


I tried upgrading kernel (right now, *uname -a* returns: Linux arm 
4.9.41-ti-r53 #1 SMP PREEMPT Thu Aug 10 02:34:57 UTC 2017 armv7l 
GNU/Linux), disabling audio/vídeo/wireless/adc overlays, enabling/disabling 
cape_universal, loading internet dtbos (from kilobaser 
and
 
bbbadventures ) 
and default ones (like cape-universaln) and changing boards (I have 2 BBBs) 
and installing bb-cape-overlays through apt-get

I think I'm missing something really stupid, because I found nothing 
regarding this kind of error so far.
If I try to load the dtbos on boot through uEnv.txt, my board stops with 
the 4 user leds lit, which I understand as a signal that my BBB is not 
loading the OS. Of course, I can't ssh it.

What am I missing?

Best regards,
Marco

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d7b3a25d-e723-4fa2-ab46-2eb014a10bbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BeagleBone Black - No HDMI Output

[achu4798]

Hello,

I am using Beagle bone Black Rev C with 7.11 image and I have connected the 
device to LCD monitor using micro HDMI to HDMI cable. Before it was working 
fine but suddenly it started showing blank screen.
I tried various steps:

1) reflashed the device 
2) parse-edid edid to check about monitor 
3) did xrandr --verbose with 1024x720@60 as well as 50 rate and changed the 
same in /boot/uEnv.txt
4) saw about the device connection also in /proc/cmdline also.
Everything was normal as before but it did is showing blank screen.

Please someone help me with this one.

By the way I am using sony Ericson HDMI cable. So, the use of low quality 
is outdated.


Gerald and Robert I am following this thread for past 2-3 days continously 
and tried almost all the steps in the comments but no use. Someone help me 
with this.



Thanks in advance

Regards,
Ashwin


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b5461e3d-2138-49cd-bc3d-b27e2a0e9622%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Enabling SPI1 on BBGW via DeviceTree (no capemanager)

[martti . kuutti]

I have same problems with SPI1. Guilty part seems to be wl18x that requires 
pulldown on certain pin. See /opt/source/dtb-4.4-ti/src/arm/
am335x-bonegreen-wl1835.dtsi
 (included by am335x-bonegreen-wireless.dts). Last fragment introduces 
gpio-hog of pin p9.30.  I've tried to enable SPIDEV1 on boot which leads to 
wilink crashing on init. 
Comment on file shows that it is somehow related to BT_AUD which I dont 
need but I need wlan and bluetooth. I dont know if that is hardwired or not 
but changing that hog-pin to another was NOT good idea... 

So I need to re-route my wirings to SPI0 (which overlaps my I2C-2...) so 
i'll be quite busy for a while...

Please inform here if solution is found. 

perjantai 23. kesäkuuta 2017 18.33.16 UTC+3 mjbo...@gmail.com kirjoitti:
>
> Problem "solved" (worked around really) by switching to SPI0, changing the 
> pins around and rerouting most of our custom cape.
> There are still some problems with the SPI bus but that's a separate issue.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/609ca62e-16f4-40bb-b83d-2ff681dbb769%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to manually load any dtbo to slots

[Marco Thome]

Hi,

I started reading abou dts files a few days ago and wrote one to change the 
lasts P8 pins' mode, but I can't load my dtbo to 
*/sys/devices/platform/bone_capemgr/slots* with *echo*. Everytime I do 
that, my terminal gets no response and I get stuck (even ctrl + C does not 
work).
I tried disabling other capes like HDMI on *uEnv*, upgrading kernel, 
changing pinmode through *config-pin* (which returns no file/directory 
error), changing boards (I have access to a few BBBs), disabling/enabling 
universal cape and loading internet capes (from kiloblaser 
,
 
bbbadventures ) 
and default ones (like cape-universaln). I ought to think it must be 
something really stupid I'm missing, because I found nothing regarding this 
kind of error so far.

My custom dts:

/dts-v1/;
/plugin/;
/ {
 compatible = "ti,beaglebone", "ti,beaglebone-black";
 /* identification */
 part-number = "bb-gpio";
 /*version = "00A0";*/
 /* state the resources this cape uses */
 exclusive-use =
 "P8.42",
 "P8.43",
 "P8.44",
 "P8.46",
 "gpio2_11",
 "gpio2_8",
 "gpio2_9",
 "gpio2_7";
 fragment@0 {
  target = <_pinmux>;
  __overlay__ {
   bb_gpio_pins: pinmux_bb_gpio_pins {
pinctrl-single,pins = <
0x0b4 0x0f /* P8_42 GPIO2_11 */
0x0a8 0x0f /* P8_43 GPIO2_8 */
0x0ac 0x0f /* P8_44 GPIO2_9 */
0x0a4 0x0f /* P8_42 GPIO2_7 */
>;
   };
  };
 };
 fragment@1 {
  target = <>;
  __overlay__ {
   bbgpio : gpio {
pinctrl-names = "default";
pinctrl-0 = <_gpio_pins>;
status = "okay";
/*oe {
 gpio-name = "oe";
 gpio = < 11 0x00>;
 output;
};
clk {
 gpio-name = "clk";
 gpio = < 8 0x00>;
 output;
};
le {
 gpio-name = "le";
 gpio = < 9 0x00>;
 output;
};
sdi {
 gpio-name = "sdi";
 gpio = < 7 0x00>;
 output;
};*/
   };
  };
 };
};

Last lines of dmesg:
[   64.071193] pru-rproc 4a334000.pru0: PRU rproc node 
/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a334000 probed successfully
[   64.090943] remoteproc remoteproc2: 4a338000.pru1 is available
[   64.091062] pru-rproc 4a338000.pru1: PRU rproc node 
/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a338000 probed successfully
[  321.616414] bone_capemgr bone_capemgr: part_number 'bb-gpio', version 
'N/A'
[  321.616478] bone_capemgr bone_capemgr: slot #4: override
[  321.630993] bone_capemgr bone_capemgr: slot #4: auto loading handled by 
U-Boot

uname -a (right now):
Linux arm 4.9.41-ti-r53 #1 SMP PREEMPT Thu Aug 10 02:34:57 UTC 2017 armv7l 
GNU/Linux

pinctrl pins (71 ~ 75):
pin 71 (PIN71) 44e1091c  pinctrl-single
pin 72 (PIN72) 44e10920  pinctrl-single
pin 73 (PIN73) 44e10924  pinctrl-single
pin 74 (PIN74) 44e10928  pinctrl-single
pin 75 (PIN75) 44e1092c 0030 pinctrl-single


Can anyone point out what I may be missing?

Best regards,
Marco

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/334bf1ec-5a4c-43da-821f-00802abec5ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Black - No HDMI Output

[achu4798]

>
> Hello,
>
>
I am Ashwin. I am using BeagleBone black with 7.11 wheezy image. Earlier I 
was using it by connecting to LCD monitor it was working before but 
suddenly it started to show blank screen.  I have been following this 
thread since then and I have followed almost all the steps in these 
comments. 
I have done

1) Reflashed the device
2) checked about the monitor in parse-edid edid it showed correctly 
3) xrandr --verbose to 1024x720@60 as well as 50 rate and set the same in 
/boot/uEnv.txt also
4) checked the hdmi status in sys/class/graphics/fb0/device/status also it 
was showing connected also.


Please Gerald/Robert help me with this issue.


Thanks in Advance


Regards,
Ashwin

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/36d333ef-5cca-4673-8e23-be9c3f8e0ab1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BeagleBone Black - No HDMI Output

[achu4798]

>
> Hello Gerald,
>

I am Ashwin. I am using Beaglebone Black with 7.11 wheezy image with LCD 
monitor. Previously it was working fine.but suddenly it started to show 
blank screen. I have been following the thread about the HDMI issue in BBB 
closely and followed almost all the steps suggested by everyone but no use. 
I am still having the issue. 

I have done checking about the 
1) status of the device connected to hdmi port
2) parse-edid edid
3) changed the screen resolution and frame rate using xrandr as well as in 
/boot/uEnv,txt 
4) Even reflashed 2 times but no use.

I require your help with this one. Can you suggest me any other solution?


Thanks in Advance,
Regards,
Ashwin

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4fc70b84-70c6-4478-88b8-1d9a1e82ec58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] beaglebone rev B i2c

[herve . lebreton11]

Hello All,

We are using BBB for some years now for our product . Some month ago due to 
the new revision of BBB we had to switch the base image from debian 7.9 to 
debian 8.6 IoT (from beagleboard.org) . so far everything ok with any type 
of rev C BBB .. We tried to update an older BBB which is of revision B and 
then got some issues with i2c , i2c-1 and i2c-2 do not work anymore .

Our way of working with emmc is to burn an entire image onto it.

I checked dmesg on both revision and besides the timeout I get when trying 
to access i2c-1 and i2c-2 , I got the same initialisation messages 
concerning i2c.

When I do i2cdetect -r -y 1 , it is slow and do not show any device adress 
(plus some timeout messages in dmesg) .

So question is , what is the difference between rev C and B in terms of i2c 
configuration ? (beside the fact that the name of the device has been 
switched but this should not be an issue here)

Any advice , idea welcome.

Thanks,

Hervé.





-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f5c7b20f-edfa-4a57-a971-068eac0c545c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Voltage Range 5V +/-

[Fohnbit]

Hello Graham,

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/8c74f35e-5da2-46e3-b32d-c4bd093eb785%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Voltage Range 5V +/-

[Graham]

The USB specification requires that it will operate between 4.5 and 5.5 
Volts.

For the 5 Volt power jack, the PMIC will operate between 4.5 and 5.5 Volts.
BUT, the PMIC will shut down and go into self protection above or below
those Voltages.  So, in order to allow for some noise and Voltage spikes,
so that you have margin against the shut down points, I recommend that
you operate the Power Jack and USB between 4.75 and 5.25 Volts.

Physical damage will not occur until at least 7 Volts, but it will self 
protect
(turn itself off) starting at 5.50 Volts

If you question has to do with running the BBB from batteries, I suggest 
that
you have an external boost/buck converter, so that the power to the 
BBB stays at a safe and comfortable 4.75 to 5.25 Volts, no matter what the
battery is doing.

--- Graham

==
On Thursday, August 10, 2017 at 1:43:05 AM UTC-5, Fohnbit wrote:
>
> Hello,
>
> which Range is supported at the USB and power jack input?
> 5V or cource ... but in which range before the board will be damaged?
> 4.5 - 5.5V ?
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f0bb8832-ff3c-4de4-aebb-1cfccf4a8cc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: "What Was I Thinking" and Learning How Sensors Might Work/Seth

[Mala Dies]

Hello Sir,

I cannot just run a .js file with sudo nodejs temp.js on my BBB. The issue 
pertains to nodejs not being installed or something. I went to the 
npmjs.org site and found bonescript and tried to start from there. I also 
tried nodejs.org to find info. on how to get it on the BBB. 

Seth

P.S. I am coming up short for some reason. I did some work with what the 
sites have listed at https://www.npmjs.com/package/bonescript 
and 
https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions.
 
If you or if anyone else is having trouble, please give some advice. 

On Wednesday, August 9, 2017 at 9:21:43 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Aug 9, 2017 at 8:53 PM, Mala Dies  
> wrote: 
> > Hello Again, 
> > 
> > Seth here. Um, node is not found on my version of stretch. I just tried 
> to 
> > run a .js file on the BBB and it replied to me saying that sudo: node: 
> is 
> > not a known command. What gives? Does anyone have an idea as to what is 
> > happening? 
>
> "nodejs" 
>
> (in debian an older binary package had already used the binary "node" 
> name..) 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1727b3fc-9726-4e0e-8094-ea7f3152602e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: "What Was I Thinking" and Learning How Sensors Might Work/Seth

[Mala Dies]

Hello,

Okay...

TMP36 to BBB:

Pin 3 to 3.3v

Pin 2 to P9_40 (GPIO/Analog)

Pin 1 to P9_34 (GND_ADC/Low noise GND)

I think this should help. I am making a temperature sensor tell me what the 
temp. is inside for now.

Seth

P.S. I appreciate you reaching out. Please let me know of what other info. 
I need to furnish. 

On Wednesday, August 9, 2017 at 10:31:40 PM UTC-5, Dennis Lee Bieber wrote:
>
> On Wed, 9 Aug 2017 18:47:22 -0700 (PDT), Mala Dies 
>  declaimed the following: 
>
>
> >...cough. 
> > 
> >Um, Why would I attach a male to male lead from 3.3v on the BBB to GND on 
> >the TMP36 sensor? 
> > 
> >Easier: 
> > 
> >*BBB* (3.3v) or P9_03 *to **TMP36* (GND) or Pin 3 
> > 
> >I think this is my question. Please try to answer with some type of 
> >understanding for me. 
> > 
>
> Since all of my crystal balls are in storage, I would have no 
> idea... 
> If you are trying this connection, you must have some reason for it. You'd 
> have to tell us your reasons for any particular wiring. 
>
> -- 
> Wulfraed Dennis Lee Bieber AF6VN 
> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4e66305d-0b3f-47a1-be60-7c14262c2a79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Voltage Range 5V +/-

[Fohnbit]

Hello,

which Range is supported at the USB and power jack input?
5V or cource ... but in which range before the board will be damaged?
4.5 - 5.5V ?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1463e147-f648-4b3e-92ca-71a55dd85bd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.