[beagleboard] Re: Windows adb driver issue

[Vishveshwar]

On Wednesday, January 8, 2014 9:57:40 PM UTC+5:30, Doug Nappier wrote:
>
> I am working with Android Jelly bean and am having some adb issues when it 
> comes to Windows 7. I can not get windows 7 to recognize the device as an 
> Android device and can not find it with adb. When I boot into my linux host 
> machine I can use adb to find the beagleboard.  
>
> I ran lsusb on the device in my linux host and got the following output:
> Bus 001 Device 011: ID 18d1:9018 Google Inc
>
> I read in the TI ADB install 
> guide that 
> you need to add the following lines to you the .inf file:
>
> %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9018
> %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9018&MI_01
>

That guide is quite old and probably not up-to-date.
Have you checked the information the the TI User Guide for the Android 
version you are using? I think the PIDs have changed.

-Vishveshwar

>
> When I go to my device manager, where the device is mistakenly being 
> established as a mass storage device, and attempt to point Windows at this 
> new .inf file it gives me the error "Windows could not find the driver 
> software for your device"
>
> Does anyone have any ideas how to fix this.
>

-- 
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/groups/opt_out.

[beagleboard] Re: Can it run Minecraft (Full PC)?

[Joey Carlini]

Bit of an update, signs point to Yes, it can run if you put a choke on the 
amount of RAM you need. It would involve a direct compile of the LWJGL for the 
bone, and replacing that with the version Minecraft draws from, so it would be, 
to say the least, involved.

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Maximum voltage range -- beaglebone revA5 power supply.

[Loren Amelang]

>
> Trying to understand this...  It seems you are saying the default state of 
> the TPS65215C is to have the AC pin internally connected to the USB pin. 
> But the datasheet says:
> -
> AC input is prioritized over USB input, i.e. if both inputs are valid, 
> current is pulled from the AC input and not USB. If both, AC and USB 
> supplies are available, the power-path switches to USB input if VAC drops 
> below 4.1 V (fixed threshold).
>
> Note that the rise time of VAC and VUSB must be less than 50 ms for the 
> detection circuits to operate properly. If the rise time is longer than 50 
> ms, the IC may fail to power up.
>
> The linear charger periodically applies a 10-mA current source to the BAT 
> pin to check for the presence of a battery. This will cause the BAT 
> terminal to float up to > 3 V which may interfere with AC removal detection 
> and the ability to switch from AC to USB input. For this reason, it is not 
> recommended to use both AC and USB inputs when the battery is absent.
> -
>
> So there is the official word on all the power supply rise-time issues 
> people report! 
>
> -
> AC and USB Input Discharge
> AC and USB inputs have 90-µA internal current sinks which are used to 
> discharge the input pins to avoid false detection of an input source. The 
> AC sink is enabled when USB is a valid supply and VAC is below the 
> detection threshold. Likewise, the USB sink is enabled when AC is a valid 
> supply and VUSB is below the detection limit.
>
> Both current sinks can be forced OFF by setting the [ACSINK, USBSINK] bits 
> to 11b. Both bits are located in register 0x01 (PPATH).
> -
>
> There is an even more important reason for never having AC and USB 
> connected simultaneously. 
>
> Sure sounds to me like the TPS65215C never turns on both FETs at the same 
> time. 
>
>
> But as I asked before, the reality is best known from the RMA stream - do 
> people actually fry their TPS2051 switches? 
>
> Loren
>
>
> On Wednesday, January 8, 2014 5:33:51 AM UTC-8, Gerald wrote:
> The TPS65215C passes what ever voltage is supplied to it out heat pin as 
> long as it is not over 7.2V, which is mote than 5V. So, while the TPS65217C 
> can run at 6V, the TPS2051 cannot,. 
>
> Gerald
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] A6A BBB - eMMC flashing issue?

[fabrguer]

LEDs are flashing! Seems it works.
Thanks! I don't know how I missed that instruction.
:-)

>  

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Boot failure "external abort on non-linefetch" in cpsw_probe with any image after Wi-Fi install

[Loren Amelang]

>
> @Victor:
>
> In your first post, you had exactly my error report. So do I understand 
> correctly you tried the two older images listed below and received the 
> totally different error reports? I've never seen any of those messages, but 
> I've only tried newer images, like 
> Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.09.05.img.xz. 
>
 

>
> [0.651272] omap2_set_init_voltage: unable to get clk dpll1_ck
> [0.657458] omap2_set_init_voltage: unable to set vdd_mpu_iva
> [0.663475] omap2_set_init_voltage: unable to get clk l3_ick
>
> Looks like those are complaining about clocks? Have you seen this:
> http://web.archiveorange.com/archive/v/vEQ2y6LmBVoCWJwTbcnr
>
> about a problem with clocks not being enabled before mdio: probe
>
> "Make the driver control the device clocks. Appearantly, the Davinci
> platform probes this driver with the clock all powered up, but on OMAP,
> this isn't the case."
>
> And Vaibhav's reply:
> As per the commit logs of the mainline kernel a patch adding pm_runtime_* 
> calls in the driver went in around 3.7-rc3.
>
>
> And for the over-current messages, have you seen this:
>
> https://groups.google.com/forum/#!searchin/beagleboard/lorenamelang/beagleboard/eB1ZRsZRtbk/3hKkZaSh0B0J
> -
> And if you go to 6V, it will blow up the power control switch for the USB 
> host, rated at 5.5VDC maximum. 
> Gerald
> -
> Looks like the TPS2051 is one of the few components that isn't protected 
> from overvoltage by the TPS65217C,.  
>

>
> On Friday, January 10, 2014 4:22:06 PM UTC-8, Víctor MV wrote:
>
> More information:
>  Angstrom-Cloud9-IDE-eglibc-ipk-v2012.01-core-beaglebone-2012.01.11.img.gz, 
> booted (still getting PHY 0:00 not found,  PHY 0:01 not found).
> Angstrom-Cloud9-IDE-eglibc-ipk-v2012.01-core-beaglebone-2012.01.27.img.xz 
> booted.
>
>

-- 
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/groups/opt_out.

[beagleboard] Re: can no longer connect via os x

[rattus]

Is it possible that your router reassigned the DHCP address?

If so, you might access the router and see what's assigned, on my Linksys 
router the table is under Status->Local Network->DHCP Clients table; my BBB 
running Debian shows up as 'arm'. I'm assuming you're not running the 
default Angstrom with the hosed dropbear issue as you've been able to ssh 
in the past. DAMHIK ;-)

On Thursday, January 9, 2014 12:24:47 AM UTC-7, Chuck Benson wrote:
>
> Initially I was able to connect via OS X -- could launch the start page 
> from the mounted BBB, able to install drives, able to connect to 
> 192.168.7.2, and also ssh to the BBB. However, on subsequent use, I can no 
> longer connect. The board will mount and I can see the files in the Finder, 
> but the start.htm page won't render & it does not show in the Terminal 
> window (no response to ping or nmap). The board LED's appear to be behaving.
>
> Suggestions?
>
> Thanks
> Chuck
>
>
>

-- 
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/groups/opt_out.

[beagleboard] Userspace RAM access

[rattus]

Hi - I'm looking for a way to address files in RAM only in order to 
minimize eMMC writes; there will be a lot of manipulation of contents that 
I'd like to keep away from nonvolatile storage, and then would like to save 
in full block writes if possible.

Sorry to noob this, but is there a way to ensure RAM access via /dev/xxx?

-- 
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/groups/opt_out.

Re: [beagleboard] LiPo power cape for Beagle Bone.

[Neilh]

I've experimented with powerfilm OEM for a couple of years. They need good 
UV protection when out in the sun, so look at the model to see if it is 
already protected, or you need to supply it with a secondary film.

On Tuesday, January 22, 2013 3:22:51 PM UTC-8, Eric wrote:
>
> pleanty of solar chargers around try these guys:
>
> http://www.powerfilmsolar.com/products/portable-remote
>
> On Tue, Jan 22, 2013 at 3:13 PM, William Pretty Security <
> bill@xplornet.com > wrote:
>
>> Turns out they have  a “solar” version too J
>>
>>  
>>
>> https://www.sparkfun.com/products/11496
>>
>>  
>>
>>  
>>
>> *From:* beagl...@googlegroups.com  [mailto:
>> beagl...@googlegroups.com ] *On Behalf Of *William Pretty 
>> Security
>> *Sent:* Tuesday, January 22, 2013 6:05 PM
>> *To:* beagl...@googlegroups.com 
>> *Subject:* RE: [beagleboard] LiPo power cape for Beagle Bone.
>>
>>  
>>
>> Hi Guys;
>>
>>  
>>
>> I was doing a little research and found this at good old Sparkfun !
>>
>>  
>>
>> https://www.sparkfun.com/products/11359
>>
>>  
>>
>> Seems to me, you mount this on a Beaglebone proto-board, add an on/off 
>> switch and off you go !
>>
>> You can use just about any crappy old wall wort to charge the battery J
>>
>>  
>>
>> Bill
>>
>>  
>>
>>  
>>
>> *From:* beagl...@googlegroups.com  [
>> mailto:be...@googlegroups.com ] *On Behalf Of *Eric Fort
>> *Sent:* Tuesday, January 22, 2013 5:21 PM
>> *To:* beagleboard
>> *Cc:* Andrew Bradford
>> *Subject:* Re: [beagleboard] LiPo power cape for Beagle Bone.
>>
>>  
>>
>> I'm trying to better understand the issue with the creation of a LiPo 
>> cape for the bone.  Here's my thinking:
>>
>> With a nominal cell voltage of 3.7v it would take a 2 cell LiPo pack to 
>> light up the 5v rail no matter what you do.  At this point you have 7.4v.  
>> Use a buck converter and produce 5v from 7.4v (or possibly a 6-13.8v source 
>> making it a rather useful general power supply cape useful for powering the 
>> bone in your car as well) with decent efficiency and feed that into the 5v 
>> line on the expansion connectors the same way that the battery cape does 
>> now.  As for charging the lipo pack I'm not sure I'd really worry about 
>> that much, rather I'd simply supply a connector on the cape for a standard 
>> RC type lipo pack and optionally a decent sized cap for continuity when 
>> changing batteries.  The user could then choose the type and size needed 
>> for the desired runtime.  when it comes to charging, just disconnect the 
>> LiPo pack and plug it into a standard RC charger available from any decent 
>> hobby store where the pack was sourced from.  How does this vary from the 
>> approaches previously looked at for a LiPo cape?  What problems might I 
>> have missed?
>>
>> Eric
>>
>>
>>
>> Eric
>>
>> On Tue, Jan 22, 2013 at 6:33 AM, Andrew Bradford <
>> and...@bradfordembedded.com > wrote:
>>
>> On Mon, 21 Jan 2013 20:53:16 -0800
>> Eric Fort > wrote:
>>
>> > Just a thought A large lithium pack for the bone would rock!
>>
>>
>> Regarding the lithium battery pack idea, it's a good one except for one
>> little issue with the bone where a rework is required in order to power
>> down into TPS65217 OFF or SLEEP modes when a battery is connected due
>> to SYS voltage staying present and the way 3.3V_EXP is generated. So
>> long as you don't want to power off with the battery still connected
>> there's no issue, though.
>>
>> The existing battery cape doesn't have this problem as it's 4 AA cells
>> with a regulator and that feeds into the 5V line on the expansion
>> connectors.
>>
>> -Andrew
>>
>>  
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>>  
>>  
>>
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2013.0.2890 / Virus Database: 2638/6034 - Release Date: 01/15/13
>> Internal Virus Database is out of date.
>> --
>>
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2013.0.2890 / Virus Database: 2638/6034 - Release Date: 01/15/13
>> Internal Virus Database is out of date.
>> --
>>
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2013.0.2890 / Virus Database: 2638/6034 - Release Date: 01/15/13
>> Internal Virus Database is out of date.
>>
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2013.0.2890 / Virus Database: 2638/6034 - Release Date: 01/15/13
>> Internal Virus Database is out of date.
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>>  
>>  
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>>  
>>  
>>
>
>

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

Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Drew Fustini]

fyi - if you are in need of just 1, then you might want to check out
element14's new BBB giveaway:
http://www.element14.com/community/events/3935?ICID=bh-contest-winbbb


On Fri, Jan 10, 2014 at 5:55 PM,  wrote:

> I got one mail order from Micro Center -
> http://www.microcenter.com/product/416355/BeagleBone_Black
>
> Also, was in a Radio Shack the other day and saw a starter kit. At $89 it
> might be worth checking if you are in a pinch.
>
> Tony
>
>
> On Monday, January 6, 2014 8:45:51 PM UTC-5, Paul Wright wrote:
>>
>> I was just curious why none of my usual distributors have any BeagleBone
>> Black boards in stock and most are reporting lead times that are beyond
>> belief.  Has there been some supply chain disturbance I have missed?
>> Shortage of a key component?
>>
>> Just seems strange...
>>
>> I'm evaluating a potential use but if there are going to be supply issues
>> going forward, that is a concern.
>>
>> Does anyone have any information they can offer?
>>
>> Regards,
>>
>> paul
>>
>>
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Boot failure "external abort on non-linefetch" in cpsw_probe with any image after Wi-Fi install

[Víctor MV]

More information:

   -  
   
Angstrom-Cloud9-IDE-eglibc-ipk-v2012.01-core-beaglebone-2012.01.11.img.gz,
 
   booted (still getting *PHY 0:00 not found**,  PHY 0:01 not found*).
   - 
   
   Angstrom-Cloud9-IDE-eglibc-ipk-v2012.01-core-beaglebone-2012.01.27.img.xz 

 booted.
   
   

-- 
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/groups/opt_out.

Re: [beagleboard] debian: test images (2014-01-10)

[David Lambert]

On 01/10/2014 05:52 PM, David Lambert wrote:

On 01/10/2014 05:36 PM, Robert Nelson wrote:


