Re: [beagleboard] Trouble using SPI interfaces on new BBBW

On Wed, May 17, 2017 at 9:42 AM, Garth Webb wrote: > Hi, after I setup Wireless on my BBBW, I tried using the SPI interface using > this simple Python code: > > #import the library > from Adafruit_BBIO.SPI import SPI > > > spi = SPI(0,0) > spi.writebytes(5) > > When executed

Re: [beagleboard] Flash BBB eMMC with non-debian image

On Wed, May 17, 2017 at 1:57 PM, JDW wrote: > I have just one question. Has anyone flashed the eMMC on the BBB with any > other non-debian image, if so how did you do it? > > I have a non-debian image (QNX) which loads an OS that works just fine if I > boot from the SD

Re: [beagleboard] How to flash Debian 7.5 (2014-05-14) to eMMC?

On Wed, May 17, 2017 at 2:03 PM, Jeffrey Milloy wrote: > > I'm trying to write Debian 7.5 (2014-05-14) onto a BeagleBoneBlack > Industrial from Element14, but following the instructions at > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC didn't >

[beagleboard] Trouble using SPI interfaces on new BBBW

Hi, after I setup Wireless on my BBBW, I tried using the SPI interface using this simple Python code: #import the library from Adafruit_BBIO.SPI import SPI spi = SPI(0,0) spi.writebytes(5) 1. When executed using sudo it runs without error. However, using a logic

[beagleboard] How to flash Debian 7.5 (2014-05-14) to eMMC?

I'm trying to write Debian 7.5 (2014-05-14) onto a BeagleBoneBlack Industrial from Element14, but following the instructions at http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC didn't work. It doesn't flash the image at reboot (at least, there is no LED flashing pattern).

Re: [beagleboard] Re: Surefire PRU - Setup.

On 05/16/17 19:21, Greg Ercolano wrote: > On 05/16/17 17:36, Greg Ercolano wrote: >> root@beaglebone:~/dtb-rebuilder# make >> DTC src/arm/am437x-gp-evm.dtb >> FATAL ERROR: Unrecognized check name "unit_address_vs_reg" <-- >> Makefile:136: recipe for target

[beagleboard] Flash BBB eMMC with non-debian image

I have just one question. Has anyone flashed the eMMC on the BBB with any other non-debian image, if so how did you do it? I have a non-debian image (QNX) which loads an OS that works just fine if I boot from the SD card. I am trying to figure out how I can get that image onto the eMMC so

[beagleboard] See if I understand setting up a device tree for the PRU

I am trying to determine how to use the PRU to control the DC motors on a BB Blue. I plan to use these 4 H-bridges to control two stepper motors. The PRU will generate the proper sequence of outputs to move the stepper at the proper speed, direction, and amount of rotation. After examining the

Re: [beagleboard] Weird behaviour: input/output error and no commands after few minutes

On Wed, May 17, 2017 at 2:12 PM, Niels Jakob Buch wrote: > That makes sense, will try that. > > But are there no log-file where this kernel output is stored? > Well it could be, but I do not think Robert persists logs between reboots. Maybe I'm wrong. So then assuming if what

Re: [beagleboard] Weird behaviour: input/output error and no commands after few minutes

That makes sense, will try that. But are there no log-file where this kernel output is stored? On Wednesday, 17 May 2017 22:48:24 UTC+2, William Hermans wrote: > > Get, and connect a serial debug cable. Connect to your support PC, use > puTTY or another serial client software to view the kernel

Re: [beagleboard] Weird behaviour: input/output error and no commands after few minutes

Get, and connect a serial debug cable. Connect to your support PC, use puTTY or another serial client software to view the kernel output as it's running, and what errors are being displayed, when this happens. On Wed, May 17, 2017 at 1:25 PM, Niels Jakob Buch wrote: > > Hi

Re: [beagleboard] Re: Surefire PRU - Setup.

On Tue, May 16, 2017 at 7:41 PM, wrote: > I've been a C and assembly programmer since the 80's, but all of this with > dtc is still pure greek to me. > I'm assuming the original intent was to install the latest git version of > the dtc compiler, though I'm not sure what

[beagleboard] Weird behaviour: input/output error and no commands after few minutes

Hi there, new to Beaglebone Blue but not happy so far. Using newest image bone-debian-8.7-iot-armhf-2017-03-19-4gb Flashing to MMC, working fine. Configuring wifi to my local AP in /etc/network/interfaces Running apt-get update, apt-get upgrade without problems. Rebooting from that, all is ok,

[beagleboard] Re: image vmlinuz-4.9.25-ti-r32 may break networking

