[beagleboard] Re: How to use PRU constants table?

Hi Karl, These constants allow the C compiler to produce more efficient code. Of course you can also use them in assembly programs by explicitly using lbco/sbco instructions. Let me give you an example how pru-gcc uses the constant table. Consider this C code snippet: # define MYREG ( *

Re: [beagleboard] Re: Building drivers without source on BBB

No It did not work.I just replaced the name of my module in your example Makefile .Did you follow any pre-steps before this? Rp On Tue, Jul 19, 2016 at 9:55 PM, ZeekHuge wrote: > Hi Raul Piper, > > You should probably not worry about the /lib/modules/4.1.22-bone21/ files. >

Re: [beagleboard] GPIO problems on ubuntu 16.04

One more thing, the Linux kernel used on RaspberryPi3, etc are still running in 32bit mode: https://www.linux.com/news/raspberry-pi-3-still-essentially-32-bit-sbc-now Regards, John > On Jul 19, 2016, at 6:11 PM,

Re: [beagleboard] GPIO problems on ubuntu 16.04

I don’t know why William doesn’t take a quick look on the ARM website before making statements like this. CortexA15 is a 32bit processor. CortexA53 is a low power 64bit processor. Regards, John > On Jul 19, 2016, at 6:11 PM, William Hermans wrote: > > denis, > > For

Re: [beagleboard] GPIO problems on ubuntu 16.04

denis, For what it's worth. Ubuntu mate does not seem very . . ."complete" on any ARM platform right now. For instance, the Odroid XU4 which has 4 cores A15's and 4 cores A7 uses an armv7 kernel( 32 bit ). Where the A15 cores are actually 64bit cores I believe. Same for the RaspberryPI 3 , and

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

> > Actually, it's just my locally cross built kernel that have the large > modules, for the official *.deb, the *.ko objects are separate in the > linux-image-`uname -r`-dbg package. ;) (for gcc-4.7 + that is..) > > Yeah, just adding a blacklist for users who want to tune things is the > easiest

Re: [beagleboard] Kernel update to 4.4.15-ti-r35 failure

On Tue, Jul 19, 2016 at 4:16 PM Robert Nelson wrote: > FYI, it seems to have also broken WL1835 wifi over SDIO (mmc2). >>> >>> OK, that wasn't the issue. ti-rt-r36 still fails with WL1835. >>> >>> Useful debug output: >>> >>> Jul 19 15:12:08 beaglebone kernel:

Re: [beagleboard] Kernel update to 4.4.15-ti-r35 failure

> > FYI, it seems to have also broken WL1835 wifi over SDIO (mmc2). >>> >> >> OK, that wasn't the issue. ti-rt-r36 still fails with WL1835. >> >> Useful debug output: >> >> Jul 19 15:12:08 beaglebone kernel: omap_hsmmc 4781.mmc: card claims >> to support voltages below defined range >> . >> .

Re: [beagleboard] Kernel update to 4.4.15-ti-r35 failure

On Tue, Jul 19, 2016 at 11:18 AM Jason Kridner wrote: > On Tue, Jul 19, 2016 at 10:58 AM Jason Kridner < > jason.krid...@hangerhead.com> wrote: > >> On Tue, Jul 19, 2016 at 9:37 AM Robert Nelson >> wrote: >> >>> Hi Steve, >>> >>> On Tue,

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

On Tue, Jul 19, 2016 at 1:56 PM, John Syne wrote: > Hi Robert, > > I was one of those users who uses Systemtap, but I always build my own > kernel with debug symbols enabled, so I would recommend a standard kernel > version without debug symbols and if you are up to it, add

Re: [beagleboard] GPIO problems on ubuntu 16.04

Ok, can't be helped then. :-) Thank you for spending some time on my problem. Am Dienstag, 19. Juli 2016 16:30:26 UTC+2 schrieb William Hermans: > > Do you happen to know a download location for a working ubuntu 16.04 > beaglebone image with a 4.4.x kernel? > > > No I do not. Ubuntu on the

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

Hi Robert, I was one of those users who uses Systemtap, but I always build my own kernel with debug symbols enabled, so I would recommend a standard kernel version without debug symbols and if you are up to it, add another build with a -dbg.deb kernel/modules version. Regarding the other

[beagleboard] pasm to clpru porting guide for PRU

I'm converting some PRU assembly code from pasm to clpru and finding there are some differences. An earlier thread noted some differences between the two (Use LDI, not MOV for loading

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