Should i also push out a 8GB image? it's all zero's and it just
compresses very well..

I know but I think most of the time is writing to the SD, so it would 
be nice if there was a good way to resize the root using parted or 
something?

I just used parted - it worked fine:
root@beaglebone:~# df
Filesystem 1K-blocksUsed Available Use% Mounted on
rootfs   7537984 1220976   5930864  18% /
udev   10240   0 10240   0% /dev
tmpfs 101464 548100916   1% /run
/dev/mmcblk0p2   7537984 1220976   5930864  18% /
tmpfs 253652   0253652   0% /dev/shm
tmpfs 253652   0253652   0% /sys/fs/cgroup
tmpfs 102400   0102400   0% /run/user
tmpfs   5120   0  5120   0% /run/lock
/dev/mmcblk0p1 98094   70260 27834  72% /boot/uboot


specifially: 3.8.13-bone35

Any hints yet on how to handle pinmux GPIO etc. now that capemgr is 
not yet

there?

By default it's still 3.8 so that all books/guides/etc written for
Angstrom work..  Down the road it'll be v3.13..
Yes, I know how to do that on 3.8, but I'm lost with 3.13. Looks like 
I will have to roll my own pinmux for now to get the USB improvements ;)

Regards,






--
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/groups/opt_out.
<>

Re: [beagleboard] How to use Beagleboard image-builder?

[Robert Nelson]

On Fri, Jan 10, 2014 at 5:57 PM, David M.  wrote:
>
> On Friday, January 10, 2014 10:36:31 AM UTC-5, RobertCNelson wrote:
>>
>>
>> It's still a little hackish as so far it's really just been written for
>> me..
>>
> That's not a problem.
>
> From what you say, it looks like I can prune the X11 packages.  I'm not sure
> what my final image will be like;  there are a lot of dev packages on my
> custom image since some packages (hi, NTPD!) do not cross-compile.  What I
> do know is that I will not be running X in any sense, so I'll start pruning
> there.  Disk space on either end is not a consideration, but the smaller I
> make it, the easier it is to manage.  I'm using native C so that simplifies
> some things.

btw, i just re-organized the list.. So if you disable xorg... also
disable everything after it..

https://github.com/beagleboard/image-builder/blob/master/beagleboard.org_image.sh#L49

> If I may ask, did you base your build script on an existing project like
> buildroot?  I want to figure out how it works but I think you've done enough
> for the Beagleboard community without my asking for a personal lesson.

It started out life as a maintenance shell 'wrapper' around
'project-rootstock' back in 2009 ish, just so i could easily push out
a new image once a month.. After 'project-rootstock' bit-rotted i
ended up just re-implementing what i actually used from the project..
It's been a franken-script ever since, but it works. ;)

Regards,

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

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

Re: [beagleboard] How to use Beagleboard image-builder?

[David M.]

On Friday, January 10, 2014 10:36:31 AM UTC-5, RobertCNelson wrote:
>
>
> It's still a little hackish as so far it's really just been written for 
> me.. 
>
> That's not a problem.
 
>From what you say, it looks like I can prune the X11 packages.  I'm not 
sure what my final image will be like;  there are a lot of dev packages on 
my custom image since some packages (hi, NTPD!) do not cross-compile.  What 
I *do* know is that I will not be running X in any sense, so I'll start 
pruning there.  Disk space on either end is not a consideration, but the 
smaller I make it, the easier it is to manage.  I'm using native C so that 
simplifies some things.
 
If I may ask, did you base your build script on an existing project like 
buildroot?  I want to figure out how it works but I think you've done 
enough for the Beagleboard community without my asking for a personal 
lesson. 
 
 

-- 
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/groups/opt_out.

[beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?

[tonsofbuys]

I got one mail order from Micro Center 
- http://www.microcenter.com/product/416355/BeagleBone_Black

Also, was in a Radio Shack the other day and saw a starter kit. At $89 it 
might be worth checking if you are in a pinch.

Tony


On Monday, January 6, 2014 8:45:51 PM UTC-5, Paul Wright wrote:
>
> I was just curious why none of my usual distributors have any BeagleBone 
> Black boards in stock and most are reporting lead times that are beyond 
> belief.  Has there been some supply chain disturbance I have missed?  
> Shortage of a key component?
>
> Just seems strange...
>
> I'm evaluating a potential use but if there are going to be supply issues 
> going forward, that is a concern.
>
> Does anyone have any information they can offer?
>
> Regards,
>
> paul
>
>
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] debian: test images (2014-01-10)

[David Lambert]

On 01/10/2014 05:36 PM, Robert Nelson wrote:


Should i also push out a 8GB image? it's all zero's and it just
compresses very well..

I know but I think most of the time is writing to the SD, so it would be 
nice if there was a good way to resize the root using parted or something?

specifially: 3.8.13-bone35


Any hints yet on how to handle pinmux GPIO etc. now that capemgr is not yet
there?

By default it's still 3.8 so that all books/guides/etc written for
Angstrom work..  Down the road it'll be v3.13..
Yes, I know how to do that on 3.8, but I'm lost with 3.13. Looks like I 
will have to roll my own pinmux for now to get the USB improvements ;)

Regards,




--
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/groups/opt_out.
<>

Re: [beagleboard] debian: test images (2014-01-10)

[Robert Nelson]

On Fri, Jan 10, 2014 at 5:25 PM, David Lambert  wrote:
> On 01/10/2014 04:11 PM, Robert Nelson wrote:
>>
>> It's Friday and everyone is probally kicking back and enjoying a cold
>> beverage... Well enough of that crap, time to start actually testing
>> something... ;)
>>
>> First, for tracking please report all bugs to:
>> http://bugs.elinux.org/projects/debian-image-releases
>>
> OK I registered, but awaiting approval. In the meantime, I got the
> following:
>
> Uncompressing Linux... done, booting the kernel.
> [0.369399] omap2_mbox_probe: platform not supported
> [0.526579] tps65217-bl tps65217-bl: no platform data provided
> [0.591595] bone-capemgr bone_capemgr.9: slot #0: No cape found
> [0.628702] bone-capemgr bone_capemgr.9: slot #1: No cape found
> [0.665810] bone-capemgr bone_capemgr.9: slot #2: No cape found
> [0.702918] bone-capemgr bone_capemgr.9: slot #3: No cape found
> [0.718940] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN
> conflict P8.45 (#5:BB-BONELT-HDMI)
> [0.728585] bone-capemgr bone_capemgr.9: slot #6: Failed verification
> [0.735360] bone-capemgr bone_capemgr.9: loader: failed to load slot-6
> BB-BONELT-HDMIN:00A0 (prio 2)
> [0.752808] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset'
> failed
> [0.814570] pinctrl-single 44e10800.pinmux: pin 44e10854 already
> requested by 44e10800.pinmux; cannot claim for gpio-leds.8
> [0.826308] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
> -22
> [0.833623] pinctrl-single 44e10800.pinmux: could not request pin 21 on
> device pinctrl-single
>
> Don't know whether this is a bug or not, but I am also a bit confused as I
> thought the capemgr was not yet in 3.13?

That same error occurs on angstrom's 3.8.. HDMI no audio is trying to
load on top of hdmi with audio...

Regards,

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

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

Re: [beagleboard] debian: test images (2014-01-10)

[Robert Nelson]

On Fri, Jan 10, 2014 at 5:09 PM, David Lambert  wrote:
> On 01/10/2014 04:11 PM, Robert Nelson wrote:
>>
>>
>> 4GB standalone image that can be flashed to any 4GB or greater.
>> [bone-debian-7.3-2014-01-10-4gb.img.xz]
>>
>>
>> http://rcn-ee.net/deb/testing/2014-01-10/bone-debian-7.3-2014-01-10-4gb.img.xz
>> 096915309ec4a8fe41b1e8076a0c436b  bone-debian-7.3-2014-01-10-4gb.img.xz
>>
>> It takes about 20-30 Minutes to dd microSD (4GB)
>>
> OK It only took my system a tad over 8 minutes to a Transcend 8G SD:

Should i also push out a 8GB image? it's all zero's and it just
compresses very well..

> time xzcat /home/dlambert/downloads/bone-debian-7.3-2014-01-10-4gb.img.xz |
> dd bs=10M of=/dev/sdc
> 0+345858 records in
> 0+345858 records out
> 393216 bytes (3.9 GB) copied, 493.82 s, 8.0 MB/s
>
> real8m13.823s
> user0m38.910s
> sys0m6.756s
>
> First impressions great, came right up systemd, avahi, etc. I will keep on
> testing over the weekend.
>
> BTW is the kernel the same as the default in
> git://github.com/RobertCNelson/linux-dev.git?

specifially: 3.8.13-bone35

>
> Any hints yet on how to handle pinmux GPIO etc. now that capemgr is not yet
> there?

By default it's still 3.8 so that all books/guides/etc written for
Angstrom work..  Down the road it'll be v3.13..

Regards,

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

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

Re: [beagleboard] debian: test images (2014-01-10)

[David Lambert]

On 01/10/2014 04:11 PM, Robert Nelson wrote:

It's Friday and everyone is probally kicking back and enjoying a cold
beverage... Well enough of that crap, time to start actually testing
something... ;)

First, for tracking please report all bugs to:
http://bugs.elinux.org/projects/debian-image-releases

OK I registered, but awaiting approval. In the meantime, I got the 
following:


Uncompressing Linux... done, booting the kernel.
[0.369399] omap2_mbox_probe: platform not supported
[0.526579] tps65217-bl tps65217-bl: no platform data provided
[0.591595] bone-capemgr bone_capemgr.9: slot #0: No cape found
[0.628702] bone-capemgr bone_capemgr.9: slot #1: No cape found
[0.665810] bone-capemgr bone_capemgr.9: slot #2: No cape found
[0.702918] bone-capemgr bone_capemgr.9: slot #3: No cape found
[0.718940] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN 
conflict P8.45 (#5:BB-BONELT-HDMI)

[0.728585] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[0.735360] bone-capemgr bone_capemgr.9: loader: failed to load 
slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[0.752808] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
failed
[0.814570] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[0.826308] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) 
status -22
[0.833623] pinctrl-single 44e10800.pinmux: could not request pin 21 
on device pinctrl-single


Don't know whether this is a bug or not, but I am also a bit confused as 
I thought the capemgr was not yet in 3.13?


Dave.

--
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/groups/opt_out.
<>

Re: [beagleboard] Re: Boot failure "external abort on non-linefetch" in cpsw_probe with any image after Wi-Fi install

[Víctor MV]

Some more information, i decided to give it a try with the image 
Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz
 available 
at http://www.angstrom-distribution.org/demo/beaglebone/. 

Surprisingly this is what i'm getting:

-Boot 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03)

I2C:   ready
DRAM:  256 MiB
No daughter card present
NAND:  HW ECC Hamming Code selected
16 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

Net:   cpsw
Hit any key to stop autoboot:  0 
SD/MMC found on device 0
reading uEnv.txt

33 bytes read
Loaded environment from uEnv.txt
Importing environment from mmc ...
reading uImage

3137440 bytes read
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Angstrom/3.2/beaglebone
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:3137376 Bytes = 3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[0.068294] _omap_mux_get_by_name: Could not find signal 
uart1_cts.uart1_cts
[0.068315] omap_hwmod_mux_init: Could not allocate device mux entry
[0.068465] _omap_mux_get_by_name: Could not find signal 
uart2_cts.uart2_cts
[0.068483] omap_hwmod_mux_init: Could not allocate device mux entry
[0.068644] _omap_mux_get_by_name: Could not find signal 
uart3_cts_rctx.uart3_cts_rctx
[0.068728] omap_hwmod_mux_init: Could not allocate device mux entry
[0.106314] cpuidle-am33xx cpuidle-am33xx.0: failed to register driver
[0.261139] _omap_mux_get_by_name: Could not find signal leds-gpio
[0.651272] omap2_set_init_voltage: unable to get clk dpll1_ck
[0.657458] omap2_set_init_voltage: unable to set vdd_mpu_iva
[0.663475] omap2_set_init_voltage: unable to get clk l3_ick
[0.669409] omap2_set_init_voltage: unable to set vdd_core
[0.927024] hub 1-0:1.0: over-current condition on port 1
[1.186994] hub 1-0:1.0: over-current condition on port 1
[1.447002] hub 1-0:1.0: over-current condition on port 1
[1.706975] hub 1-0:1.0: over-current condition on port 1
[1.966988] hub 1-0:1.0: over-current condition on port 1
[2.226976] hub 1-0:1.0: over-current condition on port 1
[2.486983] hub 1-0:1.0: over-current condition on port 1
[2.746982] hub 1-0:1.0: over-current condition on port 1
[3.006980] hub 1-0:1.0: over-current condition on port 1
[3.266980] hub 1-0:1.0: over-current condition on port 1
[3.526979] hub 1-0:1.0: over-current condition on port 1
[3.786975] hub 1-0:1.0: over-current condition on port 1
[4.046994] hub 1-0:1.0: over-current condition on port 1
[4.306975] hub 1-0:1.0: over-current condition on port 1
[4.566981] hub 1-0:1.0: over-current condition on port 1
[4.827045] hub 1-0:1.0: over-current condition on port 1
[5.086988] hub 1-0:1.0: over-current condition on port 1
[5.346982] hub 1-0:1.0: over-current condition on port 1
[5.606985] hub 1-0:1.0: over-current condition on port 1
[5.866990] hub 1-0:1.0: over-current condition on port 1
[6.126976] hub 1-0:1.0: over-current condition on port 1
[6.386980] hub 1-0:1.0: over-current condition on port 1
[6.646976] hub 1-0:1.0: over-current condition on port 1
[6.906974] hub 1-0:1.0: over-current condition on port 1
[7.166987] hub 1-0:1.0: over-current condition on port 1
[7.427043] hub 1-0:1.0: over-current condition on port 1
[7.687078] hub 1-0:1.0: over-current condition on port 1
[7.947139] hub 1-0:1.0: over-current condition on port 1
[8.207116] hub 1-0:1.0: over-current condition on port 1
[8.467097] hub 1-0:1.0: over-current condition on port 1
[8.727113] hub 1-0:1.0: over-current condition on port 1
[8.987448] hub 1-0:1.0: over-current condition on port 1
systemd-fsck[56]: Angstrom-Cloud9-: clean, 28959/874496 files, 
748256/3494137 blocks
[9.247089] hub 1-0:1.0: over-current condition on port 1
[9.507206] hub 1-0:1.0: over-current condition on port 1

