date:20160921

[beagleboard] Real-time support for Beaglebone using Yocto

2016-09-21 Thread nikesh patil

Hi,

I am using Beaglebone Platform and I want to build the linux kernel with 
real-time support in ti using Yocto.
In yocto, we can create a core-image-rt image, which has a rt support, but 
I am getting errors when I try to build a core-image-rt.
Whereas I am able to build core-image-console, core-image-sato, 
core-image-minimal, these images for beaglebone.

So is there any machine specific configuration, to build core-image-rt for 
beaglebone?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/cef5d054-168e-4b5c-8c18-e8fe1c40b1a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long

2016-09-21 Thread Viswadeep Sarangi

You're right. My BBB is a 2 GB eMMC model. And I know I have to boot from 
the SD card, at least for the time being. 
I did try your suggestion and tried older debain images anf flashed it to 
the eMMC, but it didn't work so I am okay with booting from the SD card, I 
think I'll buy a smaller sized SD card for this (about 4 GB) and use my 16 
GB SD card for some other purpose. 

Thank you.

SIncerely,
Viswadeep

On Thursday, 22 September 2016 06:40:59 UTC+5:30, Dennis Lee Bieber wrote:
>
> On Wed, 21 Sep 2016 08:18:56 -0700 (PDT), Viswadeep Sarangi 
> > declaimed the 
> following: 
>
> >I downloaded the image 
> >: 
> https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz
>  
> >from https://beagleboard.org/latest-images 
> > 
>
> Just take note that, if your BBB is a 2GB model, you CAN NOT FLASH 
> THIS 
> IMAGE -- that's why I had specified the older 2GB images for testing. 
> -- 
> 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/2356531c-bcdf-4296-8fa9-b1a4bb7d388e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] bbgw wlan0 users

2016-09-21 Thread Robert Nelson

Please test this image:

https://rcn-ee.net/rootfs/bb.org/testing/2016-09-21/iot/

Is wlan0 working better for you?

Remember, it's in tether mode at startup, so to connect to a differenet wifi:

sudo connmanctl
#connmanctl> tether wifi disable
#connmanctl> enable wifi
#connmanctl> scan wifi
#connmanctl> services
#connmanctl> agent on
#connmanctl> connect wifi_*_managed_psk
#connmanctl> quit

note, when not in tether mode, instead of doing:

sudo ifconfig wlan0 down

do:

sudo bb-wl18xx-wlan0-down

and instead of:

sudo ifconfig wlan0 up

do:

sudo bb-wl18xx-wlan0-up

For me it's still not 100% reliable when you take down the wlan0 and
then bring it up..

But it seems to work on hard reboots, soft reboot's..


1: 
https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-wlan0-down
2: 
https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-wlan0-up

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/CAOCHtYi6x_30R%2Bosns--YO9MNXjDGbc9nS2Cw8eQSTOhH3wqPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: How Flashing Now Works with Debian

2016-09-21 Thread Joshua S

THANKS The git pull saved me ! I couldn't get the correct loader files 
to save my life.

On Monday, July 14, 2014 at 10:50:20 AM UTC-7, RobertCNelson wrote:
>
> On Mon, Jul 14, 2014 at 12:29 PM,  > 
> wrote: 
> > Hi, 
> > 
> > I am getting as well the "Error: script halting, system unrecognized." 
> when 
> > executing beaglebone-black-eMMC-flasher.sh. 
> > The image I have flashed is from here 
> > http://elinux.org/BeagleBoardDebian#Flasher 
> > 
> https://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC-flasher-debian-7.5-console-armhf-2014-07-06-2gb.img.xz.
>  
>
> > When I check with "LC_ALL=C lsblk -l" the mountpoint "/boot/uboot" is 
> > missing. 
> > 
> > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT 
> > mmcblk1boot0 179:16 0 1M 1 disk 
> > mmcblk1boot1 179:24 0 1M 1 disk 
> > mmcblk0 179:0 0 7.4G 0 disk 
> > mmcblk1 179:8 0 1.8G 0 disk 
> > mmcblk1p1 179:9 0 96M 0 part 
> > mmcblk1p2 179:10 0 1.7G 0 part / 
> > 
> > Is there anything that I can do? 
> > What I want to do is clone a beaglebone black to multiple others, is 
> > beaglebone-black-eMMC-flasher.sh the best way to do that? 
> > Thanks in advance. 
>
> So in, 2014-07-06 i rewrote a lot of things... 
>
> First, make sure you run: 
>
> cd /opt/scripts/tools/ 
> git pull 
>
> Next open: /boot/uEnv.txt 
>
> Uncomment this line: 
>
> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v2.sh 
>
> At this point your microSD card is set to flash the eMMC.. so shutdown 
> (sudo halt) and get ready to flash stuff.. 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e50a2f57-f6a9-48a2-b1d0-95b50151613e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Fwd: AIX/Linux Admin (Production Support)

