Re: [beagleboard] Re: Help with PIR demo

Amazing already explained in previous post sounds like original poster has no knowledge that modern processor are powered at 3.3 volts or less and never bothered to read schematics. I applaud the willingness to walk through the examples  Sent from Yahoo Mail on Android On Sat, Dec 17,

Re: [beagleboard] Access EEPROM of BBB

consider it as a file at: /sys/bus/i2c/drivers/at24/1-0050/eeprom On Mon, Dec 12, 2016 at 3:27 PM, Ankita Thummar wrote: > New with BBB. I want to know how to access EEPROM (4KB) of BBB and read > and write a data structure into it. > Please suggest me some documents or

[beagleboard] Re: Help with PIR demo

Thanks for the replies, everybody. I am confused about the voltage requirements of the BBB...it accepts a 5V power supply (in the slot next to the ethernet cable input), and yet it is a 3.3V device? In addition, the demo prescribes that the PIR be powered by pin P9_5, which is a 5V supply. So

[beagleboard] PRU cycle counter overflow

HI All Is there a way to get an interrupt when there is PRU cycle counter overflow ? 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

Re: [beagleboard] Re: Possible to remove eeprom?

On Sat, 12/17/16, Charles Steinkuehler wrote: Subject: Re: [beagleboard] Re: Possible to remove eeprom? To: beagleboard@googlegroups.com Date: Saturday, December 17, 2016, 9:26 PM On 12/17/2016 12:12 PM, ferdster

Re: [beagleboard] Re: WiFi was working, is now missing

Heh. So the Adafruit part was working, but then this morning, it's decided to come up as wlan1 not wlan0 and is dead to WiFi again. I doubled up my entry in /etc/network/interfaces and it's back. I'll need to punch some holes in the lid of my enclosure so the 3-man IT staff it takes keep Linux

Re: [beagleboard] Re: Possible to remove eeprom?

On 12/17/2016 12:12 PM, ferdster wrote: > Hallo TJF, > > I think you are referring to the eMMC. I am talking about the small i2c > eeprom > that is used to identify the board. Like Robert Nelson said, you're going to have to hack on U-Boot to remove all the EEPROM calls. ...but unless you are

Re: [beagleboard] Fix the driver signage of the Windows 64bit package

On Dec 16, 2016 1:44 PM, "da66en" wrote: In particular, the RNDIS driver signage is no longer valid. It needs the SHA2 signature. I got it to work by signing it myself with my keys, not a good solution for most people. And Everytime we resign it, Microsoft breaks it by

[beagleboard] Re: Possible to remove eeprom?

Hallo TJF, I think you are referring to the eMMC. I am talking about the small i2c eeprom that is used to identify the board. Thanks. On Saturday, December 17, 2016 at 10:15:40 AM UTC-7, TJF wrote: > > Hi ferdster, > > don't deal with any softtware! > > Am Samstag, 17. Dezember 2016 01:29:35

[beagleboard] Re: Possible to remove eeprom?

Hi ferdster, don't deal with any softtware! Am Samstag, 17. Dezember 2016 01:29:35 UTC+1 schrieb ferdster: > > but we'd like to get rid of it. > Just override (dd) the boot sector on the eeprom. The bootloader cannot find it and checks the next device in the regular sequence. Regards -- For

[beagleboard] Re: v4.9.x-ti now open for testing...

Oh, this does remind me, I meant to ask, since I have *NOT* bisected the kernel before, any pointers on where to start looking for good info on effective bisection? I figured I would mark the 3.13 kernel as working (i had things working there), unless you know or have tried some kind of hid

[beagleboard] Re: v4.9.x-ti now open for testing...

Well, still no dice as far as usb_f_hid goes. I tried to change a few config items. I ended up, I think, with a better kernel build (less kruft), but nothing working. I guess its either bisect the kernel and see what broke (que mission impossible theme), or dig into the kernel further and see

Re: [beagleboard] Re: pru + 4.4 kernel?

Great news, keep going! Greg On Saturday, December 17, 2016 at 11:16:25 AM UTC-5, Jay Doobie wrote: > > Ahhh! Ok, I had modified things so much last night I went back to the > original and forgot to update the uio pruss in the non-overlay version. It > WORKS! > > When I was saying pinmux

Re: [beagleboard] Re: pru + 4.4 kernel?

Ahhh! Ok, I had modified things so much last night I went back to the original and forgot to update the uio pruss in the non-overlay version. It WORKS! When I was saying pinmux works, I guess I should have indicated that I was trying to set 990, 99c, 994 to 0x15. So it appears something in

Re: [beagleboard] Re: pru + 4.4 kernel?

Not totally clear what you are saying. I see you have the UIO PRUSS line uncommented in "PRU works". It is not uncommented in "pinmux works". So are you saying when you uncomment the UIO PRUSS line to activate it, it kills the pinmux? Sorry for the confusion! On Saturday, December 17, 2016 at

Re: [beagleboard] Re: pru + 4.4 kernel?

uEnv.txt: https://github.com/doobie42/OpenPegasus/blob/master/uEnv.txt Some progress that might shed light into issues? I have modified the dts files from the dts-rebuilder and in one I can access the PRU, and in the other I can get the pins set the way I want, but sadly not at the same time.

[beagleboard] Link to Official WIKI Page broken?

>From this page: http://beagleboard.org/latest-images The link to the "official wiki page": https://elinux.org/Beagleboard:Updating_The_Software seems to never connect for me. Anyone else see the same? Regards, Greg -- For more options, visit http://beagleboard.org/discuss --- You

Re: [beagleboard] Re: pru + 4.4 kernel?

Hi Jay, you are correct it is difficult to work through all the issues and find the right sources of information. I did attempt to document the current process for activating the PRU with Remoteproc: https://github.com/Greg-R/pruadc1 More specifically look in the PDF file:

Re: [beagleboard] Help with PIR demo

On Fri, Dec 16, 2016 at 10:33 PM, Chris Fink wrote: > At first the LED light turned on right away, and I got a constant succession > of "Motion Detected" messages. Then I realized that the code assumed an > active-LOW output from the PIR, but my PIR is active-HIGH,

Re: [beagleboard] Re: pru + 4.4 kernel?

I certainly expect I screwed something up. I've yet to see a website that really does a good job describing how to get the pru enaled or setting a main DT or overlay. I was going to try to grab the source for my old main DT and see if I am missing something. I have't been able to get either

[beagleboard] Re: v4.9.x-ti now open for testing...

> > I had another look at this. I don't think it is creating any interfaces > for some reason. I am unsure why not. If I check the configfs part of the filesystem, there doesn't seem to be anywhere where the "interface" values show up (things like bInterfaceProtocol or bInterfaceSubClass).

[beagleboard] Re: Windows 10 Bone_D64.exe Failing

Hi I am facing this issue. compatibility troubleshooting didn't work for me. Also I tried disabling signature check. -- 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