[beagleboard] Re: Signed BBB drivers for Windows 10

I disabled driver signature requirement and the driver install worked after that. Search for "disable signature requirement for drivers windows 10". If I remember correctly you restart while holding shift, (press shift then click on restart). Then after restart navigate to screen with 10-15

[beagleboard] Re: Same Ole Game, Different Take/Seth

Hello, I am using a couple different books. I am using the Programming the BeagleBone Black from Monk and another book called Evil Genius by Rush. It is a similar book on the BBB. I had some odd connections at first. You are right. I guess I am learning what I am doing. Seth P.S. I lost

Re: [beagleboard] Re: spi / shiftout.js in 2017-03-19 image

On Tue, Jul 11, 2017 at 8:17 PM, William Hermans wrote: > SPI is notoriously finicky when it comes to high speed, and noise. Since > I'm not an EE, I could not say much more than that. Typically though, from > what I understand, traces can not be very long. > Additionally,

Re: [beagleboard] Re: spi / shiftout.js in 2017-03-19 image

SPI is notoriously finicky when it comes to high speed, and noise. Since I'm not an EE, I could not say much more than that. Typically though, from what I understand, traces can not be very long. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you

Re: [beagleboard] Re: Windows 10 Bone_D64.exe Failing

Well, this is like a 2 year old post . . . Let me just say this. I'm running Windows 10 pro on a Lenovo Thinkpad, and I happened to have a BBG plugged into a USB 3.0 port off this laptop for power( using ethernet for networking ), and Windows update automatically installed the NDIS driver for it

[beagleboard] Re: spi / shiftout.js in 2017-03-19 image

On Friday, July 7, 2017 at 1:53:10 PM UTC-7, Jeff Albrecht wrote: [...] > Are there any other changes that I may have missed? Suggestions? > Regarding the SPI test in Exploring BeagleBone Black. Got it, works on my machine now! Thank you William and Gaurav for your input. It turned out that

[beagleboard] Re: Windows 10 Bone_D64.exe Failing

I had the same issue, I disabled signature requirement for drivers. On Wednesday, August 12, 2015 at 11:13:13 PM UTC-4, mscleavite wrote: > > I have just upgraded to Windows 10 on a machine that I have not previously > connected my BBB to. I had success on other windows 8 machines as well as >

Re: [beagleboard] Re: Same Ole Game, Different Take/Seth

Hello Sir, Supposedly, the GNDA_ADC pin on the BBGW makes less noise. This noise would create a higher fluctuation of distance from the actual temp. in the environment. Seth P.S. Now, the GND to VDD_3V3 had some idea behind it but was not listed in the book. I had to put value at 63 degrees

Re: [beagleboard] Re: Same Ole Game, Different Take/Seth

Hello, So, TMP36: + Vs is now at VDD_3V3 GND is now at DGND I did configure the old software to work but this is easier. Seth On Tuesday, July 11, 2017 at 7:40:51 PM UTC-5, RobertCNelson wrote: > > On Tue, Jul 11, 2017 at 7:23 PM, Mala Dies > wrote: > > Hello Again

Re: [beagleboard] Re: Same Ole Game, Different Take/Seth

Hello, The instructions on the book said to connect the pins of the TMP36 via jumper wires to the BBB/BBGW in that manner. I am using a BBGW instead of the BBB or BBBW for this project. Seth P.S. Should I have the jumper wires connecting to different pins on the BBGW? On Tuesday, July 11,

Re: [beagleboard] Re: Same Ole Game, Different Take/Seth

Hello Again, I read the schematic on the book. The book states via photo to wire things up this way. Seth On Tuesday, July 11, 2017 at 8:03:05 PM UTC-5, Mala Dies wrote: > > Hello, > > The instructions on the book said to connect the pins of the TMP36 via > jumper wires to the BBB/BBGW in

Re: [beagleboard] Re: Same Ole Game, Different Take/Seth

On Tue, Jul 11, 2017 at 7:23 PM, Mala Dies wrote: > Hello Again Mr. Dennis, > > Seth here. I have done some small time work on what wiring I have concocted. > Here goes: > > TMP36: > > Pin 1 is + Vs and it is connected to P9_34 or GNDA_ADC. > > Pin 2 is Vout and it is connected

[beagleboard] Re: Same Ole Game, Different Take/Seth

Hello Again Mr. Dennis, Seth here. I have done some small time work on what wiring I have concocted. Here goes: TMP36: Pin 1 is + Vs and it is connected to P9_34 or GNDA_ADC. Pin 2 is Vout and it is connected to P9_40 or AIN1. and... Pin 3 is GND and it is connected to P9_03 or VDD_3V3.

[beagleboard] Re: Same Ole Game, Different Take/Seth

Hello Dennis, Yep...I changed the wiring and changed a uEnv.txt file in the /boot directory. I have the P9_40/AIN1 pin connect now instead of the P9_39/AIN0. When I stated that I changed a file, I changed the file to enable BB-ADC1,BB-ADC2 instead of having it enabled at BB-AIN0, BB-AIN1.

RE: [beagleboard] where is capemgr?

Robert, Thanks. I have spent a good bit of time with the robotics cape through working with James Strawson. He has constructed a very good set of aps and library for newbies to use. Those are his main constituents, IMHO. I have been using his board without his code base with his help. He and I

[beagleboard] FrSky Receivers