For what i've read online about this:

   1. too much current is being consumed by whatever is plugged into that 
   port or 
   2. the power FET (U13?) for the USB port has been damaged causing it to 
   indicate an over current condition
   
On my design (BB-based), P1 (i'm assuming it's referring to P10 Ethernet 
connector) is not soldered. And i doubt it's due to the power FET.

Maybe if i compile the kernel without davinci_mdio?

-- 
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/groups

Re: [beagleboard] debian: test images (2014-01-10)

[David Lambert]

On 01/10/2014 04:11 PM, Robert Nelson wrote:


4GB standalone image that can be flashed to any 4GB or greater.
[bone-debian-7.3-2014-01-10-4gb.img.xz]

http://rcn-ee.net/deb/testing/2014-01-10/bone-debian-7.3-2014-01-10-4gb.img.xz
096915309ec4a8fe41b1e8076a0c436b  bone-debian-7.3-2014-01-10-4gb.img.xz

It takes about 20-30 Minutes to dd microSD (4GB)


OK It only took my system a tad over 8 minutes to a Transcend 8G SD:
time xzcat 
/home/dlambert/downloads/bone-debian-7.3-2014-01-10-4gb.img.xz | dd 
bs=10M of=/dev/sdc

0+345858 records in
0+345858 records out
393216 bytes (3.9 GB) copied, 493.82 s, 8.0 MB/s

real8m13.823s
user0m38.910s
sys0m6.756s

First impressions great, came right up systemd, avahi, etc. I will keep 
on testing over the weekend.


BTW is the kernel the same as the default in 
git://github.com/RobertCNelson/linux-dev.git?


Any hints yet on how to handle pinmux GPIO etc. now that capemgr is not 
yet there?


Regards,

Dave.


--
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/groups/opt_out.
<>

Re: [beagleboard] Re: FreeBSD on BeagleBoard-xm

[Robert Nelson]

On Fri, Jan 10, 2014 at 4:55 PM, Embedded Zhang  wrote:
> Uhmmm. either the bbxm website or you made a mistake:
>
> quote from http://beagleboard.org/Products/BeagleBoard-xM:
>
> What is BeagleBoard-xM?
>
> The $149 MSRP BeagleBoard-xM delivers with the help of its AM37x 1GHz ARM
> processor,
>
>
> I believe that the bbxm website made a mistake, since from the manual:
>
> http://beagleboard.org/static/BBxMSRM_latest.pdf
>
> The BeagleBoard-xM processor is the DM3730CBP 1GHz version and comes in a
> .4mm
>
> pitch POP package.
>
>
> ==
>
> Then my question again is that, is the freeBSD port for bbxm support the
> current version of bbxm (rev c)?

Have you asked the freeBSD guys?  I'd really hope that if they wrote
support for the "bbxm" they support the rev c as that revision has
been out for a few years... At this point it would be pretty stupid of
them not too..

Regards,

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

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

Re: [beagleboard] Re: FreeBSD on BeagleBoard-xm

[Embedded Zhang]

Uhmmm. either the bbxm website or you made a mistake:

quote from http://beagleboard.org/Products/BeagleBoard-xM:

What is BeagleBoard-xM?

The $149 MSRP BeagleBoard-xM delivers with the help of its AM37x 1GHz ARM 
processor, 


I believe that the bbxm website made a mistake, since from the manual:

http://beagleboard.org/static/BBxMSRM_latest.pdf

The BeagleBoard-xM processor is the DM3730CBP 1GHz version and comes in a 
.4mm 

pitch POP package. 


==

Then my question again is that, is the freeBSD port for bbxm support the 
current version of bbxm (rev c)?

==




On Friday, January 10, 2014 4:11:11 PM UTC-5, Gerald wrote:
>
> The BBXM has never been built with the AM37xx. It has always been the 
> DM37xx.
>
> Gerald
>
>
>
> On Fri, Jan 10, 2014 at 2:47 PM, Embedded Zhang 
> 
> > wrote:
>
>> Does this support   AM37x 1GHz ARM Cortex-A8 
>> 
>> ?
>> the previous bbxm is with omap, and the current is with am37x.
>>
>>
>> On Monday, January 21, 2013 6:17:56 PM UTC-5, Flavio Alves wrote:
>>
>>> Hello all, 
>>>
>>> Does anybody could advice me how to prepare an FreeBSD image from 
>>> sources for a Beagle-xM? 
>>>
>>> I could not find any tutorial or guide to do that. 
>>>
>>> Best regards, 
>>>
>>> Flavio 
>>>
>>> -- 
>>> Flavio de Castro Alves Filho 
>>>
>>> flavio...@gmail.com 
>>> www.linuxembarcado.com 
>>> Twitter: http://twitter.com/#!/fraviofii 
>>> LinkedIn profile: www.linkedin.com/in/flaviocastroalves 
>>>
>>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

[beagleboard] Re: debian: test images (2014-01-10)

[Robert Nelson]

Laughs, gmail broke every link..

http://rcn-ee.net/deb/testing/2014-01-10/BBB-eMMC-flasher-debian-7.3-2014-01-10-2gb.img.xz

http://rcn-ee.net/deb/testing/2014-01-10/bone-debian-7.3-2014-01-10-4gb.img.xz

http://rcn-ee.net/deb/testing/2014-01-10/debian-7.3-console-armhf-2014-01-10.tar.xz

Regards,

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

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

[beagleboard] debian: test images (2014-01-10)

[Robert Nelson]

It's Friday and everyone is probally kicking back and enjoying a cold
beverage... Well enough of that crap, time to start actually testing
something... ;)

First, for tracking please report all bugs to:
http://bugs.elinux.org/projects/debian-image-releases

So go forward and test the first "beta" release. There are 3 files on
the web server, depending on what you want to do. Using the same
standard procedure found here:
http://elinux.org/Beagleboard:Updating_The_Software

http://rcn-ee.net/deb/testing/2014-01-10/

An eMMC "flasher" which can be installed to any 2GB or greater microSD
card. [BBB-eMMC-flasher-debian-7.3-2014-01-10-2gb.img.xz]

http://rcn-ee.net/deb/testing/2014-01-10/BBB-eMMC-flasher-debian-7.3-2014-01-10-2gb.img.xz
5cb3f88ae14cbcb94604786484f96309
BBB-eMMC-flasher-debian-7.3-2014-01-10-2gb.img.xz

It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash
eMMC (look for full 4 LED's)

4GB standalone image that can be flashed to any 4GB or greater.
[bone-debian-7.3-2014-01-10-4gb.img.xz]

http://rcn-ee.net/deb/testing/2014-01-10/bone-debian-7.3-2014-01-10-4gb.img.xz
096915309ec4a8fe41b1e8076a0c436b  bone-debian-7.3-2014-01-10-4gb.img.xz

It takes about 20-30 Minutes to dd microSD (4GB)

Finally one of my classic "setup_sdcard.sh".
[debian-7.3-console-armhf-2014-01-10.tar.xz]

http://rcn-ee.net/deb/testing/2014-01-10/debian-7.3-console-armhf-2014-01-10.tar.xz
526adb40799a8e060df020ed1cd47c12  debian-7.3-console-armhf-2014-01-10.tar.xz

Note for users who use my classic "setup_sdcard.sh" script, here is
the magic options to get the beaglebone project files + systemd.

sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone
--beagleboard.org-production --enable-systemd

To "rebuild"
git clone git://github.com/beagleboard/image-builder.git
cd image-builder
git checkout bb.org-v2014.01.10 -b tmp
./beagleboard.org_image.sh

Thoughts/rants/list/etc?

Go Test!

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

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

[beagleboard] Re: Build a QT/11 application for beagleboard black by cross compiling from ubuntu

[gdj]

I used the instructions and got a working BBB with a CAP LCD7. However I 
needed to cut the eMMC lines to the LCD CAP (BeagleToys one), it is a A3 
Ref but still did not work, but the site say is 100% BBB compatible.. ha ha 
. The only thing that does not work is the mouse when used with the LCD 
CAP, but that is not a problem to me as I used the touch screen. I made a 
document up with the instructions as I had to change some things to get the 
GUI , GDD and LCD cap working.

I also think QT creator has a bug , one has to delete the xx.user file and 
then setup the kit, else you cannot change the kit, it still uses the 
original kit. So just be sure to select the correct kit when started after 
the .user file was was deleted.

It works great !!


 Building and setting up QT environment for BeagleBone 

There are too few information available on how to easily setup QT 
environment for building Beaglebone applications (command line or GUI). In 
this tutorial we will compile QT and setup the environment from scratch.
1. My environment 
   
   - 
   
   Host: Ubuntu 13.10 64bit (VB) 
   - 
   
   Target: BeagleBone Black running Angstrom 
   - 
   
   QT: 4.8.5 
   
2. Setup Angstrom cross-compile toolchain for Linux 

Download :

   - 
   
   
   
angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2
 for 
   64bit host or 
   - 
   
   
   
angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2
 for 
   x86 (or download more recent version at 
   
   http://www.angstrom-distribution.org/toolchains/). 
   - 
   
   https://googledrive.com/host/0B3Z340LOBulvMG5NRmNlZEppSEE
   
 Run

$> tar -C / -xjf 
angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2
3. Download and un-tar QT 

> wget 
http://download.qt-project.org/official_releases/qt/4.8/4.8.5/qt-everywhere-opensource-src-4.8.5.tar.gz
 
> tar -xzf qt-everywhere-opensource-src-4.8.5.tar.gz
 
> mv qt-everywhere-opensource-src-4.8.5 qt-4.8.5-beagle
 

  4. Create qmake.conf 

> cd qt-4.8.5-beagle
 
> mkdir ./mkspecs/qws/linux-am335x-g++ 
 
> cp ./mkspecs/qws/linux-arm-g++/qplatformdefs.h 
./mkspecs/qws/linux-am335x-g++ 
 
> touch ./mkspecs/qws/linux-am335x-g++/qmake.conf
 

 Add the following to qmake.conf with your favorite editor:

#
 
# qmake configuration for building with arm-linux-g++
 
#
 
include(../../common/linux.conf)
 
include(../../common/gcc-base-unix.conf)
 
include(../../common/g++-unix.conf) 
 
include(../../common/qws.conf)
 
 
 
# modifications to g++.conf
 
#Toolchain
 
 
 
#Compiler Flags to take advantage of the ARM architecture
 
QMAKE_CFLAGS_RELEASE =   -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon 
-mfloat-abi=softfp
 
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon 
-mfloat-abi=softfp
 
 
 
QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
 
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
 
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
 
QMAKE_LINK_SHLIB = 
/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
 
 
 
# modifications to linux.conf
 
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
 
QMAKE_OBJCOPY = 
/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
 
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip
 
 
 
load(qt_config)
  5. Configure QT embedded 

./configure -v -opensource -confirm-license -prefix /opt/qt -embedded arm 
-platform qws/linux-x86-g++ -xplatform qws/linux-am335x-g++ -depths 
16,24,32 -no-mmx -no-3dnow -no-sse -no-sse2 -no-glib -no-cups -no-largefile 
-no-accessibility -no-openssl -no-gtkstyle -qt-mouse-pc -qt-mouse-linuxtp 
-qt-mouse-linuxinput -plugin-mouse-linuxtp -plugin-mouse-pc -fast 
-little-endian -host-big-endian -no-pch -no-sql-ibase -no-sql-mysql 
-no-sql-odbc -no-sql-psql -no-sql-sqlite -no-sql-sqlite2 -no-webkit 
-no-qt3support -nomake examples -nomake demos -nomake docs -nomake 
translations -qt-mouse-tslib
 6. Build and install 

> make -j 4
 
> sudo make install
 7. Install Qt SDK (lib) we built previously on your board 

Make sure you beaglebone is connected to your host (assume ip =192.168.7.2 
USB)

   - 
   
   ssh to your beaglebone (ssh root@192.168.7.2) 
   

   - 
   
   Create dir structure from your prefix:
   
   > root@beaglebone:/# mkdir /opt
   
 
   > root@beaglebone:/# mkdir /opt/qt
   
   > opkg install tslib-calibrate
   
   > ts-all
   
   > ts-calibrate (calibrate all points)
   
   > update-rc.d -f gdm remove
   
   > systemctl disable gdm.service
   
   > reboot
   
 
   - 
   
   Copy lib from your host to beagle (after reboot):
   
   > scp -r /opt/qt/lib root@192.168.7.2:"/opt/qt"
   -

Re: [beagleboard] BBB always destoy my eMMC image if I plug in a ethernet cable.

[Gerald Coley]

If the SD card has the flashing image on it it will flash the board. That
is why the instructions say to remove the SD card before power cycling the
board..

Gerald


On Fri, Jan 10, 2014 at 2:52 PM,  wrote:

> I found that the BBB just sometimes just not boot, then I would re-flash
> the system run again. I then found that if the ethernet is connected and I
> boot from SD card the internal flashing algo start. One can check it with
> 'ps ax', the whole sequence of events can be seen .. first a dd with
> dev/nul, then the creation of the flash etc, this is WITHOUT the boot
> button connected.  It does however also works as advertised , with no
> ethernet connected, then one has to keep the boot button in, with power on
> to get in the flashing eMMC mode.
>
> I personally think this is not suppose to be so, it should ONLY flash the
> eMMC if the BOOT is pressed during power up..
>
> This render a non boot BBB is you switch the power off  within one hour,
> as the eMMC is then not fully programmed, and one cannot see the leds is
> now toggling the flashing sequence, as it always toggle, the only way I
> could detect it was to look at the processes, and see the dd etc
>
> I am using the BBB supplied angstrom, with the latest image before the
> angstrom site went down for 'THREE WEEKS' 
>
> Kind Regards
> Gerrie
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] BBB always destoy my eMMC image if I plug in a ethernet cable.

[gdj]

I found that the BBB just sometimes just not boot, then I would re-flash 
the system run again. I then found that if the ethernet is connected and I 
boot from SD card the internal flashing algo start. One can check it with 
'ps ax', the whole sequence of events can be seen .. first a dd with 
dev/nul, then the creation of the flash etc, this is WITHOUT the boot 
button connected.  It does however also works as advertised , with no 
ethernet connected, then one has to keep the boot button in, with power on 
to get in the flashing eMMC mode.

I personally think this is not suppose to be so, it should ONLY flash the 
eMMC if the BOOT is pressed during power up..

This render a non boot BBB is you switch the power off  within one hour, as 
the eMMC is then not fully programmed, and one cannot see the leds is now 
toggling the flashing sequence, as it always toggle, the only way I could 
detect it was to look at the processes, and see the dd etc

I am using the BBB supplied angstrom, with the latest image before the 
angstrom site went down for 'THREE WEEKS' 

Kind Regards
Gerrie

-- 
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/groups/opt_out.

Re: [beagleboard] Re: FreeBSD on BeagleBoard-xm

[Gerald Coley]

The BBXM has never been built with the AM37xx. It has always been the
DM37xx.

Gerald



On Fri, Jan 10, 2014 at 2:47 PM, Embedded Zhang wrote:

> Does this support  AM37x 1GHz ARM Cortex-A8
> 
> ?
> the previous bbxm is with omap, and the current is with am37x.
>
>
> On Monday, January 21, 2013 6:17:56 PM UTC-5, Flavio Alves wrote:
>
>> Hello all,
>>
>> Does anybody could advice me how to prepare an FreeBSD image from
>> sources for a Beagle-xM?
>>
>> I could not find any tutorial or guide to do that.
>>
>> Best regards,
>>
>> Flavio
>>
>> --
>> Flavio de Castro Alves Filho
>>
>> flavio...@gmail.com
>> www.linuxembarcado.com
>> Twitter: http://twitter.com/#!/fraviofii
>> LinkedIn profile: www.linkedin.com/in/flaviocastroalves
>>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] Re: FreeBSD on BeagleBoard-xm