On Sunday, May 14, 2017 at 4:38:59 PM UTC-5, Mark Copper wrote: > > On Thursday, May 11, 2017 at 6:28:42 PM UTC-5, Mark Copper wrote: >> >> Could be broken hardware as well. OTOH BBBW did work out of the box but >> networking failed after kernel update while everything else seems OK. >> >>

Re: [beagleboard] Re: Surefire PRU - Setup.

On Tue, May 16, 2017 at 9:41 PM, wrote: > On Tuesday, May 16, 2017 at 7:11:33 PM UTC-7, RobertCNelson wrote: >> >> On Tue, May 16, 2017 at 7:36 PM, Greg Ercolano wrote: >> > root@beaglebone:~/dtb-rebuilder# make >> > DTC src/arm/am437x-gp-evm.dtb

Re: [beagleboard] rc_ files

On Wed, May 17, 2017 at 12:04 AM, wrote: > ya..everything what you said are happenening. > But the new image is not written into the board. > After the cyclon led stops, the default storage of 39.5MB partition is > opening. is that mean new image written into the

Re: [beagleboard] rc_ files

Try this https://github.com/beagleboard/beaglebone-blue/wiki/Flashing-firmware On 2017-05-17 01:04 AM, sreedivya1...@gmail.com wrote: ya..everything what you said are happenening. But the new image is not written into the board. After the cyclon led stops, the default storage of 39.5MB

[beagleboard] Advise Sought - Configuring Linux to work with only 16 data bits connected to DDR3 on am57xx.

Hi, Our initial board with the 5718 has a single Kingston 256MBx16 DDR3 chip with only 16 data bits connected to the first EMIF. The 572xEVM/BeagleBoard appears to utilize all 32 data bits, the lower 16 of which are connected to the first Kingston DDR3 part in the "pair" while the upper 16

Re: [beagleboard] Re: Surefire PRU - Setup.

On 2017-05-17 04:21, Greg Ercolano wrote: On 05/16/17 17:36, Greg Ercolano wrote: root@beaglebone:~/dtb-rebuilder# make DTC src/arm/am437x-gp-evm.dtb FATAL ERROR: Unrecognized check name "unit_address_vs_reg" <-- Makefile:136: recipe for target 'src/arm/am437x-gp-evm.dtb'

Re: [beagleboard] beaglebone black with 1G ethernet

LK"I Thanks, I'm about to use Marvell Ethernet switch 88E6341 , I've seen the driver exits under driivers folder: https://github.com/beagleboard/linux/commits/4.4/drivers/net/dsa/mv88e6xxx.c How will the linux "knows" to use this driver?? (p.s. since the ethernet swith is unmanaged, it should be

[beagleboard] Marvell 88E6XXX

LK"I Hi , I'm using BBB , and want to replace the PHY with Marvell 88E6341 . I've found the driver exists on the driver folder on the BBB linux source code. But what should I change with the device tree in order to replace the 10/100 default PHY with that chip? Thanks, Harel -- For more

Re: [beagleboard] rc_ files

ya..everything what you said are happenening. But the new image is not written into the board. After the cyclon led stops, the default storage of 39.5MB partition is opening. is that mean new image written into the board? On Tuesday, May 16, 2017 at 7:22:41 PM UTC+5:30, RobertCNelson wrote:

Re: [beagleboard] Re: Surefire PRU - Setup.

On 05/16/17 17:36, Greg Ercolano wrote: > root@beaglebone:~/dtb-rebuilder# make > DTC src/arm/am437x-gp-evm.dtb > FATAL ERROR: Unrecognized check name "unit_address_vs_reg" <-- > Makefile:136: recipe for target 'src/arm/am437x-gp-evm.dtb' failed <-- > make[1]: ***

Re: [beagleboard] Re: Surefire PRU - Setup.

On Tuesday, May 16, 2017 at 7:11:33 PM UTC-7, RobertCNelson wrote: > > On Tue, May 16, 2017 at 7:36 PM, Greg Ercolano > wrote: > > root@beaglebone:~/dtb-rebuilder# make > > DTC src/arm/am437x-gp-evm.dtb > > FATAL ERROR: Unrecognized check name "unit_address_vs_reg"

Re: [beagleboard] Re: Flashing eMMC memory from SD card with Chipsee Debian Jessie

Thanks for your answer. I actually have only "TTL-232R-5V" cable. I assume, I need cable with 3.3V connectors because of preventing of BBB damage. So I've just ordered one (FTDI TTL-232R-3.3V). Dňa utorok, 16. mája 2017 15:55:06 UTC+2 RobertCNelson napísal(-a): > > On Tue, May 16, 2017 at 8:50