Just in case you do not know already.
https://eewiki.net/display/linuxonarm/BeagleBone+Black That guide is for
the black, there is one for the white, but don't know if there is one for
the blue, or any of the wireless variants.
On Wed, Jun 21, 2017 at 5:52 PM, William Hermans <yyrk...@gmail.
mzimmers,
You know, I tried a few different guides when building the kernel and none
of them worked until I found Robert's build guide( 4+ years ago ). In your
shoes, I would probably forget about trying to follow DR Molloy's book in
this case, and just use Robert's guide. Because no one is going
I suppose it would be useful if I actually shared the link I was tlaking
about. heh https://www.youtube.com/watch?v=aMUh9DmFLto
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To
On Sat, Jun 17, 2017 at 7:33 PM, Robert Nelson
wrote:
> On Sat, Jun 17, 2017 at 9:28 PM, 'LV LV' via BeagleBoard
> wrote:
> >
> > I want to develop something for my home that has a GUI on the BB with
> LCD3
> > cape.
> > At $1000/year Qt
By the way, I would be willing to help you with testing. I have two Windows
machines here on which I can test. 1 Windows 7 pro x64 machine, and 1
Windows 10 pro x64 machine.
With that said, I'm pretty busy, so the clearer your documentation is, the
more likely I will be able to help you test,
On Fri, Jun 16, 2017 at 1:16 PM, Ravi Kumar Prasad <7rav...@gmail.com>
wrote:
> HI,
> I'm a GSoC student with BeagleBoard.org this year. My project is to
> develop a GUI based usb flashing tool for BeagleBone hardware.
> The tool comprises of two parts a nodejs usb bootloader server which tftps
>
My personal experience has led me to believe, no you can not. About the
only peripheral that I've noticed does not give issue when running off USB
power is ethernet. But we've tried to run ethernet + CANBUS, and no go . .
. and in this specific case, the board was being powered by a 1a wallwart
to
gt; I very much appreciate your help. Possibly vcan is what I am looking for.
> I will try it and let you know. My actual physical can interface is working
> fine we want something for automated testing.
>
> Thanks
>
> Yash
>
> Yashwant Shitoot
>
> On Wed, Jun 14, 2017 a
http://www.embeddedhobbyist.com/2015/09/linux-can-development/
On Wed, Jun 14, 2017 at 4:11 PM, wrote:
> Hello,
>
> For testing purpose I would like to feed dummy data to my program. Ideally
> my program would call read (socket can) and think the data came from can
> device.
Derrek Molly has a semi recent 3 piece set of article on his exploring
beagelbone web site. For creating Linux device drivers.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To
On Sun, Jun 11, 2017 at 5:01 PM, William Hermans <yyrk...@gmail.com> wrote:
> Now as far as direct memory access to the I2C hardware. Well, it's not
> impossible, and is probably already being done in the driver module for the
> beaglebone's hardware. In kernel space. So, if
Now as far as direct memory access to the I2C hardware. Well, it's not
impossible, and is probably already being done in the driver module for the
beaglebone's hardware. In kernel space. So, if you're dead set on learning
that, you'd need to look into the am335x I2C kernel driver source for that.
On Sun, Jun 11, 2017 at 3:04 PM, mzimmers wrote:
> Hi William -
>
> Yeah, sorry about that...I was being lazy. The output of perror says
> "Connection timed out" though the first time the write is called, errno is
> 22. In the next write attempts, errno is 110 (agreeing with
On Sun, Jun 11, 2017 at 8:01 AM, mzimmers wrote:
> Hi -
>
> I'm reading chapter 8 of Dr. Molloy's book, which discusses bus access.
> The example I'm working on right now uses the file system to access devices
> on the I2C bus. I recognize that this is a typical way to access
Sorry, AIN0-AIN6, but you got the idea already hopefully. And just to be
clear, you would only need one pf the ADC lines, not all 7.
On Fri, Jun 9, 2017 at 11:57 AM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Fri, Jun 9, 2017 at 11:47 AM, David McRell <dmcrell.c
On Fri, Jun 9, 2017 at 11:47 AM, David McRell
wrote:
> Hello,
>
> What is the purpose of the resistor divider connected to AIN7? What
> software is dependent on this, if any?
>
> Is this only a convenient connection to quickly test ADC functionality? I
> find no
If the driver is loading, it's very unlikely the hardware is setup
incorrectly. I will tell you from hands on, if you manually load your RTC
driver like this. You may have to write to the RTC, before reading from it.
Otherwise you'll experience that error, or one similar to it.
--
For more
On Sat, Jun 3, 2017 at 9:37 AM, wrote:
> Hello to all. I recently bought the BBB. Starting with this card, I would
> like to know some information. My BBB does not have an SD card, but I use
> only the 4GB eMMC. Linux is already pre-installed on eMMC and I think
>
On Thu, Jun 1, 2017 at 5:13 PM, Mary Metelko wrote:
> The Adafruit_BBIO code usage does work when the user is root.
>
Then it's a matter of permissions. Which means you need to adjust
permission forr the user using those applications. Make udev rules for the
hardware
403 error Mark, we do not have permissions to see that image. e.g. I've
done this before, and usually it's because I had not shared the image
properly, and / or the link I've given was for my eyes only.
On Fri, Jun 2, 2017 at 6:54 AM, Mark A. Yoder
wrote:
> I've been
On Thu, Jun 1, 2017 at 2:26 PM, Metelko wrote:
> I have updated my system starting with a base image from:
> https://rcn-ee.com/rootfs/2017-04-07/elinux/ubuntu-16.
> 04.2-console-armhf-2017-04-07.tar.xz
> Then updating the kernel: Linux bbb-266a 4.9.30-ti-rt-r37 #1 SMP
Graham, that wont fix the issue. The problem he's having is because the OS(
Linux ) is not setup to use the serial interface. You can tell, because he
is getting serial messages from the kernel until after the kernel is
loaded. Which means the rootfs is meant to "take over" but isn't.
On Mon, May
That's /boot/uEnv.txt, typo above.
On Sun, May 28, 2017 at 11:57 PM, William Hermans <yyrk...@gmail.com> wrote:
> First, you disable universal IO, second, if you do not need hdmi, you
> disable hdmi video, and audio at boot. Through /boot.uEnv.txt. This will
> free up any pin tha
First, you disable universal IO, second, if you do not need hdmi, you
disable hdmi video, and audio at boot. Through /boot.uEnv.txt. This will
free up any pin that's not related to I2C-0, I2C-2, the eMMC, and possibly
a few others I'm not thinking of off the top of my head.
On Sun, May 28, 2017
Yes,
echo BB-BONE-SWI:00A0
needs to change to:
echo BB-BONE-SWI
On Sat, May 27, 2017 at 12:15 PM, jmelson wrote:
>
>
> On Saturday, May 27, 2017 at 2:12:05 PM UTC-5, jmelson wrote:
>>
>>
>>
>>
>> echo BB-BONE-SWI:00A0 > /sys/bus/platform/devices/bone_capemgr/slots
>>
the AM335x processor.
I posted some code on the groups here yesterday, or the day before for the
full code listing of what I'm using an explanation above. Pretty much, a
really simple, and to the point line select using 3 GPIO's, and an IO pin
multiplexer.
On Fri, May 26, 2017 at 5:45 PM, Willi
You can get that info from the AM335x TRM I beleive but what I do to get
this information is to do something such as this:
root@wgd:~/# ls /sys/devices/platform/ocp/*.gpio/gpio/
/sys/devices/platform/ocp/*44e07000*.gpio/gpio/:
gpio2 gpio22 gpio23 gpio26 gpio3 gpiochip0
up to
"you".
On Thu, May 25, 2017 at 3:53 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Thu, May 25, 2017 at 1:10 PM, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>
>> On Thu, May 25, 2017 at 3:08 PM, jmelson <el...@pico-systems.com> wrote:
On Thu, May 25, 2017 at 1:10 PM, Robert Nelson <robertcnel...@gmail.com>
wrote:
> On Thu, May 25, 2017 at 3:08 PM, jmelson <el...@pico-systems.com> wrote:
> >
> >
> > On Thursday, May 25, 2017 at 2:05:44 PM UTC-5, William Hermans wrote:
> >>
&g
So it's been a while since I've used __delay_cycles() in any code for any
hardware. But the general reason why I've not used it is that the
implementation from one piece of hardware to another is, or can be
different, and it's a "software way" to time things. Which is to say, it
can sometimes be
his video, although he still refers to the
> original one on his website.
> --- Graham
>
> ==
>
> On Tue, May 23, 2017 at 5:16 PM, William Hermans <yyrk...@gmail.com>
> wrote:
>
>> https://www.youtube.com/watch?v=T9yFyWsyyGk
>>
>> . . .
>>
>&g
https://www.youtube.com/watch?v=T9yFyWsyyGk
. . .
On Tue, May 23, 2017 at 3:11 PM, Graham wrote:
> I don't know of a single resource that covers the whole chain.
> The closest is Derek Molloy's
> http://derekmolloy.ie/beaglebone/setting-up-eclipse-
>
And yeah, we could also be using bare metal hardware in tandem with a
beaglebone for even better performance. But that would also require C / C++
at minimum, and honestly is not needed for our own purposes.
On Mon, May 22, 2017 at 2:43 PM, William Hermans <yyrk...@gmail.com> wrote:
>
&
On Mon, May 22, 2017 at 12:51 PM, Niels Jakob Buch wrote:
> I am thinking that its a shame, when there is a splendid opportunity to
> move into higher level languages and managed code. We have a full-blown
> computer here, with an operating system, and we are using the same
>
On Mon, May 22, 2017 at 4:25 AM, Niels Jakob Buch wrote:
> Thanks for your feedback, very substantial stuff, I appreciate and
> confirms the fact that some of this is due to lack of experience with
> simple linux and device tree concepts.
>
> As the amount of information is
Sounds like fun. GPIO is super easy on this platform, once you know how the
GPIO subsystem works. PWM and ADC is a little more complicated. but not
much. PWM can be a bit of a bugger, because some of the examples do not
really work( overlays ). With PWM it becomes an exercise of wills, as you
the
oops, https://github.com/wphermans/bb-info is the top most path . . .
On Sat, May 20, 2017 at 6:27 PM, William Hermans <yyrk...@gmail.com> wrote:
> By the way these are my own preffered "pin mux mode" "spread sheet" PDF
> files for working with various pins: ht
to who created them. Whom also derived the information in these files from
Derrek Molloy.
So I do not claim the material at all. I just wanted a location that was
easy for me to find, and would never go away. My git seemed to be as good a
place as any, for me.
On Sat, May 20, 2017 at 6:14 PM, W
n the TRM into the SRM. That is why the
> SRM is specific to the BBB. And the TRM gets updated failry often by TI.
>
>
>
> Gerald
>
>
>
>
>
> *From:* beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
> *On Behalf Of *William Hermans
> *Sent:* Sa
System reference manual SRM, Technical reference manual TRM.
On Sat, May 20, 2017 at 5:58 PM, William Hermans <yyrk...@gmail.com> wrote:
> No, prior to uboot overlays, overlays were loaded from the initrd, at
> best. Also we need to understand that the board file(also an overla
No, prior to uboot overlays, overlays were loaded from the initrd, at best.
Also we need to understand that the board file(also an overlay of sorts -
but required )is seperate from all this discussion.
I do not understand why you would have "field people" playing around with
hardware overlays
I do not use OSX myself, but have reports from a coworker that dd on OSX is
somehow incompatible with these images. e.g. images made with dd in OSX
fail, but work perfectly fine when created with Linux dd.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message
On Fri, May 19, 2017 at 3:34 AM, Niels Jakob Buch wrote:
> The frustration level is growing...
>
Sounds like you're experiencing the same thing I did when first starting.
One of the biggest hurdles here is going to be related to your knowledge of
Linux. After that, knowing the
On Fri, May 19, 2017 at 8:42 AM, Clark Sann wrote:
> William
>
> If I power my IO through the 3.3V bus on the BB Blue, which turns on as
> the BB Blue turns on, will that be sufficient to protect the GPIO?
>
As Jason mentioned. Please make a separate new post / thread so as
On Wed, May 17, 2017 at 8:35 PM, Greg Ercolano wrote:
> > . . .
>
So a lot of text there to "Wade" through so I'll try to answer the
questions you have in order. Without the "Sea of text" ;)
I think Universal IO, which includes the shell script config-pin is a
really cool
On Thu, May 18, 2017 at 2:06 PM, Niels Jakob Buch wrote:
> Argh, waiting on a pile of JST-XX connectors to get the Blue-world up and
> running. But thanks!
>
So, I actually have no idea of the pin pitch on those JST headers. But the
serial debug cable I bought years ago, and
attaching the cable does not work
>
> Now comes the noob question: How do I attach the cable, seems that there
> is plenty BeagleBone Black tutorials on that, but not sure how to do it on
> the blue one.
>
> On Wednesday, 17 May 2017 23:49:32 UTC+2, William Hermans wrote:
>>
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
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
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
lol dahm text correction got me good that time "obstacle"
On Tue, May 16, 2017 at 1:26 AM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Tue, May 16, 2017 at 1:07 AM, Joseph Heller <joseph.heller...@gmail.com
> > wrote:
>
>> On Tuesday, May 16
On Tue, May 16, 2017 at 1:07 AM, Joseph Heller <joseph.heller...@gmail.com>
wrote:
> On Tuesday, May 16, 2017 at 3:27:07 AM UTC+2, William Hermans wrote:
>>
>>
>>
>> On Wed, Apr 26, 2017 at 1:02 AM, Joseph Heller <joseph.h...@gmail.com>
>> wrote:
>
On Wed, Apr 26, 2017 at 1:02 AM, Joseph Heller
wrote:
> Updated link: http://catch22.eu/beaglebone/beaglebone-pru-c/
>
I may have mentioned this before, but I think blinking a USR LED would be
far more useful. Nothing to hook up, and worry about blowing the pins on
Also very glad you chose to demonstrate this using UIO, instead of
remote_proc.
On Mon, May 15, 2017 at 6:26 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Wed, Apr 26, 2017 at 1:02 AM, Joseph Heller <joseph.heller...@gmail.com
> > wrote:
>
>> Updated l
There are many way to build a development environment. Me, I just compile
on the beaglebone directly, and if I need anything "big" compiled, I have
an ODROID XU4 - Octa core 2G ram. I've only ever needed to use a debugger
once, and not for these platforms. If I did however, I'd use gdb, and
By the way, websockets put simply, is a TCP connection between systems,
that is always connected. So there is no need for Ajax, or any of that old
school HTML mumbo jumbo.
On Sun, May 14, 2017 at 4:04 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Sun, May 14, 2017 at 12
On Sun, May 14, 2017 at 12:38 PM, Piotr C wrote:
> Thanks for suggestions.
> Do you have any further hints/examples/similar implementations that I
> could read, understand and eventually base on?
>
The code I wrote is not, and will not be available to the public.
There is
On Sun, May 14, 2017 at 11:47 AM, William Hermans <yyrk...@gmail.com> wrote:
> Either pipe the output of candump to a file, or write your own application
> to actually parse the PGN values, then dump the parsed data into a file.
> Then have a second application take that data,
Either pipe the output of candump to a file, or write your own application
to actually parse the PGN values, then dump the parsed data into a file.
Then have a second application take that data, and send it out over a
websocket to the browser.
You'll need a file lock on this shared file, and it
Ok, so I have identified the problem. GPI on the beaglebone is
comparatively slow to GPO when changing state, but it's no where near as
bad as I thought. The actual "cutoff" for GPI changes to take effect are
somewhere between 500, and 1000 uSec. Or between .5, and 1 millisecond. I
tested all the
So, same kernel but RT PREEMPT enabled. The only code that's changed:
sleep(.2);
printf("PWM1 %u Z1IN %u\n", !!(*gpio0_out & PWM1), !!(*gpio1_in & Z1IN));
printf("PWM2 %u Z2IN %u\n", !!(*gpio0_out & PWM2), !!(*gpio1_in & Z2IN));
printf("PWM3 %u Z3IN %u\n", !!(*gpio1_out & PWM3),
Sure seems to indicate there is a bug in the gpio driver somewhere . . . it
does not get any faster than this, and yes, the sleep()s are required AGAIN.
root@wgd:~/dl-i2c-test# nano tst.c
root@wgd:~/dl-i2c-test# gcc -Wall -o tst tst.c
root@wgd:~/dl-i2c-test# ./tst
PWM1 1 Z1IN 0
PWM2 1 Z2IN 0
low down.
The above is with a sleep value of 200ms, and we can see that the inputs
have not caught up with the output in the second half of the test.
On Sat, May 13, 2017 at 4:02 PM, William Hermans <yyrk...@gmail.com> wrote:
> Something odd I'm just now noticing is that GPI on the beagl
Todd, how are you powering your board ? Hopefully not via USB . . .
On Sat, May 13, 2017 at 4:10 PM, acheesehead wrote:
> Yes, small dongle. It is plugged into a powered USB hub. Disabled HDMI in
> uEnv.txt. Rebooted and still no joy.
>
> I tried the Debian image on the
Something odd I'm just now noticing is that GPI on the beaglewbone seems to
have some lag.
What I'm doing:We have a cape with 6 channels PWM, 6 pins input, and
several pins output. In order to test the PWM circuitry on our capes, I'm
configuring these pins as GPO's, and we have a test header
On Sat, May 13, 2017 at 12:59 PM, acheesehead wrote:
> Thanks for your help William. I will try to somehow upgrade the image.
>
No problem. Yeah, I knew you probably did not want to hear "upgrade to a
latest Debian image", but most people here who would be able to help
On Sat, May 13, 2017 at 12:53 PM, acheesehead wrote:
> root@beaglebone-exp:~# opkg list-installed |grep ralink
> linux-firmware-ralink - 1:0.0+r8-gitAUTOINC+c530a75c1e6a472b0eb9558310b518
> f0dfcd8860-r8.1
>
At this point, you're on your own with google. Unless someone
-r8.1
> - linux-firmware version 0.0+r8-gitAUTOINC+c530a75c1e6a472b0eb9558310b518
> f0dfcd8860-r8
>
>
> On Saturday, May 13, 2017 at 1:31:30 PM UTC-6, William Hermans wrote:
>>
>> You have opkg . . .
>>
>> --
> For more options, visit http://beagleboard.
stalled the Angstrom image on the DVD that came
> with the display. I did reboot.
>
> On Saturday, May 13, 2017 at 1:12:14 PM UTC-6, William Hermans wrote:
>>
>> What does this show for your system ?
>> root@wgd:~# apt-cache search firmware-ralink
>> firmwa
What does this show for your system ?
root@wgd:~# apt-cache search firmware-ralink
firmware-ralink - Binary firmware for Ralink wireless cards
And if that shows what does:
root@wgd:~# dpkg -l | grep ralink
Show for you ? It does not return anything for me, but I also do not have a
realtech wifi
On Sat, May 13, 2017 at 11:48 AM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Sat, May 13, 2017 at 11:46 AM, William Hermans <yyrk...@gmail.com>
> wrote:
>
>> nan == "not a number". So something you've "hacked" is most likely
On Sat, May 13, 2017 at 11:46 AM, William Hermans <yyrk...@gmail.com> wrote:
> nan == "not a number". So something you've "hacked" is most likely
> causing that output.
>
Quite possibly related to sending output from an unsigned char, or
character typ
nan == "not a number". So something you've "hacked" is most likely causing
that output.
On Sat, May 13, 2017 at 11:36 AM, Michael K Johnson
wrote:
> Furthermore, when I hack the library to write the calibration file even if
> the sanity checks fail, just so I can see what it
Oh, and right, running fdisk -l on the partition wont work either. You have
to issue the command on the block device in whole. As I showed above.
On Sat, May 13, 2017 at 10:13 AM, William Hermans <yyrk...@gmail.com> wrote:
> By the way, the above from the "live"
By the way, the above from the "live" image was from eMMC. If that matters.
On Sat, May 13, 2017 at 10:10 AM, William Hermans <yyrk...@gmail.com> wrote:
> So I usually use this method:
>
> On Beaglebone:
> root@wgd:~# cat /etc/dogtag
> BeagleBoard.org Debian
So I usually use this method:
On Beaglebone:
root@wgd:~# cat /etc/dogtag
BeagleBoard.org Debian Image 2017-04-02
On Debian support system:
william@eee-pc:~$ unxz bone-debian-8.7-console-armhf-2017-04-02-1gb.img.xz
william@eee-pc:~$ file bone-debian-8.7-console-armhf-2017-04-02-1gb.img
Write that information down . . .
On Sat, May 13, 2017 at 9:17 AM, William Hermans <yyrk...@gmail.com> wrote:
>
> On Sat, May 13, 2017 at 5:20 AM, Dennis Lee Bieber <wlfr...@ix.netcom.com>
> wrote:
>
>> On Fri, 12 May 2017 17:49:39 -0700, William Hermans
&g
On Sat, May 13, 2017 at 5:20 AM, Dennis Lee Bieber <wlfr...@ix.netcom.com>
wrote:
> On Fri, 12 May 2017 17:49:39 -0700, William Hermans
> <yyrk...@gmail.com> declaimed the following:
>
> >By the way, similar to what Graham mentioned. Get a larger sdcard.
> >Perso
r anything of that nature, but you can render the disk unreadable. e.g.
lose your existing data.
On Fri, May 12, 2017 at 5:24 PM, William Hermans <yyrk...@gmail.com> wrote:
> This is the specific post I mentioned: https://groups.google.com/
> forum/#!searchin/beagleboard/William$20Rober
This is the specific post I mentioned:
https://groups.google.com/forum/#!searchin/beagleboard/William$20Robert$20Reduce$20rootfs|sort:relevance/beagleboard/0IDdkljrWOE/9V3X0gSvMHkJ
On Fri, May 12, 2017 at 5:14 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Fri, May 12,
On Fri, May 12, 2017 at 5:33 AM, Christopher Burian
wrote:
> William, I didn't get very far with apt-get remove before I was still left
> with lots of cruft and not knowing what I can get rid of without breaking
> things.
>
> Best regards,
> Chris
>
So, you need to be more
On Fri, May 12, 2017 at 9:44 AM, Graham Haddock
wrote:
> I take back what I said about a non standard read sequence. I re-read the
> data sheet, and they describe a standard concatenated write/read sequence
> for a single byte read. But I do note that they do not describe
No. You don't boot from a chroot, you simply pivot from one rootfs to
another. I suggest you go out and do some reading and experiment on your
own. Additionally, chroot does not imply QEMU either.
On Thu, May 11, 2017 at 6:59 PM, Riko Ho wrote:
> Hi Everyone,
>
> Is
Need more information. e.g.we need to see your uboot environment file. Also
need to see the output from the serial debug port.
On Thu, May 11, 2017 at 12:07 PM, Andy Nelson wrote:
>
> Hi I'm running Freepbx (asterisk) for beagle bone black latest build/.
>
> I can boot
> On Thursday, May 11, 2017 at 11:44:40 AM UTC-5, Torsten K. wrote:
>>
>>
>> Hi,
>>
>> two weeks ago I received my BeagleBone Blue.
>>
>> So far, I've managed to get
>>
>> - an OrangeRX DSMX receiver
>> - a GP-735T GPS receiver
>> - a Servo
>> - and a 2S LiPo Akku
>>
>> going, more or less
As for why your pin is not "sticking" low until to go high. My first
instinct is there is a logic flaw in your code. However, something else did
cross my mind. Is that pin floating ? Or is there a weak pullup / pulldown
on it ?
--
For more options, visit http://beagleboard.org/discuss
---
You
So, I'm having a hard time following your code there, based on what you're
explaining in English. We'll just chalk that up to you code your way, I
code mine, blah blah blah . . .
But what's bothering me is this bit of(condensed ) code:
while(1){
> if (clock == 1){// Check for Start
On Wed, May 10, 2017 at 8:41 AM, Christopher Burian
wrote:
> Hi all,
>
> I'd like to install x264 and ffmpeg, but ran out of space while
> downloading ffmpeg source. I'm ordering some micro SD cards to work with
> but once I'm done developing, I'd like to be booting off
More information needed.
On Wed, May 10, 2017 at 8:19 AM, Christopher Burian
wrote:
> Hi all,
>
> Using a brand new Beagleboard Green, I set it up to connect to the
> internet through a Windows PC and ran apt-get update then apt-get upgrade
>
> After the upgrade, which
More information needed.
On Wed, May 10, 2017 at 2:45 AM, wrote:
> Hi!
>
> I am trying to set up a RTC (DS1307) on my Beaglebone Blue, but, I can
> not. I've followed some BeagleBone Black tutorials, but, unsuccessfully
>
> Has anyone managed to configure it? Any
On Tue, May 9, 2017 at 11:20 AM, William Hermans <yyrk...@gmail.com> wrote:
> I'm noticing on the second system spi_omap2_mcspi is loading as well. One
> thing I have also noticed is that with recent TI kernels,kernel modules
> seem to remove themselves when not needed, or possi
I'm noticing on the second system spi_omap2_mcspi is loading as well. One
thing I have also noticed is that with recent TI kernels,kernel modules
seem to remove themselves when not needed, or possibly conflicting with
another driver. Which is a good thing, but also, could potentially be a bad
On Tue, May 9, 2017 at 10:16 AM, Gaurav S wrote:
> Hello All,
> With LCD, it seems like SPI is behaving awkwardly. I have two beagle bone
> boards one with LCD plugged in (SYS1) and the other stand alone beagle bone
> (SYS2), both running latest debian lxqt 2gb image
A few things about your code.
First, if you're concerned about performance, you're using the wrong
language. Wrong type of a language for that matter. You should be using C,
C++, or ASM. *IF* you're concerned about performance.
Secondly, calling a time() related function in your main loop, every
On Tue, May 9, 2017 at 1:47 AM, wrote:
> Hi there,
>
> I´m pretty new to Linux and the BBB. I´m using Debian Jessie and
> struggling with the DTO. I think I have an little idea now how it works. I
> try to export a dtbo to the slots.
>
> this is what i get when i cat the
Uh yeah, HERE is the link: http://elinux.org/Ti_AM33XX_PRUSSv2#C_Compiler
hehehe . . .
On Mon, May 8, 2017 at 6:59 PM, William Hermans <yyrk...@gmail.com> wrote:
> Hi Clark,
>
> No, you do not need to use Code Composer Studio. You can use the old TI
> ASM toolchain, and there a
Hi Clark,
No, you do not need to use Code Composer Studio. You can use the old TI ASM
toolchain, and there are two C compilers for the PRU's. One of which is
also from TI. Someone else ported gcc to the PRU as well.
Here is a link to a list of compilers, the first one from TI is the cgt C
On Sun, May 7, 2017 at 5:42 PM, Riko Ho wrote:
> I hadn't done :
>
> $ sudo dd if=buildroot/output/images/rootfs.ext4 of=/dev/sdb2
>
> may be that's the problem ?
>
>
As Robert said, no that's not the problem. I'm kind of wondering how old
the sources are that buildroot
On Sun, May 7, 2017 at 4:35 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Sun, May 7, 2017 at 3:38 PM, Riko Ho <antonius.r...@gmail.com> wrote:
>
>> I have boot and root partition. And I have put sdcard.img on boot by cp
>> command, will t
On Sun, May 7, 2017 at 3:38 PM, Riko Ho wrote:
> I have boot and root partition. And I have put sdcard.img on boot by cp
> command, will that work?
>
What is a "sdcard.img" ? Elaboration is required.
But typically, no it wont work. Typically, you'll want to use dd, or
101 - 200 of 4107 matches
Mail list logo