Has anyone had any luck connecting non DSM2 / DSMX up to the Beagle Bone Blue? I have FrSky Taranis X9D Plus ACCST Radio and D4R-ii Receiver (http://www.getfpv.com/frsky-d4r-ii-4ch-2-4ghz-accst-receiver-w-telemetry.html) lying around. I was wondering if they would be compatible with the

Re: [beagleboard] where is capemgr?

On Tue, Jul 11, 2017 at 2:49 PM, Clark Briggs wrote: > Robert, > Thanks. > I have spent a good bit of time with the robotics cape through working with > James Strawson. He has constructed a very good set of aps and library for > newbies to use. Those are his main

Re: [beagleboard] where is capemgr?

On Tue, Jul 11, 2017 at 2:28 PM, wrote: > After watching the great progress, I started in. I have the 3/19/2017 latest > image with apt-get upgrades running on a Rev C BBB with a Rev C Robotics > Cape. All in all, the process worked well. But I can't find capemgr. I

[beagleboard] where is capemgr?

After watching the great progress, I started in. I have the 3/19/2017 latest image with apt-get upgrades running on a Rev C BBB with a Rev C Robotics Cape. All in all, the process worked well. But I can't find capemgr. I went looking for it because I want to access analog I/O and other stuff.

Re: [beagleboard] Remoteproc not loading firmware

I don't get it... What I did now is: git pull in dtb-rebuilder; then make all_arm and make install_arm - everything successfull; then sudo reboot; Now whenever I boot the board or I do sudo modprobe pru_rproc - nothing happens, there is even no message saying that prus were probed

Re: [beagleboard] Remoteproc not loading firmware

On Tue, Jul 11, 2017 at 1:36 PM, Igor Jędrzejczak wrote: > I also now noticed that there is a message from remoteproc about loading > some elf fw file... Here is my whole dmesg, maybe there is some misconfig > there... > > https://pastebin.com/1HGLkRi2 The elf file is for the

Re: [beagleboard] Remoteproc not loading firmware

I also now noticed that there is a message from remoteproc about loading some elf fw file... Here is my whole dmesg, maybe there is some misconfig there... https://pastebin.com/1HGLkRi2 Thanks for a quick reply Regards On Tuesday, 11 July 2017 20:19:45 UTC+2, Igor Jędrzejczak wrote: > >

Re: [beagleboard] Remoteproc not loading firmware

@Robert - tried it, didn't help... On Tuesday, 11 July 2017 18:15:31 UTC+2, RobertCNelson wrote: > > On Tue, Jul 11, 2017 at 10:57 AM, Igor Jędrzejczak > wrote: > > > > Hello! > > > > I'm facing an issue with Beaglebone Black PRU. I have successfully > compiled > > a C

Re: [beagleboard] uboot, saveenv and what works

Thanks Robert ! Looks like someone using yocto for BBB also had a similar question a couple years ago, https://lists.yoctoproject.org/pipermail/yocto/2015-April/024636.html... On Tuesday, July 11, 2017 at 11:59:37 AM UTC-5, RobertCNelson wrote: > > On Sun, Jul 9, 2017 at 10:53 AM, marty

Re: [beagleboard] uboot, saveenv and what works

On Sun, Jul 9, 2017 at 10:53 AM, marty leisner wrote: > Different postings seem to indicate different things. > > I've been using u-boot for over a decade and I'm used to the saveenv/fw_* > tools. > > Seems the default beagles don't support this. I have a older 2G eMMC and

[beagleboard] Re: uboot, saveenv and what works

I THINK I have the same/similar question. Given the BeagleBone/BeagleBoard's single ext4 partition strategy for containing the FS and kernel and where u-boot/MLO is copied into the the "hole" below the partition table using the dd command, where is the default and user-updated u-boot

Re: [beagleboard] Remoteproc not loading firmware

On Tue, Jul 11, 2017 at 10:57 AM, Igor Jędrzejczak wrote: > > Hello! > > I'm facing an issue with Beaglebone Black PRU. I have successfully compiled > a C program for PRU0 and copied it to /lib/firmware with name > am335x-pru0-fw. But when I type sudo rmmod pru_rproc and then

[beagleboard] Re: Max14830, uart over spi, device tree overlay/kernel driver

We just received a Maxim 3107 evaluation board and WERE planning on interfacing it to the BeagleBoard-X15 to try to bring up extra UART ports over SPI/I2C on the BBX15, but then we found the room for a USB hub in place of the Maxim chips on our custom board. Nonetheless, if there's anything

[beagleboard] Remoteproc not loading firmware

Hello! I'm facing an issue with Beaglebone Black PRU. I have successfully compiled a C program for PRU0 and copied it to /lib/firmware with name am335x-pru0-fw. But when I type sudo rmmod pru_rproc and then sudo modprobe pru_rproc I see only that both PRUs have been probed successfully, but

[beagleboard] How to convert multiple raw images to qcow2?

I have created 1 VM in qemu using 2 raw images, which has 2 partitions as given below. /dev/sda1 910G 263G 601G 31% / /dev/sdb 5G 1G 4G 20% /mnt Then I am stopping the VM and converting both raw images to qcow2 format. Using these qcow2 images I am trying to launch a new

[beagleboard] Re: Right way to configure ID EEPROM on new cape?

In addition to Robert's response, here is a second (though somewhat outdated) page and associated links that show how to write to eeprom of a custom cape. https://github.com/jbdatko/eeprom_tutorial/blob/master/eeprom.md Note: some of the information on this page is old stuff, for example the

[beagleboard] Re: Max14830, uart over spi, device tree overlay/kernel driver

Hi, Did you got this working ? If so please can you post the solution. On Wednesday, 20 July 2016 18:43:34 UTC+5:30, Laurits Telle Riple wrote: > > I am trying to get MAX14830 > > > to work with

[beagleboard] Re: GPIO configuartion in Device Tree Overlay and how to set a default value for an output pin

Well I did a little workaround and made a script that will init the GPIO via sysfs in the way I want at system start. But I don´t need to set the pinmux via the overlay for that as far as i know. echo "61" > /sys/class/gpio/export #set gpio61 P8_26 echo "out" >