I guess maybe the thing to do would be to edit the universalio overlay file of choice. So that it did not touch the needed pins / peripherals used by a given cape with eeprom. On Tue, Jul 19, 2016 at 10:54 AM, William Hermans wrote: > SO, after talking with Robert and finding

[beagleboard] Re: cape-universal & 4.1.x = default.. ;)

SO, after talking with Robert and finding that all these kernel modules that get loaded from cape_universal=enable. I wonder how this impacts other capes such as the Logic supply RS232 / CAN cape that automatically loads it's own device tree overlay. Could capes such as this be loaded first,

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

Ok, thanks Robert. I am really starting to warm up to universal-io. Never had the chance, or reason to get it working before. Now . . . I'm using it to test custom cape circuits, and all kind of things. Plus I really do want to write that webpage GPIO / peripheral configuration page . . . but

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

On Tue, Jul 19, 2016 at 12:24 PM, William Hermans wrote: > Ah those! most of them come from loading the cape overlay... >> (cape_universal=enable) >> >> Regards, > > Seriously ? Wow I had no idea. Is this a requirement, or can it be changed > ? Or . . .hmmm how could one

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

temptation <--- wtf did that come from . . . dahm spell checker lol. *attemtping . . .* On Tue, Jul 19, 2016 at 10:24 AM, William Hermans wrote: > Ah those! most of them come from loading the cape overlay... >> (cape_universal=enable) >> >> Regards, > > Seriously ? Wow I had

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

> > Ah those! most of them come from loading the cape overlay... > (cape_universal=enable) > > Regards, Seriously ? Wow I had no idea. Is this a requirement, or can it be changed ? Or . . .hmmm how could one modify this behavior so that only what's needed is loaded. Other than my hackish fix.

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

Sorry Robert I did not mean to reply only directly to you . . . but also . . . a few users wanted to use systemtap: > > https://wiki.archlinux.org/index.php/SystemTap > > that needs debug_info.. > > So question about this. Are these few people more important than the rest of the users out here ?

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

On Tue, Jul 19, 2016 at 12:06 PM, William Hermans wrote: > I think it's pretty well documented here. However you could always write > up an eLinux or whatever wiki page . . . I do have my own web page > http://www.embeddedhobbyist.com/ with stuff on it that is important to >

Re: [beagleboard] How to decide min_free_kbytes size for BBB based custom board embedded Linux board

On Tue, Jul 19, 2016 at 11:11 AM, Ankur Tank wrote: > > We are using BeagleBoneBlack based custom Linux board. > It has 256MB of RAM and 4GB of eMMC. > Currently RFS size of the project is 163MB. While RFS partition size is > 500MB. > For testing, we added 20 number of big

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

I think it's pretty well documented here. However you could always write up an eLinux or whatever wiki page . . . I do have my own web page http://www.embeddedhobbyist.com/ with stuff on it that is important to me. But this information for using UIO on TI kernels I feel is largely useless. Because

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

Hi Joseph, On Tue, Jul 19, 2016 at 11:52 AM, Joseph Heller wrote: > Finally, that worked William ( )! I did a small check with an > LED and am able to with it on/off now via the PRU and uio. > > For your consideration, I wonder how you feel like to document this more

Re: [beagleboard] How to decide min_free_kbytes size for BBB based custom board embedded Linux board

I'm not sure why you feel compelled to even bother playing with this. In 20-21 years of using Linux I've never had to set this manually. But . . . https://www.google.com/search?q=%2Fproc%2Fsys%2Fvm%2Fmin_free_kbytes=utf-8 >

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

Finally, that worked William ( )! I did a small check with an LED and am able to with it on/off now via the PRU and uio. For your consideration, I wonder how you feel like to document this more structurally so others can benefit from it? I was offset by some older posts on the forum. Next

[beagleboard] Re: Building drivers without source on BBB

Hi Raul Piper, You should probably not worry about the /lib/modules/4.1.22-bone21/ files. But there might be a problem in your Makefile. You should try adding 'all' and 'clean' as PHONY targets in your makefile. You can see this Makefile for reference :

Re: [beagleboard] Kernel update to 4.4.15-ti-r35 failure

On Tue, Jul 19, 2016 at 10:58 AM Jason Kridner wrote: > On Tue, Jul 19, 2016 at 9:37 AM Robert Nelson > wrote: > >> Hi Steve, >> >> On Tue, Jul 19, 2016 at 5:00 AM, Steve Osselton < >> steve.ossel...@prismtech.com> wrote: >> >>> Hi, >>> >>>

Re: [beagleboard] Kernel update to 4.4.15-ti-r35 failure