2016-09-21 Thread rani rautela

Hi

Hope you are doing fine. . !!!


*JOB DESCRIPTION*

*ROLE : *AIX/Linux Admin (Production Support)

*LOCATION : *Scottsdale, AZ / Woonsocket, RI

*CLIENT: *TCS

*Responsibilities:*

· L2 Production support, Incident triaging, Install ifix, apply
patches, manage file systems, monitor performance and troubleshoot alerts
from monitoring tools.

· System failure analysis and recovery; insuring the consistency
and integrity of file systems.

· Liaison with vendors/ customer for new hardware / software
install , technology upgrades and troubleshooting

· Technical support and day to day housekeeping activities – backup
,patching , user accounts etc

· Support 500+ servers in a 24x7x365 data center.

· Manage and lead hardware and software migration and upgrade
efforts of varying size and complexity.

· Willing to work in shifts – 24x7 environment , specially nights
and weekends




--

[image: cid:image001.jpg@01D0BE16.B9DD7240]



Nityo Infotech Corp.
666 Plainsboro Road,

Suite 1285



Plainsboro, NJ 08536



Rani Rautela

Recruiter

Desk:609-853-0818 ext 2145

Fax :   609 799 5746

mailto:rani.raut...@nityo.com 
www.nityo.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/CA%2B17Rv-ze4LwU_3is-hhSo-T1nibdUcj0noMz6WVC-5ZK2pR9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Where to purchase?

2016-09-21 Thread Gerald Coley

Nothing closed yet with other distributors. We are having to go through the
approval process to become a supplier. That is holding things up.

Gerald

On Wed, Sep 21, 2016 at 3:46 PM, David Culp  wrote:

> I see that production runs should start hitting distribution soon.  Will
> the board be available anywhere besides RS Components?
>
> --
> 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/b49e841b-46b6-46ff-929b-039ad118b828%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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/CAHK_S%2BdA462aS%2BcAM6ZQs%3DOMJVwyiPFCF10VGkgkm5FzAwqHQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Where to purchase?

2016-09-21 Thread David Culp

I see that production runs should start hitting distribution soon.  Will 
the board be available anywhere besides RS Components? 

-- 
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/b49e841b-46b6-46ff-929b-039ad118b828%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Trying to run the ADC from the PRU

2016-09-21 Thread William Hermans

>
> The only device tree overlay I needed is what I have below; no need to
> load the BB-ADC overlay.
>

Right, technically, you do not need an overlay, and you do not need any
driver modules either. As directly twiddling the ADC module registers, you
essentially are creating your own driver.

Now, with that said, it could be eventually you'll end up using the
overlays, and setting up the ADC in userspace using the iio driver. But
both ways have it's pluses and minuses. I'm sure you can make the
determination for yourself.

On Wed, Sep 21, 2016 at 9:13 AM, Phil  wrote:

> Alright, I finally got this working, thanks to both William and TJF. In
> the end, my problem boils down to coding sloppiness on my part, as well as
> being constantly interrupted with other tasks. After spending a solid block
> of uninterrupted time doing some careful testing, the following code
> snippets are what I found to work. The only device tree overlay I needed is
> what I have below; no need to load the BB-ADC overlay.
>
> *PRU Code*
> //
> // Enable and/or turn on hardware
> // Code in this section must be ordered as listed for proper
> // hardware startup.
>
> // Enable OCP
> lbcor0, PRU_ICSS_CFG_base, PRU_CFG_SYSCFG, 4
> clr r0, 4
> sbcor0, PRU_ICSS_CFG_base, PRU_CFG_SYSCFG, 4
>
> // Enable ADC clock, wait for ADC module to start before proceeding
> mov r0, CM_WKUP_base + CM_WKUP_ADC_TSC_CLKCTRL
> mov r1, 2
> sbbor1, r0, 0, 4
> mov r1, 0   // clear timeout counter
> AdcWait:
> LBBOr0, adc_base, ADC_REVISION, 4   // load ADC REVISION
> QBNEAdcUp, r0, 0// exit if ADC is running
> ADD r1, r1, 1   // increase timeout counter
> QBGEAdcWait, r1.b1, 16  // if no timeout -> wait
> AdcUp:
>
> //
>
> *Device Tree* *Overlay*
> /dts-v1/;
> /plugin/;
>
> /{
> compatible = "ti,beaglebone", "ti,beaglebone-black";
> part-number = "pru_enable";
> version = "00A0";
>
> /* This overlay uses the following resources */
> exclusive-use =
> "pru0",
>
> "P9.29",// GPIO3[15]fet_off
> "P9.30",// GPIO3[16]fet_on
> "P9.31";// GPIO3[14]triac
>
> fragment@0 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> pru_pins: pinmux_pru_pins {
> pinctrl-single,pins = <
> 0x190 0x05  // P9_31 $PINS=100 pr1_pru0_pru_r30_0 mode 5
> output pulldown
> 0x194 0x05  // P9_29 $PINS=101 pr1_pru0_pru_r30_1 mode 5
> output pulldown
> 0x198 0x05  // P9_30 $PINS=102 pr1_pru0_pru_r30_2 mode 5
> output pulldown
> >;
> };
> };
> };
>
> fragment@2 { // Enable the PRUSS
> target = <&pruss>;
> __overlay__ {
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&pru_pins>;
>
> dig_pru_pins {
> pin-names = "FET_OFF","FET_ON","TRIAC" ;
> gpios = <&gpio3 14 0// P9.31
>  &gpio3 15 0// P9.29
>  &gpio3 16 0>;  // P9.30
> };
> };
> };
>
> };
>
> --
> 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/41d50a79-e4b9-4d0c-bd69-16eab8eb2a98%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORpW2ft0QuQL5n1TukmROXJQKABWAH7ieb6-BNxpEivBdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Trying to run the ADC from the PRU

2016-09-21 Thread Phil

Alright, I finally got this working, thanks to both William and TJF. In the 
end, my problem boils down to coding sloppiness on my part, as well as 
being constantly interrupted with other tasks. After spending a solid block 
of uninterrupted time doing some careful testing, the following code 
snippets are what I found to work. The only device tree overlay I needed is 
what I have below; no need to load the BB-ADC overlay.

*PRU Code*
//
// Enable and/or turn on hardware
// Code in this section must be ordered as listed for proper
// hardware startup.

// Enable OCP
lbcor0, PRU_ICSS_CFG_base, PRU_CFG_SYSCFG, 4
clr r0, 4
sbcor0, PRU_ICSS_CFG_base, PRU_CFG_SYSCFG, 4

// Enable ADC clock, wait for ADC module to start before proceeding
mov r0, CM_WKUP_base + CM_WKUP_ADC_TSC_CLKCTRL
mov r1, 2
sbbor1, r0, 0, 4
mov r1, 0   // clear timeout counter
AdcWait:
LBBOr0, adc_base, ADC_REVISION, 4   // load ADC REVISION
QBNEAdcUp, r0, 0// exit if ADC is running
ADD r1, r1, 1   // increase timeout counter
QBGEAdcWait, r1.b1, 16  // if no timeout -> wait
AdcUp:

//

*Device Tree* *Overlay*
/dts-v1/;
/plugin/;

/{
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "pru_enable";
version = "00A0";

/* This overlay uses the following resources */
exclusive-use =
"pru0",

"P9.29",// GPIO3[15]fet_off
"P9.30",// GPIO3[16]fet_on
"P9.31";// GPIO3[14]triac

fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
pru_pins: pinmux_pru_pins {
pinctrl-single,pins = <
0x190 0x05  // P9_31 $PINS=100 pr1_pru0_pru_r30_0 mode 5 
output pulldown
0x194 0x05  // P9_29 $PINS=101 pr1_pru0_pru_r30_1 mode 5 
output pulldown
0x198 0x05  // P9_30 $PINS=102 pr1_pru0_pru_r30_2 mode 5 
output pulldown
>;
};
};
};

