> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
> Behalf Of Dennis Lee Bieber
> On Tue, 25 May 2021 19:44:55 -0700, in gmane.comp.hardware.beagleboard.user
> "John Dammeyer" wrote:
>
>
> >
> >OK. Hadn't noticed until I tried it on the Beagle that it uses
>
Hi Dennis,
I will investigate that further. Wanted to get the SPI bus Type K Thermocouple
module working first. Baby steps.
The code is slightly different from the Pi but not radically so. I used
'/dev/spi/0.0' since there is no '/dev/spidev0.0' on my Beagle.
>
> My concern was that
And yet more progress using the pxl library and Lazarus with the rewritten code
from the pxl Blinky.pas example and adafruit_max31855.py. SPI bus operation.
Source code attached.
debian@ebb:~/lazarus/TC$ ./TC
Reading temperature, press any key to exit...
Temperature: 21.25C 70.25F
On Tue, 25 May 2021 19:44:55 -0700, in gmane.comp.hardware.beagleboard.user
"John Dammeyer" wrote:
>
>OK. Hadn't noticed until I tried it on the Beagle that it uses
>PXL.Boards.RPi.pas which has the definitions for the high speed I/O. The
>Beagle doesn't appear to have that feature as there
On Tue, 25 May 2021 19:16:51 -0700, in gmane.comp.hardware.beagleboard.user
"John Dammeyer" wrote:
>Hi Dennis,
>I tried on the groups site to edit this post and change what I wrote.
While the master copy appears to be a Google Groups entry, it seems to
be propagated outward since gmane
> Because this example program uses the high speed gpio the fault happens much
> sooner on the Pi without the sudo.
>
> pi@raspberrypi:~/projects/lazarus/TC $ ./TC
> An unhandled exception occurred at $00084EE4:
> ERPiOpenFile: Cannot not open
> file
Hi Dennis,
I tried on the groups site to edit this post and change what I wrote.
I meant to say both systems _do_not_ place local variables on the heap. In
fact I'm not sure that static are placed on the heap since that could cause all
sorts of fragmentation issues.
The advantage of static is
On Tue, 25 May 2021 12:55:32 -0700, in gmane.comp.hardware.beagleboard.user
"John Dammeyer" wrote:
>My understanding is both systems place the variables on the heap. Only the
>small micro-controllers with limited stack space (recall some of the PIC16
>series had a 2 word call stack). Other
ps.com] On
> Behalf Of Dennis Lee Bieber
> Sent: May-25-21 10:39 AM
> To: Beagleboard
> Subject: [beagleboard] Re: ioctl messages to Beagle SPI port.
>
> On Tue, 25 May 2021 09:45:39 -0700, in gmane.comp.hardware.beagleboard.user
> "John Dammeyer" < <mailto:jo
On Tue, 25 May 2021 09:45:39 -0700, in gmane.comp.hardware.beagleboard.user
"John Dammeyer" wrote:
>
>Here's the BBB version from and you can see the code is identical for both the
>Pi and the Beagle.
So I've solved the problem with the
ESysfsSPITransfer: Cannot transfer <1> data byte(s) through SPI bus.
The C versions with the spi_ioc_transfer structure declared inside the
transfer() function work on both the Beagle and Pi3.
Here's the BBB version from and you can see the code is
#Let's call it AssignIO(). This requests and locks #the scarce resource in
prep for an open. Odds are #unless you have some fancy hardware #multiplexing
it would stay assigned for the entire #program. But nothing stops you from
doing a #ReleaseIO() and then setting a GPIO bit to mux in #the
> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
> Behalf Of Dennis Lee Bieber
> On Fri, 21 May 2021 09:39:34 -0700, in gmane.comp.hardware.beagleboard.user
> "John Dammeyer" wrote:
>
> >static const char *device = "/dev/spidev1.0";
> > fd = open(device,
On Fri, 21 May 2021 09:39:34 -0700, in gmane.comp.hardware.beagleboard.user
"John Dammeyer" wrote:
>static const char *device = "/dev/spidev1.0";
> fd = open(device, O_RDWR);
> if (fd < 0)
> pabort("can't open device");
>
>One of two things happen. Either It opens the
On Fri, May 21, 2021 at 11:54 AM John Dammeyer wrote:
>
> Gawd, I can't even get the math right. 8 blocks of 4096 make up 32K.
>
> At the moment I suspect one of my 320x240 displays might be toast. Even the
> Python code doesn't light up the screen and that used to work. But it was
> way
age-
> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
> Behalf Of John Dammeyer
> Sent: May-21-21 9:40 AM
> To: beagleboard@googlegroups.com
> Subject: RE: [beagleboard] Re: ioctl messages to Beagle SPI port.
>
> Thanks Dennis,
>
>
> >
On Fri, May 21, 2021 at 11:40 AM John Dammeyer wrote:
>
> Thanks Dennis,
>
>
> > -Original Message-
> > From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
> > Behalf Of Dennis Lee Bieber
> > "John Dammeyer" wrote:
> >
> >
> > >The sad thing is that Derek
Thanks Dennis,
> -Original Message-
> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
> Behalf Of Dennis Lee Bieber
> "John Dammeyer" wrote:
>
>
> >The sad thing is that Derek Molloy's book, only in passing refers to
> >enabling the SPI port, and the
On Thu, 20 May 2021 19:19:08 -0700, in gmane.comp.hardware.beagleboard.user
"John Dammeyer" wrote:
>The sad thing is that Derek Molloy's book, only in passing refers to enabling
>the SPI port, and the book, in trying to also deal with the pocket beagle pins
>leaves out things where repetition
19 matches
Mail list logo
