Re: [beagleboard] BBG cannot connect via ethernet

2016-11-11 Thread William Hermans
By the way, on a stock debian image on the beaglebones. DHCP will be enabled. So unless your laptop has a DHCP server running on it ( not very likely or easy to setup on Windows ). You're going to need a router between the laptop and a beaglebone. *IF* You want to use ethernet, and if you do not ha

Re: [beagleboard] BBG cannot connect via ethernet

2016-11-11 Thread William Hermans
So . . . # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr iface usb0 inet static address 192.168.7.2 netmask 255.255.255.252 network 192.168.7.0 gateway 192.168.7.1 This is what a stock system should be setup as for USB ethernet. So

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread William Hermans
On Fri, Nov 11, 2016 at 12:45 PM, Robert Nelson wrote: > >> univ-emmc is the userspace overlay we automatically load on bootup > >> > >> open /boot/uEnv.txt > >> > >> you'll notice a cape_universal=enable > >> > >> remove that and reboot > >> > >> Regards, > >> > > > > What does that actually do

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread William Hermans
Hi Zach, So, first of all. Yes removing the line , commenting it out in uEnv.txt will keep from loading the overlay at boot. As for removing it from the initramfs, I would assume if you reversed the process. e.g. remove the line from uEnv.txt. then remove the file from /lib/firmware, that the scri

[beagleboard] BBG cannot connect via ethernet

2016-11-11 Thread Petr Ĺ efara
Hello everybody. Just got my BBG and I'm not able to connect to the internal server via eth. PC is laptop with Win10, on BBG is power LED shining and USR LEDs are blinking. BBG is directly connect to laptom via eth cable. This laptom is older one (HP ProBook4530s) after complete reinstal. In

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Zach B
Great, thanks! And not to be a pest but I assume in order to undo that change I simply comment the line that I add to the uEnv.txt and that's it? Should I worry about removing the *.dtbo object from the initrd? On Friday, November 11, 2016 at 3:22:17 PM UTC-5, RobertCNelson wrote: > > On Fri, No

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Robert Nelson
On Fri, Nov 11, 2016 at 2:14 PM, Zach B wrote: > Thanks Robert! That solved the problem I have been having. The overlay > loaded and everything looks to be working. One follow up question I do have > is what is the proper way to load a custom overlay on startup? Is there a > way to enable multiple

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Zach B
Thanks Robert! That solved the problem I have been having. The overlay loaded and everything looks to be working. One follow up question I do have is what is the proper way to load a custom overlay on startup? Is there a way to enable multiple overlays as long as they don't try to use the same

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Robert Nelson
>> univ-emmc is the userspace overlay we automatically load on bootup >> >> open /boot/uEnv.txt >> >> you'll notice a cape_universal=enable >> >> remove that and reboot >> >> Regards, >> > > What does that actually do Robert ? I've done this myself in the past, and > haven't noticed a difference on

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread William Hermans
On Fri, Nov 11, 2016 at 12:26 PM, Robert Nelson wrote: > On Fri, Nov 11, 2016 at 12:53 PM, Zach B wrote: > > wow that is incredible useful, I didn't even realize that is what dmesg > did. > > Here is the output I got: > > [ 2117.571792] bone_capemgr bone_capemgr: part_number 'PRU-GPIO-BLINK', >

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Robert Nelson
On Fri, Nov 11, 2016 at 12:53 PM, Zach B wrote: > wow that is incredible useful, I didn't even realize that is what dmesg did. > Here is the output I got: > [ 2117.571792] bone_capemgr bone_capemgr: part_number 'PRU-GPIO-BLINK', > version 'N/A' > [ 2117.571876] bone_capemgr bone_capemgr: slot #10:

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Zach B
I just tried the various combinations of enabling and disabling the HDMI, emmc, both and neither and regardless of what it is set to I get a conflict on P8.11 every time. Is there a key component that I am missing somewhere or a different way I should be going about this? On Friday, November 11

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Zach B
wow that is incredible useful, I didn't even realize that is what dmesg did. Here is the output I got: [ 2117.571792] bone_capemgr bone_capemgr: part_number 'PRU-GPIO-BLINK', version 'N/A' [ 2117.571876] bone_capemgr bone_capemgr: slot #10: override [ 2117.571920] bone_capemgr bone_capemgr: Using

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Robert Nelson
On Fri, Nov 11, 2016 at 12:42 PM, Zach B wrote: > I wanted to add on to this that when I switch the Device Tree Blob file > extension to ".dtbo" instead of ".dtb" I get the error: > -bash: echo: write error: File exists > instead of the file not found error I was getting previously. if you type "

[beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Zach B
I wanted to add on to this that when I switch the Device Tree Blob file extension to ".dtbo" instead of ".dtb" I get the error: -bash: echo: write error: File exists instead of the file not found error I was getting previously. On Friday, November 11, 2016 at 1:27:22 PM UTC-5, Zach B wrote: > >

[beagleboard] Re: Beaglebone Black PRU Troubles

2016-11-11 Thread Zach B
Hi everyone, So I messed around with my beaglebone a little bit last night. I worked out the issues in my device tree source file so it is now compiled but I can't seem to get anything to echo properly to "slots" I compile my ".dtb" file but when I go to call the comman: echo PRU-GPIO-BLINK > /

[beagleboard] Re: Removal of Components from BBBW for Custom PCB.

2016-11-11 Thread Stephane Charette
> > I'm making a custom BBBW for a school project. I'm adding a few > peripherals but would like to strip down what is unnecessary in order to > save on BOM costs. The first to go is the large HDMI chip. > HDMI and the barrel connector was already removed from BBG and BBGW. Out of curiosity,

Re: [beagleboard] Do I really need a USB-to-FTDI cable to see the U-boot prompt? Will it not work on micro-HDMI?

2016-11-11 Thread Stephane Charette
On Thursday, November 10, 2016 at 12:36:07 PM UTC-8, William Hermans wrote: > > You do not have to buy a FTDI cable. It could be any decent cable, that > does not necessarily cost as much as FTDI. For example my buddy and I > ordered a couple of PL2303HX cables off ebay for like $5-6 usd shipped.

[beagleboard] Re: Flashing a BBB's EMC from uSD Card - problems

2016-11-11 Thread 'Ian Watts' via BeagleBoard
Update: I 'located' the uSD card - in the //dev (devices, I guess) folder; I simply by noted what changed as I inserted the uSD card and looking at the folder contents before ('ls dev' command) and after) In my case (pretty standard, I guess) I saw 'mmcblk1p1' was added as I inserted the card (

[beagleboard] Re: debian: release candidate: 2014-12-11

2016-11-11 Thread Mrudula Chougule
Hi, I am using repository and steps for building the same mentioned in below link; https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-HDMI 1) I have flashed U-boot Image to internal Flash of Beagle Bone Black. When I try to boot-up from internal flash without having kernel i

[beagleboard] Beagle Bone Black - uboot

2016-11-11 Thread Mrudula Chougule
Hi, I am working on Beagle Bone Black AM335x platform and started porting U-boot for the same. I have followed steps for building U-boot, Kernel and rootfs on below mentioned link, https://eewiki.net/display/linuxonarm/BeagleBone+Black I am able to compile it successfully but when I try to l

[beagleboard] Not able to ping the router or google from my beagleboard-xm running ubuntu

2016-11-11 Thread anuj . gupta
Hi i am working on beagleboard-xm running ubuntu , when i connected my ethernet cable then i am not able to ping anything it shows network unreachable. I changed the /etc/network/interfaces and added the static ip details even the problem was not resolved Thanks -- This message contains co

[beagleboard] Re: Flashing a BBB's EMC from uSD Card - problems

2016-11-11 Thread 'Ian Watts' via BeagleBoard
Hi Dennis, Thanks for your response (don't know what happened the first time - I responded to you just before I did to Stephane... wierd - too late in the day I guess ! ) Firstly I thanked you. Then I confirmed my BBB is a Rev C / 4GB. Then I wrote about a new (but associated) issue I have and