fragment@2 { // Enable the PRUSS
target = <&pruss>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&pru_pins>;

dig_pru_pins {
pin-names = "FET_OFF","FET_ON","TRIAC" ;
gpios = <&gpio3 14 0// P9.31
 &gpio3 15 0// P9.29
 &gpio3 16 0>;  // P9.30
};
};
};

};

-- 
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/41d50a79-e4b9-4d0c-bd69-16eab8eb2a98%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long

2016-09-21 Thread Viswadeep Sarangi

Hi William,

I finally got the Board working !!!

Right now, it's booting from the uSD card. The OS in the eMMC is still 
causing problems though, but at least it's working somehow now. 
I downloaded the image 
: 
https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz
 
from https://beagleboard.org/latest-images

You were right about the zImage issue. Makes sense now, now that I 
downloaded the 2016 edition of the image. I realized that I had the 2013 
version of the image earlier. 

Thanks a lot, William for helping me come to this point at least. 

Sincerely,
Viswadeep 

On Tuesday, 20 September 2016 22:38:48 UTC+5:30, William Hermans wrote:
>
> zImage is the old way Robert *used* to build kernels. As in . . .
> http://www.embeddedhobbyist.com/2013/07/beaglebone-black-usb-boot/ Look 
> towards the bottom where I discuss mkimage. But anyway that post I made way 
> back in july 2013, and it's very outdated. It's not how things are done any 
> more.
>
> But quite honestly I really do not understand the kernel images in depth, 
> so perhaps as I'm an applications developer. Not a kernel developer. 
> Granted with a good bit of low level software experience too .  . .
>
> On Tue, Sep 20, 2016 at 6:13 AM, Dennis Lee Bieber  > wrote:
>
>> On Tue, 20 Sep 2016 02:39:50 -0700 (PDT), Viswadeep Sarangi
>> > declaimed the
>> following:
>>
>> >
>> >Right now, I have installed the following image onto my uSD card :
>> >
>> https://debian.beagleboard.org/images/BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz
>> > --- but the BBB doesn't boot from it anymore (even after pressing the S2
>> >button) and still shows the top 2 LEDs lit forever.
>> >
>> Try the version that does not have "flasher" in the name, just to 
>> see
>> if the system can boot from a plain SD card image.
>>
>> When booting a flasher image, the LEDs normally do a 0-3 fill 
>> sequence
>> at the start of flashing, then to some pattern that may vary with the 
>> image
>> before going to a solid all on at the end (Molloy's website says a
>> side-to-side sweep while flashing).
>>
>> You seem to be seeing the first phase of a flasher start.
>>
>> Hmm -- how are you powering the unit? A USB connection may not be
>> providing enough power to sustain eMMC flashing.
>>
>> >
>> >loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
>> >
>> Other than the fact that I don't know where the environment 
>> variables
>> are defined... mmcdev, mmcpart, and fdtfile are not defined in uEnv.txt;
>> the first two define the flash device and partition, and the last 
>> specifies
>> the device tree file.
>>
>> The contents do show that it expects the kernel image to be: 
>> zImage
>> and initrd to be: initrd.img
>> so those match the directory content.
>> --
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/6oc2ubl9o4dl0qm3gpo8kn9jg0lt7l2r50%404ax.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/06fa9b4a-a8ff-4a40-aed7-37c92ab41a0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long

2016-09-21 Thread Viswadeep Sarangi

Hi Dennis,

I finally got the Board working !!!

Right now, it's booting from the uSD card. The OS in the eMMC is still 
causing problems though, but at least it's working somehow now. 
I downloaded the image 
: 
https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz
 
from https://beagleboard.org/latest-images

I am powering the BBB using the USB, but have connected the USB to a cell 
phone charger of 5 V - 2 Amps

I am glad that it's working now, and I can look into the eMMC issue in 
detail at my convenience. I needed this to setup a Python script to run 
periodically every day and I can do that now. 

Thanks a lot, Dennis, but at least guiding me till this point. 

Sincerely,
Viswadeep 