[Embedded Zhang]

Does this support  AM37x 1GHz ARM Cortex-A8 

?
the previous bbxm is with omap, and the current is with am37x.


On Monday, January 21, 2013 6:17:56 PM UTC-5, Flavio Alves wrote:
>
> Hello all, 
>
> Does anybody could advice me how to prepare an FreeBSD image from 
> sources for a Beagle-xM? 
>
> I could not find any tutorial or guide to do that. 
>
> Best regards, 
>
> Flavio 
>
> -- 
> Flavio de Castro Alves Filho 
>
> flavio...@gmail.com  
> www.linuxembarcado.com 
> Twitter: http://twitter.com/#!/fraviofii 
> LinkedIn profile: www.linkedin.com/in/flaviocastroalves 
>

-- 
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/groups/opt_out.

[beagleboard] BeagleBone Black Audio Cape Buffer Overruns

[Jack Mitchell]

I'm currently struggling with the BeagleBone Audio cape on a BeagleBone 
black. I keep getting ALSA buffer xruns when capturing audio. Has anyone 
successfully done any recording using the audio cape and if so how did 
they do it?


I am currently running 3.13-rc7 mainline and I was experiencing the same 
behaviour on 3.8. Recording to a uSD card is worst, then eMMC and I have 
even seen buffer overruns when recording directly to tmpfs once or 
twice. I am worried that it may be a problem with the audio driver, or 
something is blocking interrupts for too long and the interrupt to empty 
the ALSA buffer is being missed.


Does anyone have any input?

Cheers,

--
  Jack Mitchell (j...@embed.me.uk)
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
--

--
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/groups/opt_out.

Re: [beagleboard] Re: How to Wake BeagleBone Black Screen from Remote SSH

[Mickae1]

A better answer is here :

http://superuser.com/questions/152347/change-linux-console-screen-blanking-behavior

And my favorite cmd is this one => setterm -blank [0-60]

Micka,

Le vendredi 28 juin 2013 14:43:33 UTC+2, mcbe...@gmail.com a écrit :
>
> Thanks all for your suggestions... Just tried the echo suggestion above 
> and it did indeed work.  So I guess if I need to keep my video playing on 
> screen I can just have a script execute that line on a timer.  Not the 
> prettiest solution, but it works!
>
> The only other thing I've actually had luck with to get the gnome desktop 
> to come back up is to actually kill it (killall gnome-session) which 
> literally ends and restarts gnome, resulting in the monitor coming back to 
> life.
>
> Cheers
>
> On Thursday, June 27, 2013 4:29:10 PM UTC-4, Charles Steinkuehler wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE- 
>> Hash: SHA1 
>>
>> On 6/27/2013 10:04 AM, Andrew Henderson wrote: 
>> > On Wednesday, June 26, 2013 1:16:49 PM UTC-4, MB wrote: 
>> > 
>> >> Any ideas? 
>> > 
>> > I have had no luck in getting the HDMI to wake back up after it 
>> > shuts off. But, if you want to disable the DPMS functionality that 
>> > shuts it off in the first place, add "consoleblank=0" to your 
>> > kernel command line arguments in the uEnv.txt. 
>>
>> To wake up the HDMI display remotely: 
>>
>>   echo 0 > /sys/class/graphics/fb0/blank 
>>
>> Interestingly, my display goes into blanking *INSTANTLY* after boot if 
>> I do not have a keyboard plugged in.  Unblanking the display via the 
>> above echo brings the display to life.  Setting the consoleblank=0 on 
>> the kernel command line only affects text consoles, not the GUI. 
>>
>> If you use the native BeagleBone gui to disable the power management 
>> turning off the monitor, the display will come up regardless of 
>> whether or not you have a KB/Mouse connected.  There's probably a 
>> gnome config file somewhere that you could edit to disable blanking 
>> via the command line, but I don't know the guts of gnome well enough 
>> to know what it would be. 
>>
>> - -- 
>> Charles Steinkuehler 
>> cha...@steinkuehler.net 
>> -BEGIN PGP SIGNATURE- 
>> Version: GnuPG v1.4.11 (MingW32) 
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ 
>>
>> iEYEARECAAYFAlHMoJYACgkQLywbqEHdNFyekgCg5nsav/3Kdk9O744I4DRgppuO 
>> fTEAn11CMdzY4BFzzpOw6RHEh9FXbtIF 
>> =4rYx 
>> -END PGP SIGNATURE- 
>>
>

-- 
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/groups/opt_out.

Re: [beagleboard] Availability - how come nobody has any BeagleBone Black to sell?

[mark . s . schaefer]

Good call!  I went online to check the stock in my nearest store and it 
says they have five as well. It's an hour drive, but probably worth it.  I 
just need one for my "project" :)

On Friday, January 10, 2014 8:48:23 AM UTC-7, ky...@cranehome.info wrote:
>
> I checked the MicroCenter retail store in my area and they had 5 in stock. 
>   Certainly not enough for a project but enough for the "I need on to play 
> with right now" issues. 
>
>

-- 
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/groups/opt_out.

[beagleboard] angstrom

[Jyotirmaya Joon]

i am using angstrom for bb-xm. but whem i do opkg update it says 404 error 
. page not found. because of this i can not install tools

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Windows 7 doesn't mount BBB as usb drive after update

[Richard Pesce]

Hi Emory,
That person's board wouldn't boot.

Good looking out though!  I appreciate it!
On Jan 10, 2014 7:12 AM, "Emory Creel"  wrote:

> there is a similar issue with an individual on whose board the initial
> files that appeared on the
> usb mount were erased
>
> https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/1qr04iE0EYc
> the recommended solution was flashing, which started the issue for this
> group, but its
> the same specific result, so I thought it might be possible the two issues
> are somehow related. just sayin'.
>
> On Wednesday, January 8, 2014 1:23:27 PM UTC-5, JBodine wrote:
>>
>> Same problem here.   It worked on Windows 7 initially but no longer.
>>
>> On Thursday, June 20, 2013 9:31:44 PM UTC-7, Richard Pesce wrote:
>>>
>>> Hello all!
>>>
>>> I recently received my Beaglebone Black.  I followed the getting started
>>> guide HERE , installed the
>>> drivers.  Afterwards I was able to connect to http://192.168.7.2 and
>>> use cloud9 etc.
>>>
>>> I got to the "Update board with latest software" portion and downloaded
>>> BBB-eMMC-flasher-2013.06.06.img.xz
>>>  and
>>> flashed the eMMC successfully.  I removed the power, ejected the uSD and
>>> then connected to the computer via USB and the BBB wouldn't mount as a USB
>>> drive.  Fearing the update failed, I tried again with the same image.  That
>>> failed... so I tried 
>>> BBB-eMMC-flasher-2013.06.20.img.xz
>>>  from 
>>> HERE and
>>> flashed again... still no USB drive.  I then tried
>>> BBB-eMMC-flasher-2013.06.17.img.xz
>>>  from HERE ...
>>> still no USB drive.  In a last ditch effort I tried (Current Production
>>> Image) 
>>> BBB-eMMC-flasher-2013.05.20.img.xz
>>>  from 
>>> HERE...
>>> still no USB drive.
>>>
>>>
>>> LINUX:
>>> It is important to note that I could SSH into all of these installs (not
>>> at http://192.168.7.2 though), and verified that everything worked
>>>  I can see /dev/mmcblk0p1 is mounted at /media/BEAGLEBONE (with my most
>>> current flash) and all the files are present.
>>>
>>> WINDOWS:
>>> I searched in device manager and could not see the BBB at all or any
>>> unknown or not working hardware.  And in computer management/Disk
>>> management there isn't anything present.
>>>
>>> I have attempted other computers (WIN7) and multiple USB ports  same
>>> issue,
>>>
>>>
>>> Anyone have any suggestions?  I'm sure I am missing something obvious.
>>>
>>>
>>> Thank you in advance!
>>>
>>>
>>>
>>>  --
> 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/Fz64scAbfwo/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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] ssh, telnet not responding after a few days of working.

[Mike Bremford]

> Would plugging and unplugging the usb cause problems?

On kernel 3.8.13, yes it would. Turn it off and on, does it come back up?
If so, try upgrading to kernel 3.13 - should fix your USB issues.

-- 
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/groups/opt_out.

Re: [beagleboard] A6A BBB - eMMC flashing issue?

[Fabrizio]

Hi Robert,


That makes sense... ;-)

For some reason I did not remember that and I haven't looked at that guide 
since (in all other places nobody talk about that so i forgot)




I will try when I go back home and update the forum. Should work now. Many 
thanks!!










​




On Fri, Jan 10, 2014 at 7:24 AM, Robert Nelson 
mailto:robertcnel...@gmail.com";>> wrote:
On Fri, Jan 10, 2014 at 9:20 AM, fabrguer  wrote:

> Hi Robert,

>

> oh, I did not know that the images are not proved to work if installed with

> a Mac.

> The first time I tried to install another distro on the BBB (it was Ubuntu)

> I followed Adafruit instructions which are for a Mac and are basically the

> same.

> See the link:

> http://learn.adafruit.com/beaglebone-black-installing-operating-systems/mac-os-x

>

> Anyway I wrote:

> sudo dd if=./BBB..img of=/dev/disk1s1

^^


s1, isn't that "partition 1"...???


They show:


sudo diskutil unmount /dev/disk4s1

then:

sudo dd bs=1m if=~/Downloads/BBB-eMMC-flasher-2013.05.08.img of=/dev/rdisk4


with: /dev/disk4s1" changed to "/dev/rdisk4"


So you'd use.. of=/dev/rdisk1  right???


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 a topic in the Google 
Groups "BeagleBoard" group.

To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/beagleboard/8-dMbYbkYOM/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/groups/opt_out.

-- 
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/groups/opt_out.

Re: [beagleboard] Availability - how come nobody has any BeagleBone Black to sell?

[kyle]

I checked the MicroCenter retail store in my area and they had 5 in stock. 
  Certainly not enough for a project but enough for the "I need on to play 
with right now" issues. 

On Wednesday, January 8, 2014 10:40:48 PM UTC-6, mark.s@gmail.com wrote:
>
> It says MCM Electronics, and MCM is out of stock, so I'm not sure I want 
> to go through the hassle of ordering just to find out they backordered it.
>

-- 
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/groups/opt_out.

Re: [beagleboard] How to use Beagleboard image-builder?

[Robert Nelson]

On Fri, Jan 10, 2014 at 9:16 AM, David M.  wrote:
> I'm running a Beaglebone White with the latest Angstrom (and 3.8.13 kernel)
> and I want to move to the beta Debian distro that Jason talked about.
>
> I have cloned the Git repo at https://github.com/beagleboard/image-builder
> on the Linux Mint virtual machine I use for ARM development, and I've run
> the script ./beagleboard.org_image.sh in the directory I use for
> development, just as I did for Angstrom.  It "worked" and pulled down lots
> of files, as I expected.
> Where do I go from here?  What are my build options?  I want to customize
> the build to a minimal system without X, just as I did for Angstrom.

It's still a little hackish as so far it's really just been written for me..

"base packages"
https://github.com/beagleboard/image-builder/blob/master/var/pkg_list.sh
AKA: everything needed for network access/debuging for a console
system..  They are split into discrete groups, just disable what you
don't need..

"chroot packages"
https://github.com/beagleboard/image-builder/blob/master/beagleboard.org_image.sh#L192
Without these the "chroot" will fail and you'll never get a final image...

