Re: [beagleboard] can't set up remoteproc on kerlnel 4.14

Hi Robert, root@beagle23:~# date Fri Jul 19 10:14:47 CEST 2019 I have checked my clock on my board, everything seems ok, see above. I don't understand why I have this certificate error? Any help how to solve it? Le mercredi 17 juillet 2019 17:58:18 UTC+2, RobertCNelson a écrit : > > On Wed,

Re: [beagleboard] can't set up remoteproc on kerlnel 4.14

Hi Robert, I have checked my clock on my board, everything seems ok Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Thu Jul 18 17:30:24 2019 from 172.23.16.22 root@beagle23:~# date Fri Jul 19 10:14:47 CEST 2019 I don't understand why I

[beagleboard] can't set up remoteproc on kerlnel 4.14

Dear, I would like to setup pru via remoteproc but I couldn't see the driver loaded even after loading device tree AM335X-PRU-RPROC-4-14-TI-PRUCAPE-00A0.dtbo. vesrion.sh gives: Saisissez le codegit:/opt/scripts/:[1cfc1dcc9918af109e337d8e50173e4e772afa52 ] eeprom:[A335BNLT00C00816BBBK13DF]

[beagleboard] Re: NI VISA for BeagleBone Green

Hi Robert, your link is talking about LINX SW, I couldn't find any topic about NI-VISA. what was your advise point to this link? I just want to install NI-VISA

Re: [beagleboard] NI VISA for BeagleBone Green

Hi Shant, can you tell me how did you install the NI-VISA-5.4.1 package, is there anty git repository to clone this driver? I will much appreciate your help. Regards, Le mercredi 16 décembre 2015 15:39:33 UTC+1, shant...@gmail.com a écrit : > > Aaah, the first one did the trick!! thank

[beagleboard] u-boot v2017.03 cross compilation failed

Hi, I have tried to compile the u-boot as described from Robert Nelson eewiki but I have ended up with the following compilation error after executing the following steps: make ARCH=arm CROSS_COMPILE=${CC} distclean make ARCH=arm CROSS_COMPILE=${CC} omap3_beagle_defconfig make ARCH=arm

Re: [beagleboard] issue booting from eMMC aftre downgrading from kernel 4.9.6-bone4 to 4.1.21-bone-rt-r20

uuid=dbc9a966-34f4-4e4b-bf18-9de885ebd3ae Le mardi 7 février 2017 14:17:24 UTC+1, malkowki a écrit : > > Hi Robert, > > I have booted my board with the latest debian image 4.4.30-ti-r64 and > mounted the emmc. > Please find attached how the uEnv.txt was set : > > > Le

Re: [beagleboard] issue booting from eMMC aftre downgrading from kernel 4.9.6-bone4 to 4.1.21-bone-rt-r20

Hi Robert, I have booted my board with the latest debian image 4.4.30-ti-r64 and mounted the emmc. Please find attached how the uEnv.txt was set : Le lundi 6 février 2017 15:51:49 UTC+1, RobertCNelson a écrit : > > On Mon, Feb 6, 2017 at 8:19 AM, malkowki <bmb.tec...@gmail.com

[beagleboard] issue booting from eMMC aftre downgrading from kernel 4.9.6-bone4 to 4.1.21-bone-rt-r20

Hi fellows, I am having issue booting from eMMC after downgrading from Kernel 4.9.6-bone4 to 4.1.21-bone-rt-r20. I am using a beaglebone black REV C with Debian 8 distibution, I had trouble communicating via USB LAN under address 192.168.7.2 then I decided to downgrade to older version that I

Re: [beagleboard] connecting to 192.168.7.2 failing after updating to kernel 4.1.36-bone-rt-r24

Hi Robert, after having compile the image 4.9.6-bone4 I still cannot ssh to 192.168.1.1 so I have tried to switch back to 4.1.21-bone-rt-r20 by modifying the uEnv.txt and reboot then I get: Checking if uname_r is set in /boot/uEnv.txt... gpio: pin 56 (gpio 56) value is 1 Running uname_boot

[beagleboard] Re: connecting to 192.168.7.2 failing after updating to kernel 4.1.36-bone-rt-r24