On Tuesday, 20 September 2016 18:44:00 UTC+5:30, Dennis Lee Bieber wrote:
>
> On Tue, 20 Sep 2016 02:39:50 -0700 (PDT), Viswadeep Sarangi 
> > declaimed the 
> following: 
>
> > 
> >Right now, I have installed the following image onto my uSD card : 
> >
> https://debian.beagleboard.org/images/BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz
>  
> > --- but the BBB doesn't boot from it anymore (even after pressing the S2 
> >button) and still shows the top 2 LEDs lit forever. 
> > 
> Try the version that does not have "flasher" in the name, just to 
> see 
> if the system can boot from a plain SD card image. 
>
> When booting a flasher image, the LEDs normally do a 0-3 fill 
> sequence 
> at the start of flashing, then to some pattern that may vary with the 
> image 
> before going to a solid all on at the end (Molloy's website says a 
> side-to-side sweep while flashing). 
>
> You seem to be seeing the first phase of a flasher start. 
>
> Hmm -- how are you powering the unit? A USB connection may not be 
> providing enough power to sustain eMMC flashing. 
>
> > 
> >loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile} 
> > 
> Other than the fact that I don't know where the environment 
> variables 
> are defined... mmcdev, mmcpart, and fdtfile are not defined in uEnv.txt; 
> the first two define the flash device and partition, and the last 
> specifies 
> the device tree file. 
>
> The contents do show that it expects the kernel image to be: 
> zImage 
> and initrd to be: initrd.img 
> so those match the directory content. 
> -- 
> 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/c8541ecd-e984-4f71-ad90-7301d49dcf51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Compilation fails with dtsi file not found.

2016-09-21 Thread cory cauvier

got it working!!! ow man I jumped out of my chair and gave a shout!  thanks 
for the help!

On Sunday, July 26, 2015 at 11:31:34 PM UTC-3, DeKay wrote:
>
> Hi
>
> I am trying to compile the 4.1 kernel as per this eewiki link 
> . I started on a 
> fresh The kernel compiles but the compilation script bombs when it gets to 
> the dtbs stuff because it can't find a file.  Help appreciated.
>
> - 
> make -j2 ARCH=arm LOCALVERSION=-bone14.1 CROSS_COMPILE=ccache 
> /home/dk/Hacking/BBB/bb-kernel/dl/gcc-l
> inaro-4.9-2015.02-3-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- 
> dtbs 
> - 
>  CHK include/config/kernel.release 
>  CHK include/generated/uapi/linux/version.h 
>  CHK include/generated/utsrelease.h 
> make[1]: 'include/generated/mach-types.h' is up to date. 
>  CHK include/generated/bounds.h 
>  CHK include/generated/asm-offsets.h 
>  CALLscripts/checksyscalls.sh 
>  DTC arch/arm/boot/dts/am335x-base0033.dtb 
>  DTC arch/arm/boot/dts/am335x-bone.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-nhdmi-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-hdmi-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-emmc-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-wl1835mod.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-replicape.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-cape-bone-argus.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-can0.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-bbb-exp-r.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-bbb-exp-c.dtb 
>  DTC arch/arm/boot/dts/am335x-bone-cape-bone-argus.dtb 
>  DTC arch/arm/boot/dts/am335x-bone-can0.dtb 
>  DTC arch/arm/boot/dts/am335x-arduino-tre.dtb 
>  DTC arch/arm/boot/dts/am335x-bonegreen.dtb 
> arch/arm/boot/dts/am335x-bonegreen.dts:19:38: fatal error: 
> am335x-boneblack-1ghz.dtsi: No such file o
> r directory 
> #include "am335x-boneblack-1ghz.dtsi" 
>  ^ 
> compilation terminated. 
> scripts/Makefile.lib:293: recipe for target 
> 'arch/arm/boot/dts/am335x-bonegreen.dtb' failed 
> make[1]: *** [arch/arm/boot/dts/am335x-bonegreen.dtb] Error 1 
> make[1]: *** Waiting for unfinished jobs 
> arch/arm/Makefile:319: recipe for target 'dtbs' failed 
> make: *** [dtbs] Error 2
>
>

-- 
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/7cf291ee-6cef-4bec-8679-b4b1d2df1804%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Compilation fails with dtsi file not found.

2016-09-21 Thread cory cauvier

When it says not registered does that mean the program is running but can 
find any onewire devices?

thanks,

Cory