"firmware packages"
https://github.com/beagleboard/image-builder/blob/master/beagleboard.org_image.sh#L276
not everyone needs them..

You can disable them globally via:
https://github.com/beagleboard/image-builder/blob/master/beagleboard.org_image.sh#L326

"bb.org/x11/lxde packages"
https://github.com/beagleboard/image-builder/blob/master/beagleboard.org_image.sh#L39
I'm still fine tunning these for the "final" image..

Finally the "bb.org" script
https://github.com/beagleboard/image-builder/blob/master/beagleboard.org_image.sh#L328

which runs, this sets up everything "custom" for the bb.org image..
(non generic stuff.)
https://github.com/beagleboard/image-builder/blob/master/chroot_script/beagleboard.org.sh

If you want "supper minimal" aka git in lessthen 64MB there's a couple
switches for that..

Regards,

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

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

[beagleboard] Re: TFTP from u-boot: slow and buggy

[Tom Rini]

On Wednesday, January 8, 2014 11:47:12 AM UTC-5, l...@ansync.com wrote:
>
> I have a setup that loads u-boot onto the BBB over the serial port, and 
> then tells u-boot to load the .dtb and kernel from a local TFTP server. 
> Loading the small .dtb file works perfectly (although slowly), and 
> succeeds. Loading the kernel takes too long, causes lots of retries, and 
> finally errors out. If I manually get the kernel from that same TFTP server 
> onto my laptop, it loads in about 11 seconds--over wifi--so the server is 
> working fine. It's just u-boot's TFTP client that seems to be causing the 
> errors. I have seen other messages around the net advising changing the 
> server's block size to 1468, which I did, and telling u-boot to turn dcache 
> off, which isn't an option anymore, but it still fails.
>

Please note that (by accident) dcache isn't enabled for am335x targets 
until the upcoming release and turning off dcache will give slower, not 
faster, downloads.

Has anyone actually got this working? Which tftp server are you using, and 
> what parameters? Is there a patch to u-boot that might fix its client?
>
 
I'm slightly curious as to what / whose binary you were using that was 
failing to work so badly that it turned out to not be a cable issue (as I 
was thinking it might be, on starting to read this thread).

-- 
Tom

-- 
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/groups/opt_out.

Re: [beagleboard] TFTP from u-boot: slow and buggy

[Tom Rini]

On Wednesday, January 8, 2014 2:43:41 PM UTC-5, Vaibhav wrote:
>
> On Wed, Jan 8, 2014 at 2:31 PM, William Hermans 
> > wrote:
>
>> Any information you're willing to share as to how you load files via 
>> serial would be awesome. Personally, I love reading about this sort of 
>> thing . ..
>>
>>
> The steps are outlined here...
>
> http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User's_Guide
> It's for the AM335x EVM but it should be easy enough to adapt it to any 
> AM335x system.
>

Please note that the link above is for UART loading of MLO and U-Boot and 
not loading files in U-Boot itself via serial.  To do this in U-Boot the 
command is 'loady address'.

-- 
Tom

-- 
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/groups/opt_out.

Re: [beagleboard] A6A BBB - eMMC flashing issue?

[Robert Nelson]

On Fri, Jan 10, 2014 at 9:20 AM, fabrguer  wrote:
> Hi Robert,
>
> oh, I did not know that the images are not proved to work if installed with
> a Mac.
> The first time I tried to install another distro on the BBB (it was Ubuntu)
> I followed Adafruit instructions which are for a Mac and are basically the
> same.
> See the link:
> http://learn.adafruit.com/beaglebone-black-installing-operating-systems/mac-os-x
>
> Anyway I wrote:
> sudo dd if=./BBB..img of=/dev/disk1s1
^^

s1, isn't that "partition 1"...???

They show:

sudo diskutil unmount /dev/disk4s1
then:
sudo dd bs=1m if=~/Downloads/BBB-eMMC-flasher-2013.05.08.img of=/dev/rdisk4

with: /dev/disk4s1" changed to "/dev/rdisk4"

So you'd use.. of=/dev/rdisk1  right???

Regards,

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

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

Re: [beagleboard] Device tree overlays and kernel versions

[David Lambert]

On 01/10/2014 08:57 AM, Robert Nelson wrote:

On Fri, Jan 10, 2014 at 8:45 AM, David Lambert  wrote:

I am considering moving from RCN kernel 3.8.13-bone35.1 to 3.13.0-rc7 to
take advantage of some USB updates. It appears that device tree overlays are
not yet supported in the latter. My questions are:

1) Are my observations correct?
2) If this is true, then are device tree overlays being dropped in later
kernel versions?

"dropped" is really the wrong word to use...

NO ONE has taken up the effort to fully port the 3.8 "overlays" to 3.13...

Personally, i'm working on a workaround that works for me and for most
cape users.
Thanks Robert. I was thinking of a workaround also, but did not want to 
"reinvent a wheel". Could you point me to your thoughts? It seems to me 
that the major issue is setting up the pinmux and associated resource 
allocation.


I'm just guessing, but the guy who originally wrote the 3.8 overlay
system would probably take cash in trade to keep working on it..

When/if I have cash - I'll keep this in mind ;)

Regards,


Regards,



--
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/groups/opt_out.
<>

Re: [beagleboard] A6A BBB - eMMC flashing issue?

[fabrguer]

Hi Robert,

oh, I did not know that the images are not proved to work if installed with 
a Mac.
The first time I tried to install another distro on the BBB (it was Ubuntu) 
I followed Adafruit instructions which are for a Mac and are basically the 
same.
See the 
link: 
http://learn.adafruit.com/beaglebone-black-installing-operating-systems/mac-os-x

Anyway I wrote:
sudo dd if=./BBB..img of=/dev/disk1s1

Seems correct to me.
Btw, is it normal that, after writing the image on the microSD, the card 
becomes not visible by the Mac? It complains saying it is not compatible or 
something and it does not get mounted at all.

-- 
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/groups/opt_out.

[beagleboard] How to use Beagleboard image-builder?

[David M.]

I'm running a Beaglebone White with the latest Angstrom (and 3.8.13 kernel) 
and I want to move to the beta Debian distro that Jason talked about.
 
I have cloned the Git repo at https://github.com/beagleboard/image-builderon 
the Linux Mint virtual machine I use for ARM development, and I've run 
the script ./beagleboard.org_image.sh in the directory I use for 
development, just as I did for Angstrom.  It "worked" and pulled down lots 
of files, as I expected.
Where do I go from here?  What are my build options?  I want to customize 
the build to a minimal system without X, just as I did for Angstrom.
 
Thanks!
 

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

[beagleboard] ssh, telnet not responding after a few days of working.

[Emory Creel]

I purchased a bbb and used it for a day or two. eventually the ssh (putty) 
stopped responding.
The log was very sparse and only indicated that it connected:
Event Log: Writing new session log (SSH packets mode) to file: putty.log
Event Log: Looking up host "192.168.7.2"
Event Log: Connecting to 192.168.7.2 port 22

no login information appears, just a black, cold, empty putty window.

when i disconnect the window shuts down with: :"Network error: Software 
caused connection abort"

lights are flashing with the heartbeat pattern.

I can see the files on the mount, and apparently I can run bonescript.

I did try to adjust the time on the board, but not explicitly, only from 
the button on the web page.

A serial connection via telnet responds the same way. connection with zero 
dialogue.

I purchased two more bbb's, because I wanted to move forward with a little 
groping around as 
possible (there was no clear fix on the web), and now, after a few days, a 
second bbb is displaying precisely the
same issue.

I am using Windows 7 64 bit
I tried it on a 32 bit XP machine, but with no change in the bbbs behavior.

Any suggestions?

Clearly I need to deal with this issue.

I am going to upgrade the OS to try to fix it.

I am praying that it is not a hardware issue.  Would plugging and 
unplugging the usb cause problems?

Any insight would be appreciated.

-mandata
 


-- 
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/groups/opt_out.

[beagleboard] Re: SSH login issue

[vital]

Hi Duke,
If you are using a Unix based system, you can plugin the cable and use the 
"screen" command and then try to fix the ssh. 

On Wednesday, January 8, 2014 1:40:27 AM UTC-2, duk...@gmail.com wrote:
>
> Hi All,
>  When I got the BBB I changed the root password and I have used it for 2-3 
> months.
> Just 2 weeks ago, i can not login my BBB. I'm sure that I supply the 
> correct password.
> But no luck to login. Is there any way to reset the BBB root password? or 
> can I login with another user? Thank you in advance.
>
> Duke
>

-- 
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/groups/opt_out.

[beagleboard] Re: 'Opkg' Erros

[Pablo Oyarzo]

I'm getting the same thing.

-Pablo Oyarzo

-- 
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/groups/opt_out.

[beagleboard] Re: Windows 7 doesn't mount BBB as usb drive after update

[Emory Creel]

there is a similar issue with an individual on whose board the initial 
files that appeared on the 
usb mount were erased
https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/1qr04iE0EYc
the recommended solution was flashing, which started the issue for this 
group, but its
the same specific result, so I thought it might be possible the two issues 
are somehow related. just sayin'.

On Wednesday, January 8, 2014 1:23:27 PM UTC-5, JBodine wrote:
>
> Same problem here.   It worked on Windows 7 initially but no longer.   
>
> On Thursday, June 20, 2013 9:31:44 PM UTC-7, Richard Pesce wrote:
>>
>> Hello all!
>>
>> I recently received my Beaglebone Black.  I followed the getting started 
>> guide HERE , installed the 
>> drivers.  Afterwards I was able to connect to http://192.168.7.2 and use 
>> cloud9 etc.
>>
>> I got to the "Update board with latest software" portion and downloaded 
>> BBB-eMMC-flasher-2013.06.06.img.xz
>>  and 
>> flashed the eMMC successfully.  I removed the power, ejected the uSD and 
>> then connected to the computer via USB and the BBB wouldn't mount as a USB 
>> drive.  Fearing the update failed, I tried again with the same image.  That 
>> failed... so I tried 
>> BBB-eMMC-flasher-2013.06.20.img.xz
>>  from 
>> HERE and 
>> flashed again... still no USB drive.  I then tried 
>> BBB-eMMC-flasher-2013.06.17.img.xz
>>  from HERE ... 
>> still no USB drive.  In a last ditch effort I tried (Current Production 
>> Image) 
>> BBB-eMMC-flasher-2013.05.20.img.xz
>>  from 
>> HERE... 
>> still no USB drive.
>>
>>
>> LINUX:
>> It is important to note that I could SSH into all of these installs (not 
>> at http://192.168.7.2 though), and verified that everything worked 
>>  I can see /dev/mmcblk0p1 is mounted at /media/BEAGLEBONE (with my most 
>> current flash) and all the files are present.
>>
>> WINDOWS:
>> I searched in device manager and could not see the BBB at all or any 
>> unknown or not working hardware.  And in computer management/Disk 
>> management there isn't anything present.
>>
>> I have attempted other computers (WIN7) and multiple USB ports  same 
>> issue,
>>
>>
>> Anyone have any suggestions?  I'm sure I am missing something obvious.
>>
>>
>> Thank you 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/groups/opt_out.

Re: [beagleboard] Device tree overlays and kernel versions

[Robert Nelson]

On Fri, Jan 10, 2014 at 8:45 AM, David Lambert  wrote:
> I am considering moving from RCN kernel 3.8.13-bone35.1 to 3.13.0-rc7 to
> take advantage of some USB updates. It appears that device tree overlays are
> not yet supported in the latter. My questions are:
>
> 1) Are my observations correct?
> 2) If this is true, then are device tree overlays being dropped in later
> kernel versions?

"dropped" is really the wrong word to use...

NO ONE has taken up the effort to fully port the 3.8 "overlays" to 3.13...

Personally, i'm working on a workaround that works for me and for most
cape users.

I'm just guessing, but the guy who originally wrote the 3.8 overlay
system would probably take cash in trade to keep working on it..

Regards,

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

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

[beagleboard] Device tree overlays and kernel versions

[David Lambert]

I am considering moving from RCN kernel 3.8.13-bone35.1 to 3.13.0-rc7 to 
take advantage of some USB updates. It appears that device tree overlays 
are not yet supported in the latter. My questions are:


1) Are my observations correct?
2) If this is true, then are device tree overlays being dropped in later 
kernel versions?



Best regards,

Dave.


--
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/groups/opt_out.
<>

Re: [beagleboard] A6A BBB - eMMC flashing issue?

[Robert Nelson]

On Thu, Jan 9, 2014 at 11:34 PM, fabrguer  wrote:
> Hi Robert,
>
> thanks for the quick reply, you are fast!
> The card was in the Macbook SD slot (through an adapter), I dd it from the
> OSX terminal using the command as you showed.
> The terminal feedback was identical.
>
> When I powerup while pressing boot only the power LED close to power
> connector turns on. None of the 4 USR LED does.
> Any idea?

It sounds like the boot partition wasn't setup..

Since I don't have any Mac systems (really need to setup a cheap
hackintosh..) can you please confirm "exactly" how you dd'ed it just
encase you dumped it to a partition instead of the drive..

As I'm about to pull the trigger on a big announcement, it would be
nice if we knew the images could be dd'ed on mac..

Regards,

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

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

Re: [beagleboard] Re: Embedded Security

[Mike Bremford]

On 9 January 2014 21:51, rh_  wrote:

> On Thu, 9 Jan 2014 08:36:27 -0800 (PST)
> Martin AA6E 
> wrote:
>
> > This article by Bruce Schneier is sobering, and it applies to most of
> > us building embedded systems.  Some of us may get security updates
> > via repositories (e.g. Ubuntu), but generally you won't get new
> > kernels this way.  How many Beagle-ish systems are out there attached
> > to the Internet, but with ageing kernels and unpatched for a long
> > time? How can we manage this better in the future?
>
> Manage what? You mean taking kernel updates where you didn't before?
> Don't you just uncomment a couple of lines in a config file?
>
> As for sobering doesn't everyone by now know the state of "security"
> in regards to computing
>
>
It's a reasonable bet that in 2014, most desktop systems have automatic
upgrades turned on (or they're at least actively managed by someone). By
contrast, when was the last time you upgraded the firmware on your router?
Your TV? And in a few years, your fridge/light bulbs/running shoes/bathroom
scales?

Turn it around: if you're shipping a device with an embedded system
connected to the net, do you really want to enable automatic downloads of
new kernels? What if the upgrade fails? Do you provide a way for the user
to fix it ("short the reset pins on your light bulb..." - good luck getting
that one to market!), you issue an RMA or you suffer a reputation for
unreliability? All of those cost money. Schneier talks a lot of sense.

-- 
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/groups/opt_out.

Re: [beagleboard] Dose anyone tell me BBB signal pin selection?

[Gerald Coley]

Did you check the support Wiki?

http://www.elinux.org/Beagleboard:BeagleBoneBlack
http://www.elinux.org/Beagleboard:BeagleBone_Black_FAQ
http://www.elinux.org/Beagleboard:BeagleBone_Black_FAQ#Capes
http://www.elinux.org/Beagleboard:BeagleBone_Black_FAQ#What_is_the_process_for_disabling_the_HDMI_and_eMMC_Virtual_Capes.3F

Gerald



On Fri, Jan 10, 2014 at 3:46 AM,  wrote:

> Hi, I am very beginner of BBB.
> I'm planning to develop a machine and want to control it by BBB via the
> expansion headers (P8 & P9).
> To control the machine, 2 serial outputs (TXD/RXD) and 39 IO pins are
> required. Is it possible?
>
> Though I referred the BBB schematics, many processor signals of the
> expansion headers were already connected to eMMC or HDMI interface.
> I don't use HDMI. Is it no pobrolem to use the signals for the HDMI
> interface?
> And which signal pin mode (mode 0 - 7) should I select?
> Please tell me.
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone connection failures

[Gerald Coley]

Sure is large font. Did you try the support Wiki?.

Gerald


On Fri, Jan 10, 2014 at 1:37 AM, Agni Biswas wrote:

>
>
> i have a beaglebone black A5, i had the exact same problem when i am
>> booting up from the SD card, however when i am booting up from the emmc it
>> works fine, i tried formatting and re-installing the image but no avail .
>> please help.
>>
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] clock jumps suddenly

[Gerald Coley]

Any chance you can say which BeagleBoard this is?

Gerald



On Fri, Jan 10, 2014 at 6:14 AM,  wrote:

