[beagleboard] my beagle bone black doesnt connect to ssh or the START.HTM any more

2018-01-23 Thread sguzman723
when i connect my beagle bone black to my computer, it reads it as some 
Ethernet connection. also a green led lights up in the Ethernet port. it 
doesn't work on the putty x64 ssh, but serial does work without a problem.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/39368d36-eaa6-4219-9a4e-9b1661cbfdb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] temperature range for bbb rev.c

2018-01-23 Thread nik600
Dear all

i'd like to know if is possible to find some kind of "official" answer 
about the temperature range of BBB rev.C, i've read that the BBB industrial 
version has a range of -40°C to +85°C but is not clear what is the range of 
the standard BBB rev. C.

I've also found some old post talking about different ranges: someone talks 
abount 0-50, some ohter about 70, other says that we must check all the BOM 
and look for the working range of all the components.

Now, i have 2 question:

1) in the meaningtime is there any news or we have to check again the BOM ?

2) in test-field enviroment i'm experiencing a specific problem: a BBB 
REV.C is working in a case with internal temperature of 60°, after 2 days 
it stop to respond (the BBB is not reachable via TCP/IP) and even the 
reboot does nothing, if i cool the case under 50° the BBB starts again.

Now, the problem seems to be quite related to the temperature, but just to 
be sure i'd like to know if is possible to debug this situation and 
understand what is blocking the boot process.

The system doesn't boot because of some internal protection related to the 
temperature or it is just a related event of some hardware failure?

Thanks to all 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ad884deb-a519-47cf-b76f-6539e535b35a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: Change USB OTG mode to USB host and USB peripheral

2018-01-23 Thread Robert Nelson
On Tue, Jan 23, 2018 at 1:07 PM,   wrote:
> Hey, 2 years later...
>
> Have you managed to solve your problem? I'm facing similar problem with my
> NanoPi Neo Air. I cannot seem to change the way OTG is handled - there is no
> dr_mode any more.

Well, it looks like someone needs to complete the musb options for the
NanoPi Neo Air

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/sun8i-h3-nanopi-neo-air.dts

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgsh5SMr%3Dr_Rpnb_oKCuGBSAwb66yEuEiRuYnz53hWZHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: Change USB OTG mode to USB host and USB peripheral

2018-01-23 Thread felipe
Hey, 2 years later...

Have you managed to solve your problem? I'm facing similar problem with my 
NanoPi Neo Air. I cannot seem to change the way OTG is handled - there is 
no dr_mode any more.