On Tue, Jul 19, 2016 at 9:58 AM, Jason Kridner wrote: > > > On Tue, Jul 19, 2016 at 9:37 AM Robert Nelson > wrote: > >> Hi Steve, >> >> On Tue, Jul 19, 2016 at 5:00 AM, Steve Osselton < >> steve.ossel...@prismtech.com> wrote: >> >>> Hi,

Re: [beagleboard] Kernel update to 4.4.15-ti-r35 failure

On Tue, Jul 19, 2016 at 9:37 AM Robert Nelson wrote: > Hi Steve, > > On Tue, Jul 19, 2016 at 5:00 AM, Steve Osselton < > steve.ossel...@prismtech.com> wrote: > >> Hi, >> >> When updating the TI kernel from 4.4.14-ti-r34 to 4.4.15-ti-r35 on Debian >> 8.5, the kernel

Re: [beagleboard] Kernel update to 4.4.15-ti-r35 failure

Hi Steve, On Tue, Jul 19, 2016 at 5:00 AM, Steve Osselton < steve.ossel...@prismtech.com> wrote: > Hi, > > When updating the TI kernel from 4.4.14-ti-r34 to 4.4.15-ti-r35 on Debian > 8.5, the kernel failed to > boot cleanly. On connecting a console, the boot process failed in > initramfs when

Re: [beagleboard] Re: Issues with Enabling SPIDev on Beaglebone Black

Thank you Vinay and Rudy for your replies. I am using the Kernel Version 3.8.13-bone79. I realised about the L thing after my last post - thank you Rudy, that is encouraging that I have successfully disabled HDMI. I have added the suggested line in /etc/default/capemgr (CAPE=ADAFRUIT-SP0).

[beagleboard] Building drivers without source on BBB

HI, I am using this Makefile to build the kernel driver on the BBB itself(already apt-get installed build-essenatials on it). obj-m += myDrvr.o all: make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules clean: make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean But I am

[beagleboard] Re: Beaglebone black is not enumerating as ttyUSB0

The circuitry for the USB to UART cable is in the USB plug of the cable, so it should enumerate as /dev/ttyUSBx without plugging it into the board. If it doesn't appear then there is most likely an issue with the cable or the PC. If you run dmesg | tail on a terminal in Ubuntu a few seconds

[beagleboard] Re: Issues with Enabling SPIDev on Beaglebone Black

Hello all, I am new to BBB. My eventual aim is to use the BBB to flash a rom with libreboot on my Lenovo Thinkpad. I am using this guide at eLinux. It says that I need to disable HDMI before I can enable SPI. I couldn't locate the uEnv.txt

Re: [beagleboard] Re: Issues with Enabling SPIDev on Beaglebone Black

Hello all, I am new to BBB and using it to flash the ROM on my Lenovo Thinkpad T400 with Libreboot, using these instructions on eLinux. I disabled HDMI on the Beaglebone by opening vi and removing the comment from the line that says it

[beagleboard] Re: cryptsetup / LUKS disk encryption on Debian not working

Hai friend, Please try to execute the command as root user or use sudo command On Wednesday, 23 July 2014 00:37:07 UTC+5:30, Niko Heeren wrote: > > Hello > > I am trying to encrypt a USB drive using the BBB and Debian wheezy (Kernel > 3.8.13-bone20). > > So the command I try is: > cryptsetup

Re: [beagleboard] Re: Issues with Enabling SPIDev on Beaglebone Black

I've attached the SPI device tree files I used. Hope this help ya out!! On Tue, Jul 19, 2016 at 12:47 PM, Rudy Misek wrote: > Whats crack'n Vinay!! Looks to me like Wheezy. > > Hey Will, > 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI > 6:

Re: [beagleboard] Re: Issues with Enabling SPIDev on Beaglebone Black

Whats crack'n Vinay!! Looks to me like Wheezy. Hey Will, 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN The L in P-O-L means loaded, so in the case above it's telling you that the HDMI hasn't been loaded. So

Re: [beagleboard] Re: Issues with Enabling SPIDev on Beaglebone Black

Can you provide info about the kernel your using? On 18 July 2016 at 13:02, wrote: > Hello all, I am new to BBB and using it to flash the ROM on my Lenovo > Thinkpad T400 with Libreboot, using these > instructions on >

[beagleboard] Kernel update to 4.4.15-ti-r35 failure

Hi, When updating the TI kernel from 4.4.14-ti-r34 to 4.4.15-ti-r35 on Debian 8.5, the kernel failed to boot cleanly. On connecting a console, the boot process failed in initramfs when trying to mount the real boot partition (the eMMC). The mount command from initramfs was complaining about