On Mon, Jan 25, 2016 at 6:57 PM, Dean <dean.b...@gmail.com> wrote:
> apt-get install build-essential
>
>
> In 3.8.x spidev2.0 could be used on spi1, but with 4.1.x+ the "first"
> is spidev1 (even if spi1 over spi0..) >
>
>
> SPIDevice *busDevice = new SPIDevice(2,0); //Using second SPI bus (both
> loaded)
>
> The code is trying to open /dev/spidev2.0, but it's not there
>
>
> This should be your first worry-> open("/dev/spidev2.0", O_RDWR) = -1 ENOENT
> (No such file or directory)
>
> Find out why your system thinks this file does not exist. As in perhaps it
> doesn't because you need to load a device tree file as mike mentioned above.
> But also as stated above, there can be many reasons why your application
> does not think this file exists.
>
> So did you tell the BBB to load the spidev interface???
>
> PS.. "4.1.12-ti-r29" was way before i fixed spi/dma..  So you really
> should upgrade: (unless you only plan to send 159 bytes over spi)
>
> cd /opt/scripts/tools/
> git pull
> sudo ./update_kernel.sh --ti-rt-channel --lts-4_1
> cd ~/
>
> git clone https://github.com/ --depth=1
> cd ./bb.org-overlays
> ./dtc-overlay.sh
> ./install.sh
>
> Then:
>
> sudo sh -c "echo 'cape_enable=bone_capemgr.
>>> /boot/uEnv.txt"
>
> Here is an update of the steps performed ...
>
> 1) I did an update on apt-get install build-essential
>
> 2) Change code from ... SPIDevice *busDevice = new SPIDevice(2,0)
>
> to SPIDevice *busDevice = new SPIDevice(1,0)
>
> 3) Updated kernel and ./dtc overlay
>
> OUTCOME: The SPIDEV2.0 problem went away – unfortunately shortly thereafter
> my BBB would no longer connect with ssh root@192.168.7.2. I therefore
> reloaded back to what I started with originally as below.
>
> Linux beaglebone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015
> armv7l GNU/Linux
>
> Linux version 4.1.12-ti-r29 (root@a5-imx6q-wandboard-2gb) (gcc version 4.9.2
> (Debian 4.9.2-10) ) #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015

Just to state this again:

"PS.. "4.1.12-ti-r29" was way before i "fixed" spi/dma..  So you
really should upgrade: (unless you only plan to send 159 bytes over
spi)"

at the "160th" byte it locks up hard.. till you reboot..

Upgrade to:

sudo update
sudo apt-get install linux-image-4.1.15-ti-r43
sudo reboot

or

sudo update
sudo apt-get install linux-image-4.1.15-ti-rt-r43
sudo reboot

No sense using 4.1.12-ti-r29 and "trying" to get spi to work, as we
know it DOESN'T work ;)

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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to