Le mercredi 21 décembre 2016 19:05:57 UTC+1, malkowki a écrit : > > Dear, > > after updating my beaglebone REVC board from kernel 4.1.21-bone-rt-r20 to > 4.1.36-bone-rt-r24 using Robert Nelson script , I am having issue > connecting from ssh Putty Host Window7 PC to

[beagleboard] connecting to 192.168.7.2 failing after updating to kernel 4.1.36-bone-rt-r24

Dear, after updating my beaglebone REVC board from kernel 4.1.21-bone-rt-r20 to 4.1.36-bone-rt-r24 using Robert Nelson script , I am having issue connecting from ssh Putty Host Window7 PC to the board via USB to 192.168.7.2. Before the update it was working perfectly now it looks like the

Re: [beagleboard] Re: BUS ERROR modprobe uio_pruss extram_pool_sz=0x800000

k-wl1835mod.dtb > #dtb=am335x-bonegreen-overlay.dtb > > > On Tue, Dec 13, 2016 at 6:45 AM, malkowki <bmb.tec...@gmail.com > > wrote: > >> Hello William, >> >> I don't see where I can make some changes in my original DTS file in >> order to extemd the

Re: [beagleboard] Re: BUS ERROR modprobe uio_pruss extram_pool_sz=0x800000

#size-cells = <0>; }; }; }; }; Le lundi 12 décembre 2016 20:05:05 UTC+1, William Hermans a écrit : > > I suspect that you need to make these changes in the overlay file you use > to initially configure the PRU's. > > On Mon, Dec 12,

[beagleboard] BUS ERROR modprobe uio_pruss extram_pool_sz=0x800000

Hi, I am running 4.1.21-bone-rt-r20, Debian GNU/Linux 8.6 (jessie). I run a PRU program with default DRAM size of 256KB , this works fines but when I tried to increase the external memory to 8MB I got a buss error #modprobe -r uio_pruss #modprobe uio_pruss extram_pool_sz=0x80 #dmesg |

[beagleboard] No DHCPDISCOVER

Hi, My old board Beagleboard xM running Debian 7.3 Kernel Version 3.9.11-x5 has having troubles getting any IP dynamic adress from the DHCP server. Below the log message: [] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.2.2 Copyright 2004-2011 Internet Systems

[beagleboard] Re: segmentation fault while running python code with Adafruit_BBIO

Hi Drew, thanks for this update. Regards, Beninio, Le mercredi 30 novembre 2016 10:55:10 UTC+1, Drew Fustini a écrit : > > On Tuesday, November 29, 2016 at 8:50:07 AM UTC-6, malkowki wrote: > > I have installed PyBBIO as well, and this one is failing when testing > the package

[beagleboard] Re: segmentation fault while running python code with Adafruit_BBIO

Thanks Dennis for your quick reply. Le mardi 29 novembre 2016 14:00:42 UTC+1, Dennis Lee Bieber a écrit : > > On Tue, 29 Nov 2016 01:56:36 -0800 (PST), malkowki > <bmb.tec...@gmail.com > declaimed the > following: > > >Dear, > > > >I am using bea

[beagleboard] segmentation fault while running python code with Adafruit_BBIO

Dear, I am using beaglebone black revision C running kernel 4.1.21-bone-rt-r20 ,re4lease Debian Jessie. I have installed the Adafruit BBIO and check that the installation was successfull by doing the follwing >>> import Adafruit_BBIO.GPIO as GPIO; print GPIO >>> whne I try to run a python

[beagleboard] writing to [/dev/mmcblk1] failed using bbb-eMMC-flasher-eewiki-ext4.sh

Le mercredi 2 novembre 2016 12:07:11 UTC+1, malkowki a écrit : > > Hi all, > > I am using linux kernel 4.1.12-bone-rt-r20 and booting the board from 4GB > SD card. > > I was trying to use the script from R.Nelson > https://github.com/RobertCNelson/boot-script

[beagleboard] writing to [/dev/mmcblk1] failed using bbb-eMMC-flasher-eewiki-ext4.sh

Hi all, I am using linux kernel 4.1.12-bone-rt-r20 and booting the board from 4GB SD card. I was trying to use the script from R.Nelson https://github.com/RobertCNelson/boot-scripts/tree/master/tools/eMMC but it ends uop with the follwing error Version: [1.20161005: sfdisk: actually calculate