> Hello,
>
> I have a program running on my beagleboard and it use the system clock to
> know when do any task. I see my program doesn't work correctly but it isn't
> from my code is from the system clock because if I open the system log I've
>  seen time has changed but the ntp in few minutes changes to correct hour.
> Below I put portion of log where it sees.
>
>
> Jan 10 07:09:01 arm kernel: [68317.245056] omap_hwmod: wd_timer2:
> _wait_target_disable failed
> Jan 10 07:09:01 arm CRON[27466]: (CRON) info (No MTA installed, discarding
> output)
> Jan 10 07:09:01 arm kernel: [68317.266357] omap_wdt: Unexpected close, not
> stopping!
> Jan 10 07:09:01 arm CRON[27482]: (root) CMD (sleep 30 && echo "1" >
> /dev/watchdog)
> Jan 10 07:09:01 arm CRON[27487]: (ubuntu) CMD (/media/data/bin/apiwatch.sh
> > /dev/null 2>&1)
> Jan 10 07:09:01 arm CRON[27483]: (ubuntu) CMD
> (/media/data/bin/node_watchdog.sh > /dev/null 2>&1)
> Jan 10 07:09:01 arm CRON[27493]: (ubuntu) CMD
> (/media/data/bin/filesystem_watchdog.sh > /dev/null 2>&1)
> Jan 10 07:09:02 arm CRON[27467]: (CRON) error (grandchild #27475 failed
> with exit status 127)
> Jan 10 07:09:02 arm CRON[27467]: (CRON) info (No MTA installed, discarding
> output)
> Jan 11 19:34:39 arm kernel: [68321.077301] omap_hwmod: wd_timer2:
> _wait_target_disable failed
> Jan 11 19:34:39 arm kernel: [68321.120452] omap_hwmod: wd_timer2:
> _wait_target_disable failed
> Jan 11 19:34:39 arm kernel: [68321.153594] omap_wdt: Unexpected close, not
> stopping!
> Jan 11 19:34:39 arm CRON[27528]: (root) CMD (
> var/control/control_ejecucion_webchanges)
> Jan 11 19:34:39 arm CRON[27531]: (root) CMD (   /var/control/PowerCheck)
> Jan 11 19:34:39 arm CRON[27532]: (root) CMD
> (/var/control/control_ejecucion_wvdial.sh)
> Jan 11 19:34:39 arm CRON[27533]: (ubuntu) CMD (/media/data/bin/apiwatch.sh
> > /dev/null 2>&1)
> Jan 11 19:34:39 arm CRON[27535]: (root) CMD (echo "1" > /dev/watchdog)
> Jan 11 19:34:39 arm CRON[27529]: (root) CMD (sleep 30 && echo "1" >
> /dev/watchdog)
> Jan 11 19:34:39 arm CRON[27536]: (ubuntu) CMD
> (/media/data/bin/filesystem_watchdog.sh > /dev/null 2>&1)
> Jan 11 19:34:40 arm kernel: [68321.831054] omap_hwmod: wd_timer2:
> _wait_target_disable failed
> Jan 11 19:34:40 arm kernel: [68321.834625] omap_hwmod: wd_timer2:
> _wait_target_disable failed
> Jan 11 19:34:40 arm CRON[27542]: (ubuntu) CMD
> (/media/data/bin/node_watchdog.sh > /dev/null 2>&1)
> Jan 11 19:34:40 arm CRON[27515]: (CRON) info (No MTA installed, discarding
> output)
> Jan 11 19:34:40 arm kernel: [68321.968444] omap_wdt: Unexpected close, not
> stopping!
> Jan 11 19:34:40 arm CRON[27516]: (CRON) error (grandchild #27528 failed
> with exit status 127)
> Jan 11 19:34:40 arm CRON[27516]: (CRON) info (No MTA installed, discarding
> output)
> Jan 11 19:35:01 arm CRON[27580]: (root) CMD (echo "1" > /dev/watchdog)
> Jan 11 19:35:02 arm CRON[27581]: (root) CMD (   /var/control/PowerCheck)
> Jan 11 19:35:02 arm CRON[27579]: (root) CMD
> (/var/control/control_ejecucion_wvdial.sh)
> Jan 11 19:35:02 arm CRON[27582]: (root) CMD (sleep 30 && echo "1" >
> /dev/watchdog)
> Jan 11 19:35:02 arm kernel: [68344.509887] omap_hwmod: wd_timer2:
> _wait_target_disable failed
> Jan 11 19:35:02 arm CRON[27587]: (ubuntu) CMD (/media/data/bin/apiwatch.sh
> > /dev/null 2>&1)
> Jan 11 19:35:02 arm kernel: [68344.551696] omap_hwmod: wd_timer2:
> _wait_target_disable failed
> Jan 11 19:35:02 arm kernel: [68344.551788] omap_wdt: Unexpected close, not
> stopping!
> Jan 11 19:35:02 arm CRON[27571]: (CRON) info (No MTA installed, discarding
> output)
> Jan 11 19:35:02 arm CRON[27583]: (root) CMD (
> /var/control/control_ejecucion_webchanges)
> Jan 11 19:35:02 arm CRON[27588]: (root) CMD (sudo echo 3 >
>  /proc/sys/vm/drop_caches)
> Jan 11 19:35:02 arm CRON[27584]: (ubuntu) CMD
> (/media/data/bin/node_watchdog.sh > /dev/null 2>&1)
> Jan 11 19:35:02 arm CRON[27590]: (ubuntu) CMD
> (/media/data/bin/filesystem_watchdog.sh > /dev/null 2>&1)
> Jan 11 19:35:02 arm CRON[27593]: (root) CMD (/sbin/route add default gw
> 10.64.64.64 dev ppp0)
> Jan 11 19:35:02 arm CRON[27578]: (CRON) error (grandchild #27593 failed
> with exit status 7)
> Jan 11 19:35:02 arm CRON[27578]: (CRON) info (No MTA installed, discarding
> output)
> Jan 11 19:35:02 arm CRON[27572]: (CRON) error (grandchild #27583 failed
> with exit status 127)
> Jan 11 19:35:02 arm CRON[27572]: (CRON) info (No MTA installed, discarding
> output)
> Jan 10 07:09:37 arm kernel: [68352.680908] omap_hwmod: wd_timer2:
> _wait_target_disable failed
> Jan 10 07:09:37 arm kernel: [68352.692657] omap_hwmod: wd_timer2:
> _wait_target_disable failed
> Jan 10 07:09:37 arm kernel: [68352.700805] omap_wdt: Unexpected close, not
> stopping!
> Jan 10 07:09:37 arm CRON[27468]: (CRON) info (No MTA installed, discarding
> output)
> Jan 10 07:09:37 arm CRON[27633]: (root) CMD (sleep 30 &&

[beagleboard] Dose anyone tell me BBB signal pin selection?

[taka1963s]

Hi, I am very beginner of BBB.
I'm planning to develop a machine and want to control it by BBB via the 
expansion headers (P8 & P9).
To control the machine, 2 serial outputs (TXD/RXD) and 39 IO pins are 
required. Is it possible?
 
Though I referred the BBB schematics, many processor signals of the 
expansion headers were already connected to eMMC or HDMI interface.
I don't use HDMI. Is it no pobrolem to use the signals for the HDMI 
interface?
And which signal pin mode (mode 0 - 7) should I select?
Please tell me.

-- 
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/groups/opt_out.

[beagleboard] i2c2 file not present in the system

[Jyotirmaya Joon]

i2c2 file is not present in the sys/bus/ and i need to use i2c2 how to 
bring it to the system .

-- 
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/groups/opt_out.

[beagleboard] clock jumps suddenly

[ekaitzaznar]

Hello,

I have a program running on my beagleboard and it use the system clock to 
know when do any task. I see my program doesn't work correctly but it isn't 
from my code is from the system clock because if I open the system log I've 
 seen time has changed but the ntp in few minutes changes to correct hour. 
Below I put portion of log where it sees. 


Jan 10 07:09:01 arm kernel: [68317.245056] omap_hwmod: wd_timer2: 
_wait_target_disable failed
Jan 10 07:09:01 arm CRON[27466]: (CRON) info (No MTA installed, discarding 
output)
Jan 10 07:09:01 arm kernel: [68317.266357] omap_wdt: Unexpected close, not 
stopping!
Jan 10 07:09:01 arm CRON[27482]: (root) CMD (sleep 30 && echo "1" > 
/dev/watchdog)
Jan 10 07:09:01 arm CRON[27487]: (ubuntu) CMD (/media/data/bin/apiwatch.sh 
> /dev/null 2>&1)
Jan 10 07:09:01 arm CRON[27483]: (ubuntu) CMD 
(/media/data/bin/node_watchdog.sh > /dev/null 2>&1)
Jan 10 07:09:01 arm CRON[27493]: (ubuntu) CMD 
(/media/data/bin/filesystem_watchdog.sh > /dev/null 2>&1)
Jan 10 07:09:02 arm CRON[27467]: (CRON) error (grandchild #27475 failed 
with exit status 127)
Jan 10 07:09:02 arm CRON[27467]: (CRON) info (No MTA installed, discarding 
output)
Jan 11 19:34:39 arm kernel: [68321.077301] omap_hwmod: wd_timer2: 
_wait_target_disable failed
Jan 11 19:34:39 arm kernel: [68321.120452] omap_hwmod: wd_timer2: 
_wait_target_disable failed
Jan 11 19:34:39 arm kernel: [68321.153594] omap_wdt: Unexpected close, not 
stopping!
Jan 11 19:34:39 arm CRON[27528]: (root) CMD (   
var/control/control_ejecucion_webchanges)
Jan 11 19:34:39 arm CRON[27531]: (root) CMD (   /var/control/PowerCheck)
Jan 11 19:34:39 arm CRON[27532]: (root) CMD 
(/var/control/control_ejecucion_wvdial.sh)
Jan 11 19:34:39 arm CRON[27533]: (ubuntu) CMD (/media/data/bin/apiwatch.sh 
> /dev/null 2>&1)
Jan 11 19:34:39 arm CRON[27535]: (root) CMD (echo "1" > /dev/watchdog)
Jan 11 19:34:39 arm CRON[27529]: (root) CMD (sleep 30 && echo "1" > 
/dev/watchdog)
Jan 11 19:34:39 arm CRON[27536]: (ubuntu) CMD 
(/media/data/bin/filesystem_watchdog.sh > /dev/null 2>&1)
Jan 11 19:34:40 arm kernel: [68321.831054] omap_hwmod: wd_timer2: 
_wait_target_disable failed
Jan 11 19:34:40 arm kernel: [68321.834625] omap_hwmod: wd_timer2: 
_wait_target_disable failed
Jan 11 19:34:40 arm CRON[27542]: (ubuntu) CMD 
(/media/data/bin/node_watchdog.sh > /dev/null 2>&1)
Jan 11 19:34:40 arm CRON[27515]: (CRON) info (No MTA installed, discarding 
output)
Jan 11 19:34:40 arm kernel: [68321.968444] omap_wdt: Unexpected close, not 
stopping!
Jan 11 19:34:40 arm CRON[27516]: (CRON) error (grandchild #27528 failed 
with exit status 127)
Jan 11 19:34:40 arm CRON[27516]: (CRON) info (No MTA installed, discarding 
output)
Jan 11 19:35:01 arm CRON[27580]: (root) CMD (echo "1" > /dev/watchdog)
Jan 11 19:35:02 arm CRON[27581]: (root) CMD (   /var/control/PowerCheck)
Jan 11 19:35:02 arm CRON[27579]: (root) CMD 
(/var/control/control_ejecucion_wvdial.sh)
Jan 11 19:35:02 arm CRON[27582]: (root) CMD (sleep 30 && echo "1" > 
/dev/watchdog)
Jan 11 19:35:02 arm kernel: [68344.509887] omap_hwmod: wd_timer2: 
_wait_target_disable failed
Jan 11 19:35:02 arm CRON[27587]: (ubuntu) CMD (/media/data/bin/apiwatch.sh 
> /dev/null 2>&1)
Jan 11 19:35:02 arm kernel: [68344.551696] omap_hwmod: wd_timer2: 
_wait_target_disable failed
Jan 11 19:35:02 arm kernel: [68344.551788] omap_wdt: Unexpected close, not 
stopping!
Jan 11 19:35:02 arm CRON[27571]: (CRON) info (No MTA installed, discarding 
output)
Jan 11 19:35:02 arm CRON[27583]: (root) CMD (   
/var/control/control_ejecucion_webchanges)
Jan 11 19:35:02 arm CRON[27588]: (root) CMD (sudo echo 3 > 
 /proc/sys/vm/drop_caches)
Jan 11 19:35:02 arm CRON[27584]: (ubuntu) CMD 
(/media/data/bin/node_watchdog.sh > /dev/null 2>&1)
Jan 11 19:35:02 arm CRON[27590]: (ubuntu) CMD 
(/media/data/bin/filesystem_watchdog.sh > /dev/null 2>&1)
Jan 11 19:35:02 arm CRON[27593]: (root) CMD (/sbin/route add default gw 
10.64.64.64 dev ppp0)
Jan 11 19:35:02 arm CRON[27578]: (CRON) error (grandchild #27593 failed 
with exit status 7)
Jan 11 19:35:02 arm CRON[27578]: (CRON) info (No MTA installed, discarding 
output)
Jan 11 19:35:02 arm CRON[27572]: (CRON) error (grandchild #27583 failed 
with exit status 127)
Jan 11 19:35:02 arm CRON[27572]: (CRON) info (No MTA installed, discarding 
output)
Jan 10 07:09:37 arm kernel: [68352.680908] omap_hwmod: wd_timer2: 
_wait_target_disable failed
Jan 10 07:09:37 arm kernel: [68352.692657] omap_hwmod: wd_timer2: 
_wait_target_disable failed
Jan 10 07:09:37 arm kernel: [68352.700805] omap_wdt: Unexpected close, not 
stopping!
Jan 10 07:09:37 arm CRON[27468]: (CRON) info (No MTA installed, discarding 
output)
Jan 10 07:09:37 arm CRON[27633]: (root) CMD (sleep 30 && echo "1" > 
/dev/watchdog)
Jan 10 07:09:37 arm CRON[27634]: (root) CMD (   /var/control/PowerCheck)
Jan 10 07:09:37 arm CRON[27636]: (root) CMD (   
/var/control/control_ejecucion_webchanges)
Jan 10 07:09:37 arm CRON[27635]: (ubuntu) CMD (/media/data

Re: [beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support

[Christian Ruocco]

Hi guys,

I’ll get on that when I have a moment. Probably this weekend!

l8r,

Xris


On 09 Jan 2014, at 19:16, crystal.69.kit...@gmail.com wrote:

> I would like to see that image as well.
> 
> Thanks
> 
> On Tuesday, January 7, 2014 1:54:41 PM UTC-6, ebi...@gmail.com wrote:
> Hi Christian Ruocco 
> 
> Could you please send me a link to download the prebuilt image of the ubuntu 
> that you mention? So i can test it.
> 
> I'll appreciate that. Sorry about my english.
> 
> Regards.
> 
> Esteban Binsak
> 
> El sábado, 4 de enero de 2014 17:42:20 UTC-3, Christian Ruocco escribió:
> Hey guys,
> 
> I got Ubuntu 12.04 running with the BBB and touchscreen working (Chipsee 
> 1024x600 7”) months ago, simply by using the Chipsee kernel with the ubuntu 
> rootfs and rebuilding other goodies against the Chipsee kernel source (like 
> the SGX OPEN GL ES 2.0 drivers).
> 
> Currently I need to boot off the SD card though, but adding the MMC support 
> to the chip see kernel doesn’t seem like a biggie.
> 
> Does that help anybody? Or am I missing something? Obviously trying to 
> apt-get kernel related packages will break it but most stuff works.
> 
> l8r,
> Xris.
> 
> On 04 Jan 2014, at 19:21, Mahammad  wrote:
> 
>> I passed with same experience trying to run ubuntu with the capacitive and 
>> the black beaglebone. I can confirm steps above are very useful. But you 
>> will have two problems when it come to BBB:
>> - That old version of kernel will hang on Beaglebone Black.
>> - Capacitive touch will not work.
>> 
>> I started with 3.2.42-psp27 and then spent like 2 days merging changes 
>> Chipsee made to have things working on BBB. Can summarize changes to:
>> - Copied the /arch/arm folder from Chipsee kernel. That helped the kernel to 
>> operate on BBB.
>> - Copy the capacitive touch driver from under /drivers/input/touchscreen/ 
>> (ft5x0x_ts.c/h and eeti_ts.c). Please copy the folder in full as it also has 
>> the Kbuild, and Makefile changes. And while mearging I note all changes in 
>> the folder where made to support the touch.
>> - During rebuild, and under the config tool; enable the touch driver under 
>> device drivers/input/touchscreen.
>> - Install lxde gnu (apt-get install lxde). Without a gnu the screen will 
>> stay black. It could have a prompt somewhere outside the screen boundries 
>> you can test if you have a keyboard.. but none of my keyboards or mice 
>> worked with that kernel. I am investigating this now. I could had messed up 
>> something while merging.
>> 
>> No changes to uEnv.txt It finally worked with touch.
>> 
>> This is not the best solution anyway.. but just to move forward. My next 
>> milestone is to have it working with kernel 3.8.13.. anyone succeeded 
>> extracting the device tree partially or in full?
>> 
>> -- 
>> 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/Y-rcKPITy0Q/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
> 

-- 
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/groups/opt_out.

[beagleboard] Test Message 2

[John Syne]

-- 
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/groups/opt_out.

[beagleboard] Re: 'Opkg' Erros

[Alex A.]

My first post on this list, but have been following it for quite some time 
now.  Out of my handy text file of useful BBB info I've been collectiing, 
I've got this:  (type each line in exactly as it appears, and press the 
ENTER key at the end)


  - /sbin/route add default gw 192.168.7.1
  - echo "nameserver 8.8.8.8" >> /etc/resolv.conf


Your BBB will now (or should) have internet access through just the USB 
connection.


On Wednesday, January 8, 2014 12:45:22 PM UTC-6, Pablo Oyarzo wrote:
>
>
>
> I got my BBB conected through USB to my desktop, and my router is conect 
> to my desktop through ethernet cable.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Test Message

[John Syn]

On 1/9/14, 7:26 PM, "evilwulfie"  wrote:

>google groups does not send your post back to you
Thank you, you are a life saver.
>
>On 1/9/2014 5:07 PM, John Syne wrote:
>>
>>
>> -- 
>> 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/groups/opt_out.
>
>-- 
>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/groups/opt_out.


-- 
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/groups/opt_out.

[beagleboard] New nrf24l01 bonescript library

[thiago . rdp]

I've just developed the first version of a library to interface with the 
nrf24l01 module.

Here it is: https://github.com/thiagorp/bbb-nrf24l01

-- 
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/groups/opt_out.

Re: [beagleboard] Test Message

[John Syn]

On 1/9/14, 7:26 PM, "evilwulfie"  wrote:

>google groups does not send your post back to you

This is very strange. When I used a non gmail e-mail address, I could see
all my postings. Now that I use a gmail address, I cannot see my postings
on the e-mail list. Why is that.

I post messages to help new users, but I also used these postings as notes
to myself that I can lookup weeks or months later. Searching these
messages in my e-mail client was convenient, but now I have to search
google groups and that isn¹t very convenient for me. Is there any way to
work around this issue?

Regards,
John
>
>On 1/9/2014 5:07 PM, John Syne wrote:
>>
>>
>> -- 
>> 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/groups/opt_out.
>
>-- 
>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/groups/opt_out.


-- 
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/groups/opt_out.

[beagleboard] Test Message 4

[John Syn]

-- 
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/groups/opt_out.

Re: [beagleboard] Re: npm install bonescript Error

[Jason Kridner]

Not sure why that, but I've found a newer work-around to the original
problem that avoids editing configure.js:

TERM=dumb npm install -g bonescript

On Thu, Jan 9, 2014 at 1:34 PM,   wrote:
> I know that this is an old thread now, but I had the same problems, followed
> this solution and now I am getting an error about node-gyp failing to import
> module filecmp. Any ideas?
>
> Thanks, Josh
>
>
> On Wednesday, June 19, 2013 8:41:01 AM UTC-5, Jason Kridner wrote:
>>
>> B,
>>
>> I got tired of looking for your e-mail on the mailing list, so I'll just
>> put the list in reply.  This is the danger of e-mailing me support questions
>> directly--not something I like too much.
>>
>> On Tue, Jun 18, 2013 at 7:29 PM, B Parvizi  wrote:
>>>
>>> Hi,
>>>
>>> I was trying to install bonescript using npm, and I receive the following
>>> error below.  I can get the updated code using:
>>>
>>> opkg update
>>> opkg install bonescript
>>>
>>> but was hoping I could use npm so I can list bonescript as a dependency
>>> in my packages.json file.   Any help would be appreciated, thanks.  Here is
>>> the error:
>>>
>>> root@beaglebone:/var/lib/cloud9/bb-servo-example# npm install bonescript
>>> --save
>>> npm WARN package.json bb-servo-example@0.0.0 No README.md file found!
>>> npm http GET http://registry.npmjs.org/bonescript
>>> npm http 304 http://registry.npmjs.org/bonescript
>>>
>>> > bonescript@0.2.2 preinstall
>>> > /var/lib/cloud9/bb-servo-example/node_modules/bonescript
>>> > node-gyp clean || (exit 0); node-gyp configure build
>>>
>>> gyp ERR! configure error
>>> gyp ERR! stack Error: Python executable "python" is v2.7.3, which is not
>>> supported by gyp.
>>> gyp ERR! stack You can pass the --python switch to point to Python >=
>>> v2.5.0 & < 3.0.0.
>>> gyp ERR! stack at failPythonVersion
>>> (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:118:14)
>>> gyp ERR! stack at
>>> /usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:107:9
>>> gyp ERR! stack at ChildProcess.exithandler (child_process.js:538:7)
>>> gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:99:17)
>>> gyp ERR! stack at maybeClose (child_process.js:638:16)
>>> gyp ERR! stack at Process._handle.onexit (child_process.js:680:5)
>>
>>
>> I added a couple of debug commands to
>> /usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js and found
>> that 'semver.lt' returns false when comparing 2.7.3 and 3.0.0.  This is a
>> bug in semver/node-gyp and not BoneScript.  I simply commented out the
>> comparison and the build completed for me.
>>
>> Note, you do need to perform the following steps for node-gyp to run on an
>> Angstrom install that might not already have python-compiler:
>> # opkg update
>> # opkg install python-compiler
>>
>>>
>>> gyp ERR! System Linux 3.8.13
>>> gyp ERR! command "node"
>>> "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js"
>>> "configure" "build"
>>> gyp ERR! cwd /var/lib/cloud9/bb-servo-example/node_modules/bonescript
>>> gyp ERR! node -v v0.8.22
>>> gyp ERR! node-gyp -v v0.8.5
>>> gyp ERR! not ok
>>> npm ERR! bonescript@0.2.2 preinstall: `node-gyp clean || (exit 0);
>>> node-gyp configure build`
>>> npm ERR! `sh "-c" "node-gyp clean || (exit 0); node-gyp configure build"`
>>> failed with 1
>>> npm ERR!
>>> npm ERR! Failed at the bonescript@0.2.2 preinstall script.
>>> npm ERR! This is most likely a problem with the bonescript package,
>>> npm ERR! not with npm itself.
>>> npm ERR! Tell the author that this fails on your system:
>>> npm ERR! node-gyp clean || (exit 0); node-gyp configure build
>>> npm ERR! You can get their info via:
>>> npm ERR! npm owner ls bonescript
>>> npm ERR! There is likely additional logging output above.
>>>
>>> npm ERR! System Linux 3.8.13
>>> npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "bonescript"
>>> "--save"
>>> npm ERR! cwd /var/lib/cloud9/bb-servo-example
>>> npm ERR! node -v v0.8.22
>>> npm ERR! npm -v 1.2.14
>>> npm ERR! code ELIFECYCLE
>>> npm ERR!
>>> npm ERR! Additional logging details can be found in:
>>> npm ERR! /var/lib/cloud9/bb-servo-example/npm-debug.log
>>> npm ERR! not ok code 0
>>>
>>>
>>
> --
> 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/groups/opt_out.

-- 
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/groups/opt_out.

Re: [beagleboard] Re: BBB, Ubuntu 13.10 (RCN distro) - stk1160 (EasyCap) not recognized

[Mahammad]

Hello

Did you manage to make the mainline driver work?

Regarding power, the module consumes like 200ma while work. I doubt power 
is an issue.

I managed to make it work with the old easycap driver made by Thomas work 
with 3.2.0 psp linux with DMA on. But it stop capture in a few seconds. I 
am trying to make the make mainlined stk1160 driver work. Did anyone 
succeed making it work?

Best Regards

Mahammad





On Thursday, October 3, 2013 3:38:03 AM UTC+2, Paul Hannah wrote:
>
> Is it viable to get a cheap hub and manually wire the 5V to that hub from 
> the 5V in, completely bypassing the BBB's circuits entirely? Or are there 
> gotchas with that also, initialisation timing or something else I haven't 
> thought of?
>
>
> On Thu, Oct 3, 2013 at 10:27 AM, garyamort 
> > wrote:
>
>>
>>
>> On Wednesday, October 2, 2013 4:56:34 PM UTC-4, Ivan Korman wrote:
>>>
>>> Any further hint?
>>>
>>>
>> So, finally googled skt1160 and after looking through the results, I'm 
>> thinking the issue might be the device.  Based on 
>> http://www.raspberrypi.org/phpBB3/viewtopic.php?f=33&t=18831&sid=057d5de92feb665cf10f4905c1929e32
>>  where 
>> you have many different people having varying degrees of failures - 
>> including some where it works only if plugged in upon bootup and not 
>> unplugged, and others where they have to periodically unplug it and plug it 
>> back in - my guess is that because this chip is so generic that the quality 
>> of production is all over the place.
>>
>> I'd also guess that your issue is related to power.   Even though your 
>> BBB has a decent power supply, I'm betting that TI was very careful with 
>> power regulation for the USB host and it just will NOT supply more than 
>> 500mA of power[which is what it is clearly rated to for and which is more 
>> than enough for any USB compliant device].
>>
>> Wheras if the producer of your your particular device was sloppy/didn't 
>> care they may need more than 500mA which most PC's these days will provide 
>> despite it being so far out of spec.
>>
>>  
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] Custom Beaglebone Black does not bootup unless UART0 port is used