Em quinta-feira, 5 de novembro de 2015 05:35:05 UTC-3, Ison Thomas escreveu:
>
> Hi
>
> I am using a custom hardware which is based on Beaglebone black. The 
> hardware difference between BBB and our board is that USB0 is changed to 
> work in host mode and USB1 in peripheral mode. I need to make the necessary 
> changes in kernel as well to make this work. I have built the kernel and 
> uboot based on the instructions given in 
> http://elinux.org/Building_BBB_Kernel. 
>
> As far as I understand, to change the behaviour of USB port, we need to 
> change the corresponding dts file. So I tried to edit the 'am33xx.dtsi' and 
> 'am335x-bone-common.dtsi' files and change the 'dr_mode' value of the USBs. 
> I have seen the 'dr_mde" in the previous versions of these files but in the 
> latest ones this is missing and I assume the USB ports are configured for 
> OTG mode.
>
> am33xx.dtsi (latest) :
>
>  " usb_otg_hs: usb@4740 {
> compatible = "ti,musb-am33xx";
> reg = <0x4740 0x1000/* usbss */
>0x47401000 0x800 /* musb instance 0 
> */
>0x47401800 0x800>;   /* musb instance 1 
> */
> interrupts = <17/* usbss */
>   18/* musb instance 0 
> */
>   19>;  /* musb instance 1 
> */
> multipoint = <1>;
> num-eps = <16>;
> ram-bits = <12>;
> port0-mode = <3>;
> port1-mode = <1>;
> power = <250>;
> ti,hwmods = "usb_otg_hs";
> status = "disabled";
> }; "
>
> am33x.dtsi (old) :
>
> "usb: usb@4740 {
> compatible = "ti,am33xx-usb";
> reg = <0x4740 0x1000>;
> ranges;
> #address-cells = <1>;
> #size-cells = <1>;
> ti,hwmods = "usb_otg_hs";
> status = "disabled";
>
> usb_ctrl_mod: control@44e10620 {
> compatible = "ti,am335x-usb-ctrl-module";
> reg = <0x44e10620 0x10
> 0x44e10648 0x4>;
> reg-names = "phy_ctrl", "wakeup";
> status = "disabled";
> };
>
> usb0_phy: usb-phy@47401300 {
> compatible = "ti,am335x-usb-phy";
> reg = <0x47401300 0x100>;
> reg-names = "phy";
> status = "disabled";
> ti,ctrl_mod = <_ctrl_mod>;
> };
>
> usb0: usb@47401000 {
> compatible = "ti,musb-am33xx";
> status = "disabled";
> reg = <0x47401400 0x400
> 0x47401000 0x200>;
> reg-names = "mc", "control";
>
> interrupts = <18>;
> interrupt-names = "mc";
> dr_mode = "host";
> mentor,multipoint = <1>;
> mentor,num-eps = <16>;
> mentor,ram-bits = <12>;
> mentor,power = <500>;
> phys = <_phy>;
>
> dmas = <  0 0   1 0
>   2 0   3 0
>   4 0   5 0
>   6 0   7 0
>   8 0   9 0
>  10 0  11 0
>  12 0  13 0
>  14 0   0 1
>   1 1   2 1
>   3 1   4 1
>   5 1   6 1
>   7 1   8 1
>   9 1  10 1
>  11 1  12 1
>  13 1  14 1>;
> dma-names =
> "rx1", "rx2", "rx3", "rx4", "rx5", "rx6", "rx7",
> "rx8", "rx9", "rx10", "rx11", "rx12", "rx13",
> "rx14", "rx15",
> "tx1", "tx2", "tx3", "tx4", "tx5", "tx6", "tx7",
> "tx8", "tx9", "tx10", "tx11", "tx12", "tx13",
> "tx14", "tx15";
> };
>
> usb1_phy: usb-phy@47401b00 {
> compatible = "ti,am335x-usb-phy";
> reg = <0x47401b00 0x100>;
> reg-names = "phy";
> status = "disabled";
> ti,ctrl_mod = <_ctrl_mod>;
> };
>
> usb1: usb@47401800 {
> compatible = "ti,musb-am33xx";
> status = "disabled";
> reg = <0x47401c00 0x400
> 0x47401800 0x200>;
> reg-names = "mc", "control";
> interrupts = <19>;
> 

Re: [beagleboard] EEPROM Serial Number for cape

2018-01-23 Thread Jason Kridner
You can use your own, but it is a general recommendation. Feel free to
adjust.

On Fri, Oct 20, 2017 at 9:04 AM Joe Vanderstelt 
wrote:

> The SRM states (in 8.2.4)  State the serial number should be WWYY&&&
> is that a requirement or can I use my own serial number?
>
> I am asking because I want to get my cape approved
> https://beagleboard.org/approved
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/aa8218a0-15cd-402a-ab68-ae15e7c7e91d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
https://beagleboard.org/about

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2BT6QP%3D_EhvV6xSfn0669a9WS3jT2LziPtiNCSTfQgAWFH%2BvKw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Minimum needed to run a Qt4 program

2018-01-23 Thread Hartley Sweeten
On Friday, January 19, 2018 at 11:06:11 AM UTC-7, Hartley Sweeten wrote:
>
> On Friday, January 19, 2018 at 10:36:14 AM UTC-7, RobertCNelson wrote:
>>
>>
>> So QT5 ( i know it's not QT4 ;) ) 
>>
>> Has a direcfb that is currently disabled: 
>>
>>   QPA backends: 
>> DirectFB . no 
>> EGLFS  yes 
>>   EGLFS i.MX6  no 
>>   EGLFS i.MX6 Wayland. no 
>>   EGLFS EGLDevice  yes 
>>   EGLFS GBM .. yes 
>>   EGLFS Mali . no 
>>   EGLFS Raspberry Pi . no 
>>   EGLFS X11 .. yes 
>>
>> It also has a tslib option: 
>>
>> tslib .. no 
>>
>>
>> https://buildd.debian.org/status/fetch.php?pkg=qtbase-opensource-src=armhf=5.7.1%2Bdfsg-3=1484191682=0
>>  
>>
>> we could try rebuilding 'qtbase-opensource-src' and see what happens.. 
>
>
>  Qt4 or Qt5 will work for me.
>
> I wasn't aware that Qt5 could work directly with the framebuffer. I 
> thought QWS was needed in order to run without X. According to the 
> following site, the QWS implementation was removed in Qt5:
>
> http://doc.qt.io/qt-5/embedded-linux.html
>
> Qt4 specifically states that it can work without X:
>
> http://doc.qt.io/archives/qt-4.8/qt-embedded-linux.html
>
> I'm willing to try either one it your willing to rebuild it :-)
>

Hi Robert,

Any luck rebuilding Qt5? I see in rcn-ee/repos you added qtbase-opensource-src 
(5.7.1+dfsg-3rcnee0~stretch+20180119) but installing qt5-default gets me 
version 5.7.1+dfsg-3+b1.

Just and FYI, trying a simple Qt app from the console with that version 
results in:

$ ./simple
QXcbConnection: Could not connect to display
Aborted

Running the program with sudo results in the same error.

Hartley

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a6359cd6-bfa1-4992-be15-2934199977e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Hardware watchdog for BBB

2018-01-23 Thread 'AVR' via BeagleBoard
Dear Harvey

Is it really means that absence of operating system on BBB eliminates 
shutdown problems from unpredictable power loss?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/089d1ade-982b-4b41-b64e-8b10351006b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: More pimux woes

2018-01-23 Thread Hugh Frater


On Monday, 22 January 2018 17:42:03 UTC, lgil...@tethers.com wrote:
>
> Thanks!!   Very helpful.  One issue with just using the config-pin utility 
> is that it doesn't always give you access to all the configurations 
> possible for a peripheral (not pin), for instance, setting a pin to eqep 
> (qep), there are actually several modes of eqep.   The dts file often 
> includes all these options.  
>
> That is a very valid point and something I hadn't considered. I was 
working around this by using my pru code to configure the required 
peripheral registers directly, which now I look at it seems a terrible way 
to do it when I could use the dts file... 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6f82ba09-c0de-4318-bc76-5e272dc0a8f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Beaglebone Green/Black Java for Linux ARM

2018-01-23 Thread Johan Henselmans
Robert, there is a new oracle jvm in town:


http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

http://download.oracle.com/otn-pub/java/jdk/8u162-b12/0da788060d494f5095bf8624735fa2f1/jdk-8u162-linux-arm32-vfp-hflt.tar.gz?AuthParam=1516697271_80e178dcd68ec5b82f12bd7c88eb3c25


On Wednesday, December 27, 2017 at 7:29:34 PM UTC+1, RobertCNelson wrote:
>
> On Wed, Dec 27, 2017 at 6:32 AM, Johan Henselmans 
>  wrote: 
> > Robert, do you still follow the Oracle java updates? 
>
> Not really.. only if people ask.. 
>
> > They have not been updated in a while. 
> > 
> > I am using these to run OpenHab on a Beaglebone, as the openjdk version 
> > seems to be a lot slower. 
> > 
> > Anyone else experiences with speed differences between openjdk and 
> oracle 
> > jdk? 
>
> Well i updated Java 8 for you: 
>
>
> https://github.com/rcn-ee/repos/commit/20dac792c418534741f5a515eba68674bfa37a35
>  
>
> Just "sudo apt update ; sudo apt upgrade" to get it.. 
>
> Otherwise it looks like Java 9 is now a no go for ARM: 
>
>
> http://www.oracle.com/technetwork/java/javase/downloads/jdk9-downloads-3848520.html
>  
>
> Regards, 
>
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2b11a1a7-36b3-479e-a847-14a04fef222c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.