Re: [beagleboard] cannot set P9.42 as INPUT MODE6 0x26

In fact I want to check the PRU memory register when the pin is set as input and forced to 3.3V. I know that from user space we use sysfs to export the pin. I have some doubt if it the same mechanism for the PRU GPIO? -- For more options, visit http://beagleboard.org/discuss --- You received

[beagleboard] cannot set P9.42 as INPUT MODE6 0x26

Dear all, I have loaded a PRU device tree as follow on Beagle bone black revC Linux version 4.1.21-bone-rt-r20 Distributor ID:Debian Description:Debian GNU/Linux 8.5 (jessie) Release:8.5 Codename:jessie /* * This program configure the PRU PINS. * There are all configured in a

Re: [beagleboard] Re: BBB, device tree seems to work, but no /dev/spidev?

y in > drivers, implementations of drivers, and things of that nature. > > > On Wed, Jul 20, 2016 at 8:47 AM, malkowki <bmb.tec...@gmail.com > > wrote: > >> I Will recompile the dtb from Robert git and flash the SD care. I Will >> keep my Kernel version since I have alr

Re: [beagleboard] Re: BBB, device tree seems to work, but no /dev/spidev?

I Will recompile the dtb from Robert git and flash the SD care. I Will keep my Kernel version since I have already use it for the PRU. I will let you know if this is work. I will also try to modify the uEnv.txt however I don't know if this will work with the 4.1.21 I am using. Thanks William

Re: [beagleboard] Re: BBB, device tree seems to work, but no /dev/spidev?

el Config file and the bootloog. > Is Anyone to guide me how to solve this issue? > > > I do believe that SPI has to be loaded earlier in the boot stage. I seem > to recall this fix for this to be loading SPI from within the main board > file. > > On Wed, Jul 20, 2

[beagleboard] Issue booting from SD om BBB while no problem on BBG, KERNEL 4.1.21-bone-rt-r20

Hello all, I am struggling with booting the BBB REVC from 4GB class 10 uSD flashed with the image 4.1.21-bone-rt-r20 and u-boot image from branch v2016.07-rc2( I have followed all the steps from R.Nelson eewiki). when I press the S2 button and plug the 5V barrel supply I can see on my serial

Re: [beagleboard] ssh not working on beaglebone after flashing eMMC

> > Start over again, and if the image you have does the same thing again, get > a different image. > > On Tue, Jun 7, 2016 at 12:19 AM, malkowki <bmb.tec...@gmail.com > > wrote: > >> I have tried >> >> sudo apt-get update && sudo apt-get -f i

Re: [beagleboard] ssh not working on beaglebone after flashing eMMC

encountered while processing: openssh-server Le mardi 7 juin 2016 09:06:27 UTC+2, malkowki a écrit : > > Hi Robert, > > I have tried the command line as you advise but this time I got the > followng error: > > /usr/sbin/dpkg-reconfigure: line 6: syntax error near unexpect

Re: [beagleboard] ssh not working on beaglebone after flashing eMMC

searched a solution on the internet but I couldn't find it any idea how to solve it? Le lundi 6 juin 2016 16:35:41 UTC+2, RobertCNelson a écrit : > > On Mon, Jun 6, 2016 at 9:33 AM, malkowki <bmb.tec...@gmail.com > > wrote: > > Hello Robert, > > > > It looks l

Re: [beagleboard] ssh not working on beaglebone after flashing eMMC

, RobertCNelson a écrit : > > On Mon, Jun 6, 2016 at 8:35 AM, malkowki <bmb.tec...@gmail.com > > wrote: > > Dear, > > > > It appears that I cannot ssh my BBB REVC after having flashed my eMMC > using > > the the Robert Nelson script bbb-eMMC-flasher-eewiki-ext4.s

[beagleboard] ssh not working on beaglebone after flashing eMMC

Dear, It appears that I cannot ssh my BBB REVC after having flashed my eMMC using the the Robert Nelson script bbb-eMMC-flasher-eewiki-ext4.sh My kernel version is 4.1.21-bone-rt-r20. I have checked the etc/ssh/ directory and I could see that all the ssh_host ... files are gone as a result