[nitesh singh]

Hi,

Thanks Don for replying.

I do not know how are those partitions created, mmcblk0boot0 and
mmcblk0boot1 . Only, two partitions are created as far as i know, boot and
rootfs.
Which script from Robert Nelson are you referring to ?

Thanks and regards,
Nitesh Singh


On Fri, Jan 10, 2014 at 1:44 PM, Don deJuan  wrote:

> On 01/09/2014 11:14 PM, nitesh singh wrote:
> > Hi,
> >
> > I am using a customised Beaglebone Black, whose schematics is very close
> to
> > Original Beaglebone Black.  You can say we cloned the Beaglebone black
> > hardware and assembled the board.
> >
> > Now I used Robert C Nelson's Debian wheezy emmc flasher image sd card to
> > boot it for first time , and wrote the emmc. Then I dumped binary data
> > copied from EEPROM of one of the original beaglebone black's eeprom to
> the
> > eeprom on this.
> >
> > So, now the issue that i am facing is that, this board will not boot up
> > again from emmc or another sd card that i use, other than the flasher sd
> > card.
> > Then accidently or by chance, i tried to look at its UART0 port from UART
> > port on the other beaglebone black and it booted up as usual.
> >
> > After that i observed that this customised beaglebone black is booting
> only
> > when the UART0 is accessed on another Beaglebone black or just simply
> > connected to its UART.
> >
> > What can be the problem here ? The emmc flashed on another original
> > beaglebone black is working fine, just this customised board will not
> boot
> > in the usual manner.
> >
> > I was reading through the minicom output at UART0 for this custom board,
> it
> > gave some read errors, and also said that mmcblk0boot0 and mmcblk0boot1
> > does not valid partition table.
> I would start here and properly partition. The rest should come after
> that part. Take a look at robert nelsons scripts for guidence if you do
> not know what to do.
>
> > What are these partitions and is it possible to write or create any
> > partitions on them ?  I have seen that they are there on other beaglebone
> > blacks and mmcblk0 changes to mmcblk1 if booted from sd card, I could not
> > understand its function. Is this creating any problem with the bootup ? I
> > suspect the eeprom data also might be causing this error.
> >
> > I have attached the minicom output file for the custom board's UART0 port
> > while it was booting.
> >
> > One more thing, it seems, connecting only DGND and UART0_RX to another
> > board is sufficient to make it boot. So it is reading some data over
> Uart0,
> > is it to do with eeprom ?
> >
> > Please help.
> >
> > Thanks and regards,
> > Nitesh
> >
>
> --
> 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/1rbO7JGhppw/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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] Re: recommend usb external drive for booting?

[cwrseckford]

On Tuesday, January 7, 2014 9:21:49 PM UTC, Rusty Wright wrote:
>
> Can anyone recommend a usb drive for using to boot off of?  From what I 
> understand the drive needs to be externally powered, not powered from usb, 
> and I can only find ones that are powered over usb.
>
> Thanks.
>
 
I started by booting the BBB from an SD Card with one of Robert Nelson's
images, then moved to booting from a USB stick (by copying the file system
image across and updating uEnv.txt).  The stick went read-only after a few
days, and I looked at a portable USB HD - I can't remember if I got it
booting or not.  In the end it seemed easier to fetch the kernel via TFTP
and then boot via NFS - again, it was just a question of updating uEnv.txt

An NFS-loaded kernel makes cross-compling and general messing around a lot
easier, it's reasonably quick, and I wouldn't develop stuff any other way.
However, while setting up TFTP and NFS you _must_ monitor the BBB console
(FTDI) during startup - there are too many details in the set-up to get
everything right the first time.

I access the BBB via ssh across the network; mostly it boots correctly just
by powering it up, but one time in ten or twenty it hangs.  This problem
prevents unattended operation, and I haven't solved it.


Will

 

-- 
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/groups/opt_out.

Re: [beagleboard] Re: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[littlefreaky36]

> Do you need the JavaFX 8 graphics capabilities?  If not, can you run it 
with graphics disabled?

I do need the graphics capabilities (otherwise I wouldn't use FX ;-) so I 
cannot disable the graphics.

> On the chance that there might be useful information in them, here are 
two links for java I have from my days of noodling around with the raspi: 
...

Thanks for the links but unfortunately they don't help. I have a Raspi and 
I can also run my JavaFX applications on it without problems. But they are 
rather slow on the Raspi so I wanted to do some performance tests with the 
BBB hardware.

-- 
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/groups/opt_out.

Re: [beagleboard] Custom Beaglebone Black does not bootup unless UART0 port is used

[Don deJuan]

On 01/09/2014 11:14 PM, nitesh singh wrote:
> Hi, 
>
> I am using a customised Beaglebone Black, whose schematics is very close to 
> Original Beaglebone Black.  You can say we cloned the Beaglebone black 
> hardware and assembled the board.
>
> Now I used Robert C Nelson's Debian wheezy emmc flasher image sd card to 
> boot it for first time , and wrote the emmc. Then I dumped binary data 
> copied from EEPROM of one of the original beaglebone black's eeprom to the 
> eeprom on this.
>
> So, now the issue that i am facing is that, this board will not boot up 
> again from emmc or another sd card that i use, other than the flasher sd 
> card. 
> Then accidently or by chance, i tried to look at its UART0 port from UART 
> port on the other beaglebone black and it booted up as usual. 
>
> After that i observed that this customised beaglebone black is booting only 
> when the UART0 is accessed on another Beaglebone black or just simply 
> connected to its UART.
>
> What can be the problem here ? The emmc flashed on another original 
> beaglebone black is working fine, just this customised board will not boot 
> in the usual manner. 
>
> I was reading through the minicom output at UART0 for this custom board, it 
> gave some read errors, and also said that mmcblk0boot0 and mmcblk0boot1 
> does not valid partition table. 
I would start here and properly partition. The rest should come after
that part. Take a look at robert nelsons scripts for guidence if you do
not know what to do.

> What are these partitions and is it possible to write or create any 
> partitions on them ?  I have seen that they are there on other beaglebone 
> blacks and mmcblk0 changes to mmcblk1 if booted from sd card, I could not 
> understand its function. Is this creating any problem with the bootup ? I 
> suspect the eeprom data also might be causing this error.
>
> I have attached the minicom output file for the custom board's UART0 port 
> while it was booting. 
>
> One more thing, it seems, connecting only DGND and UART0_RX to another 
> board is sufficient to make it boot. So it is reading some data over Uart0, 
> is it to do with eeprom ?
>
> Please help. 
>
> Thanks and regards, 
> Nitesh
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[Giuseppe Iellamo]

And it worked!

Thank you very much John and Robert!

Now I'm heading to QT5 realm!



Il giorno giovedì 9 gennaio 2014 21:50:46 UTC+1, john3909 ha scritto:
>
>
> From: Giuseppe Iellamo >
> Reply-To: >
> Date: Thursday, January 9, 2014 at 8:11 AM
> To: >
> Subject: [beagleboard] Re: JavaFX 8 on BeagleBone Black (SGX driver 
> problem?)
>
> Sorry I can't help you but maybe you can help me.
>
> I'm using your exact configuration...
>
> But I still read 
>
>
>
>
>
>
>
> *root@arm:/opt/Graphics_SDK_setuplinux_5_00_00_01/gfxsdkdemos/ogles2# 
> ./OGLES2ChameleonMan PVRShell: EGL 1.4 initializedExit message has been set 
> to: "PVRShell: Unable to create surface".InitAPI failed!PVRShell: Unable to 
> create surface*
> I've loaded the modules, I've installe the libraries in 
> *gfx_rel_es8.x*
>
> Please tell me what did you load from the Graphics SDK?
>
> Hi Giuseppe,
>
> Here is what I did to make this work:
>
> Download the Graphics SDK from here:
>
>
> http://software-dl.ti.com/dsps/dsps_public_sw/gfxsdk/5_01_00_01/index_FDS.html
>
> Use the hardfp version if you are using Debian.
>
> Make the file executable and install. Update the Rules.make file to 
> reflect your environment. Here is an example:
> =
> #  is your login userid
> HOME=/home/
>
> # Set Toolchain path. I installed Linaro via apt-get install 
> arm-linux-gnueabihf-gcc
> CSTOOL_DIR=/usr
>
> # Set Tool chain prefix (ex arm-arago-linux-gnueabi- )
> CSTOOL_PREFIX=arm-linux-gnueabihf-
>
> # Set kernel installation path ( ex /home/user/linux-04.00.01.13 )
> KERNEL_INSTALL_DIR=${HOME}/GIT/linux-dev-3.12/KERNEL
>
> # Set Target filesystem path ( ex /home/user/targetfs )
> TARGETFS_INSTALL_DIR=/mnt//rootfs
>
> # Set installation folder
> GRAPHICS_INSTALL_DIR=${HOME}/Graphics/Graphics_SDK_5_01_00_01_hardfp
> ==
>
> Host > make BUILD=release OMAPES=8.x PM_RUNTIME=1 all
> # Insert SDCARD and I’m assuming the rootfs is mounted at 
> /mnt//rootfs from Rules.make file above
> Host > sudo make BUILD=release OMAPES=8.x PM_RUNTIME=1 install
>
> After you boot your BBB, run
> BBB > sudo /etc/init.d/335x-demo
> # Reboot
> BBB > sudo /etc/init.d/rc.pvr start
>
> Now run the demos and everything should work fine.
>
> Regards,
> John
>
>
>
> Il giorno giovedì 9 gennaio 2014 10:40:35 UTC+1, littlef...@gmail.com ha 
> scritto:
>>
>> Hello,
>>
>> I am trying to run the newest JavaFX 8 snapshot release on the beaglebone 
>> black. So far I haven't got it running, the debug output shows the 
>> following:
>>
>> Multi-Threading Enabled
>> Prism pipeline init order: es2 
>> Using platform text rasterizer
>> Using java-based Pisces rasterizer
>> Using dirty region optimizations
>> Not using texture mask for primitives
>> Not forcing power of 2 sizes for textures
>> Using hardware CLAMP_TO_ZERO mode
>> Opting in for HiDPI pixel scaling
>> Prism pipeline name = com.sun.prism.es2.ES2Pipeline
>> Loading ES2 native library ... prism_es2_eglfb
>> Loaded /opt/jdk1.8.0/jre/lib/ext/../arm/libprism_es2_eglfb.so from 
>> relative path
>> succeeded.
>> GLFactory using com.sun.prism.es2.EGLFBGLFactory
>> *eglGetConfigAttrib failed!(X)* Got class = class 
>> com.sun.prism.es2.ES2Pipeline
>> GraphicsPipeline.createPipeline: error initializing pipeline 
>> com.sun.prism.es2.ES2Pipeline
>> Graphics Device initialization failed for :  es2
>> Error initializing QuantumRenderer: no suitable pipeline found
>>
>>
>> What I've done:
>>
>> - Installed the Ubuntu 13.10 image from Robert C Nelson (
>> https://rcn-ee.net/deb/rootfs/saucy/ubuntu-13.10-console-armhf-2013-12-17.tar.xz
>> )
>> - Compiled the kernel from 
>> https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.12 and 
>> installed it
>> - Used the 
>> sgx_build_modules.shscript
>>  from the git repo above to download and compile the SGX drivers
>> - Copied the drivers to the SD card and installed it on the BBB
>> - I had to manually load the omaplfb module, as it doesn't seem to be 
>> loaded automatically (bufferclass_ti and pvrsrvkm are loaded automatically)
>> - After that, the SDK demos (OGLES2ChameleonMan and OGLES2MagicLantern) 
>> seem to work fine
>> - When starting a JavaFX application, it fails during startup with the 
>> log mentioned above (tried to enable all possible debug output)
>>
>>
>> I've found the error string in the OpenJFX sources, but to get more 
>> information, I'd need to create a debug build of the prism-es2 module (or 
>> maybe from the whole OpenJDK), which at this point I don't know how to do. 
>> Maybe somebody knows what the problem might be.
>>
>> From 
>> /rt/modules/graphics/src/main/native-prism-es2/eglfb/EGLFBGLFactory.c:
>>
>> ...
>> if (!eglChooseConfig(egldisplay, eglAttrs, &config, 1, &numconfigs)) {
>> fprintf(stderr, "Failed to get a FBconfig with requested 
>> attrs\n");
>> //cleanup
>> return 0;
>> }
>>
>> #ifdef DEBUG
>> printf("eglChooseCo