On Sunday, July 26, 2015 at 11:31:34 PM UTC-3, DeKay wrote:
>
> Hi
>
> I am trying to compile the 4.1 kernel as per this eewiki link 
> . I started on a 
> fresh The kernel compiles but the compilation script bombs when it gets to 
> the dtbs stuff because it can't find a file.  Help appreciated.
>
> - 
> make -j2 ARCH=arm LOCALVERSION=-bone14.1 CROSS_COMPILE=ccache 
> /home/dk/Hacking/BBB/bb-kernel/dl/gcc-l
> inaro-4.9-2015.02-3-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- 
> dtbs 
> - 
>  CHK include/config/kernel.release 
>  CHK include/generated/uapi/linux/version.h 
>  CHK include/generated/utsrelease.h 
> make[1]: 'include/generated/mach-types.h' is up to date. 
>  CHK include/generated/bounds.h 
>  CHK include/generated/asm-offsets.h 
>  CALLscripts/checksyscalls.sh 
>  DTC arch/arm/boot/dts/am335x-base0033.dtb 
>  DTC arch/arm/boot/dts/am335x-bone.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-nhdmi-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-hdmi-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-emmc-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-wl1835mod.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-replicape.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-cape-bone-argus.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-can0.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-bbb-exp-r.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-bbb-exp-c.dtb 
>  DTC arch/arm/boot/dts/am335x-bone-cape-bone-argus.dtb 
>  DTC arch/arm/boot/dts/am335x-bone-can0.dtb 
>  DTC arch/arm/boot/dts/am335x-arduino-tre.dtb 
>  DTC arch/arm/boot/dts/am335x-bonegreen.dtb 
> arch/arm/boot/dts/am335x-bonegreen.dts:19:38: fatal error: 
> am335x-boneblack-1ghz.dtsi: No such file o
> r directory 
> #include "am335x-boneblack-1ghz.dtsi" 
>  ^ 
> compilation terminated. 
> scripts/Makefile.lib:293: recipe for target 
> 'arch/arm/boot/dts/am335x-bonegreen.dtb' failed 
> make[1]: *** [arch/arm/boot/dts/am335x-bonegreen.dtb] Error 1 
> make[1]: *** Waiting for unfinished jobs 
> arch/arm/Makefile:319: recipe for target 'dtbs' failed 
> make: *** [dtbs] Error 2
>
>

-- 
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/42d6f155-03e4-4ee4-888d-ad9d153f051f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Compilation fails with dtsi file not found.

2016-09-21 Thread cory cauvier

I couldn't find your example file this morning.  Said it didn't exsist.  I 
was troubleshooting and decided I should start from scratch.  Didn't 
realize it was loading it into the cape overlay each time

On Sunday, July 26, 2015 at 11:31:34 PM UTC-3, DeKay wrote:
>
> Hi
>
> I am trying to compile the 4.1 kernel as per this eewiki link 
> . I started on a 
> fresh The kernel compiles but the compilation script bombs when it gets to 
> the dtbs stuff because it can't find a file.  Help appreciated.
>
> - 
> make -j2 ARCH=arm LOCALVERSION=-bone14.1 CROSS_COMPILE=ccache 
> /home/dk/Hacking/BBB/bb-kernel/dl/gcc-l
> inaro-4.9-2015.02-3-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- 
> dtbs 
> - 
>  CHK include/config/kernel.release 
>  CHK include/generated/uapi/linux/version.h 
>  CHK include/generated/utsrelease.h 
> make[1]: 'include/generated/mach-types.h' is up to date. 
>  CHK include/generated/bounds.h 
>  CHK include/generated/asm-offsets.h 
>  CALLscripts/checksyscalls.sh 
>  DTC arch/arm/boot/dts/am335x-base0033.dtb 
>  DTC arch/arm/boot/dts/am335x-bone.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-nhdmi-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-hdmi-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-emmc-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-wl1835mod.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-replicape.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-cape-bone-argus.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-can0.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-bbb-exp-r.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-bbb-exp-c.dtb 
>  DTC arch/arm/boot/dts/am335x-bone-cape-bone-argus.dtb 
>  DTC arch/arm/boot/dts/am335x-bone-can0.dtb 
>  DTC arch/arm/boot/dts/am335x-arduino-tre.dtb 
>  DTC arch/arm/boot/dts/am335x-bonegreen.dtb 
> arch/arm/boot/dts/am335x-bonegreen.dts:19:38: fatal error: 
> am335x-boneblack-1ghz.dtsi: No such file o
> r directory 
> #include "am335x-boneblack-1ghz.dtsi" 
>  ^ 
> compilation terminated. 
> scripts/Makefile.lib:293: recipe for target 
> 'arch/arm/boot/dts/am335x-bonegreen.dtb' failed 
> make[1]: *** [arch/arm/boot/dts/am335x-bonegreen.dtb] Error 1 
> make[1]: *** Waiting for unfinished jobs 
> arch/arm/Makefile:319: recipe for target 'dtbs' failed 
> make: *** [dtbs] Error 2
>
>

-- 
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/2a24bb3c-332c-41a0-af30-05f3041d0b21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Compilation fails with dtsi file not found.

2016-09-21 Thread Robert Nelson

On Wed, Sep 21, 2016 at 9:21 AM, cory cauvier  wrote:
> Is it loaded three times and only the first one worked?  slot 4

Why did you load it more then once?

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/CAOCHtYiKLZVwOmfe3dPNoyoBh%2B4aKib1EdEvWTuruTfMFCHUSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Compilation fails with dtsi file not found.

2016-09-21 Thread Robert Nelson

On Wed, Sep 21, 2016 at 9:05 AM, cory cauvier  wrote:
> In the picture is the error im getting.  Any advice on what is happening?
>

dmesg | grep bone


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/CAOCHtYjw8HyBOJ3_Rms2NwCBycCNT9ANizSX79VtXpjSpxuUXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Compilation fails with dtsi file not found.

2016-09-21 Thread cory cauvier

In the picture is the error im getting.  Any advice on what is happening?

THanks,

Cory

On Sunday, July 26, 2015 at 11:31:34 PM UTC-3, DeKay wrote:
>
> Hi
>
> I am trying to compile the 4.1 kernel as per this eewiki link 
> . I started on a 
> fresh The kernel compiles but the compilation script bombs when it gets to 
> the dtbs stuff because it can't find a file.  Help appreciated.
>
> - 
> make -j2 ARCH=arm LOCALVERSION=-bone14.1 CROSS_COMPILE=ccache 
> /home/dk/Hacking/BBB/bb-kernel/dl/gcc-l
> inaro-4.9-2015.02-3-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- 
> dtbs 
> - 
>  CHK include/config/kernel.release 
>  CHK include/generated/uapi/linux/version.h 
>  CHK include/generated/utsrelease.h 
> make[1]: 'include/generated/mach-types.h' is up to date. 
>  CHK include/generated/bounds.h 
>  CHK include/generated/asm-offsets.h 
>  CALLscripts/checksyscalls.sh 
>  DTC arch/arm/boot/dts/am335x-base0033.dtb 
>  DTC arch/arm/boot/dts/am335x-bone.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-nhdmi-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-hdmi-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-emmc-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-overlay.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-wl1835mod.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-replicape.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-cape-bone-argus.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-can0.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-bbb-exp-r.dtb 
>  DTC arch/arm/boot/dts/am335x-boneblack-bbb-exp-c.dtb 
>  DTC arch/arm/boot/dts/am335x-bone-cape-bone-argus.dtb 
>  DTC arch/arm/boot/dts/am335x-bone-can0.dtb 
>  DTC arch/arm/boot/dts/am335x-arduino-tre.dtb 
>  DTC arch/arm/boot/dts/am335x-bonegreen.dtb 
> arch/arm/boot/dts/am335x-bonegreen.dts:19:38: fatal error: 
> am335x-boneblack-1ghz.dtsi: No such file o
> r directory 
> #include "am335x-boneblack-1ghz.dtsi" 
>  ^ 
> compilation terminated. 
> scripts/Makefile.lib:293: recipe for target 
> 'arch/arm/boot/dts/am335x-bonegreen.dtb' failed 
> make[1]: *** [arch/arm/boot/dts/am335x-bonegreen.dtb] Error 1 
> make[1]: *** Waiting for unfinished jobs 
> arch/arm/Makefile:319: recipe for target 'dtbs' failed 
> make: *** [dtbs] Error 2
>
>

-- 
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/b9e1a433-0ed0-4904-ade4-26424d2f8c1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] lead finding services

2016-09-21 Thread sunitha seo



*DataAngle Technologies *is an ITES and Project Consulting firm providing 
expertise services in Business Process Outsourcing (BPO), Market Research, B2B 
Lead Generation , 
Recruitment and Digital Marketing. We specialize in providing innovative, 
reliable and cost-effective Business Process Outsourcing (BPO) Services to 
customers across the globe for key business processes for both voice and 
non-voice.

http://www.datangle.net/b2b-lead-generation-services/

-- 
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/a51926ef-a2fd-455d-a4f8-6484925bf9d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BB-BONE-AUDI-02 load without cape

2016-09-21 Thread Pierre Yameogo

Hi,
I want to know if it's possible to load BB-BONE-AUDI-02 via /boot/uEnv.txt 
and watch digital output on oscilloscope without plug in cape.
I try it (also loading am335x-boneblack-audio.dtb of course), all kernel 
messages (dmesg) are ok (except i2c register setup, of course, cape isn't 
plugged), when I play a wave file with aplay, all seems ok but nothing move 
on digital audio pin. I use last debian release : Debian 8.5 2016-05-13 4GB 
SD LXQT
Something strange, removing am335x-boneblack-audio.dtb from uEnv.txt give 
many kernel error message but soundcard is here (aplay -l) and playing a 
wave file give signal on oscilloscope. However only dsp_a or dsp_b digital 
audio format are working and I need I2S, right_J or left_J
Do I need to do a kernel update?
Thanks
Pierre  




-- 
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/52032681-2a87-4aa6-a0b4-27799cfb0852%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] wifi works when BBGW first powered on, but not after a warm reboot

2016-09-21 Thread Stephane Charette

I installed build BBGW-blank-debian-8.6-seeed-iot-armhf-2016-09-18-4gb 
tonight. But I cannot get WIFI to work at all with this build.  I think the 
most recent changes have made things worse.

On both cold and warm boot, the serial console spits out the same message 
every few seconds:

wlcore: ERROR firmware boot failed despite 3 retries

/var/log/syslog has lots of repeating messages, such as:

Sep 18 18:47:24 beaglebone wifidog_server[3940]: [3][Sun Sep 18 18:47:24 
2016][3943](gateway.c:397) Could not create web server: Cannot assign 
requested address
Sep 18 18:47:24 beaglebone systemd[1]: wifidog-gateway.service: Main 
process exited, code=exited, status=1/FAILURE
Sep 18 18:47:24 beaglebone systemd[1]: wifidog-gateway.service: Unit 
entered failed state.
Sep 18 18:47:25 beaglebone systemd[1]: wifidog-gateway.service: Failed with 
result 'exit-code'.
Sep 18 18:47:28 beaglebone systemd[1]: wifidog-pre-startup.service: Service 
hold-off time over, scheduling restart.

This is the latest build freshly installed on the BBGW.  I've not run any 
commands yet except for "cat" and "ifconfig" to see what interfaces are 
available (lo and usb0).

-- 
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/c6e7309c-7dfe-4a9b-af4f-f11af060f231%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Real-time support for Beaglebone using Yocto

[beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long

[beagleboard] bbgw wlan0 users

Re: [beagleboard] Re: How Flashing Now Works with Debian

[beagleboard] Fwd: AIX/Linux Admin (Production Support)

Re: [beagleboard] Where to purchase?

[beagleboard] Where to purchase?

Re: [beagleboard] Re: Trying to run the ADC from the PRU

[beagleboard] Re: Trying to run the ADC from the PRU

Re: [beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long

[beagleboard] Re: BBB doesn't boot after inserting uSD card having linux, even after pressing the S2 button for long

[beagleboard] Re: Compilation fails with dtsi file not found.

[beagleboard] Re: Compilation fails with dtsi file not found.

[beagleboard] Re: Compilation fails with dtsi file not found.

Re: [beagleboard] Re: Compilation fails with dtsi file not found.

Re: [beagleboard] Re: Compilation fails with dtsi file not found.

[beagleboard] Re: Compilation fails with dtsi file not found.

[beagleboard] lead finding services

[beagleboard] BB-BONE-AUDI-02 load without cape

Re: [beagleboard] wifi works when BBGW first powered on, but not after a warm reboot

20 matches

Site Navigation

Mail list logo

Footer information