> Okay, 4.4.22-ti-r49 has hit the repo:
I can no longer reproduce the issue with 4.4.32-ti-r68. Thanks a lot, Nelson.
-- Juliusz
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To
No luck... it hangs again in the same stage. Any other tips?
Cheers
FBP
On Friday, November 18, 2016 at 7:01:36 PM UTC-3, RobertCNelson wrote:
>
> On Fri, Nov 18, 2016 at 3:53 PM, Felipe Brito > wrote:
> >
> > I'm trying to reflash the BBB emmc. I have the microSD 16GB
Thanks, Downloading now and will let you know.
As of this revision (rev C) I dont need to hold the usr button while
booting?
Cheers
FBP
On Friday, November 18, 2016 at 7:01:36 PM UTC-3, RobertCNelson wrote:
>
> On Fri, Nov 18, 2016 at 3:53 PM, Felipe Brito > wrote:
> >
On Fri, Nov 18, 2016 at 3:53 PM, Felipe Brito wrote:
>
> I'm trying to reflash the BBB emmc. I have the microSD 16GB installed with
> win32IMG and BBB-blank-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb
>
> I have the BBB powered by a 5V 2AMP.
>
> I have modified the uEnv.txt
I'm trying to reflash the BBB emmc. I have the microSD 16GB installed with
win32IMG and BBB-blank-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb
I have the BBB powered by a 5V 2AMP.
I have modified the uEnv.txt uncomment the correct line
The BBB starts with the led sequence when booted 1 2 3 4 3 2 1
I have been trying to flash the emmc from my BBB
I did modify the /boot/ file so it does the flashing directly from the
micro SD
The micro SD has been written with Win32 Image Writer
When I boot with the microSD, all 4 leds go sequentially. After a couple of
minutes, led USR1 stays on and the
On Fri, Nov 18, 2016 at 6:22 AM Paul Plankton
wrote:
> Hm, still not working. I have a MLO-file which works smoothly out of a
> FatFS partition but when I try to write it to the MMC directly with
>
> sudo dd if=./MLO of=/dev/mmcblk1 count=1 seek=1 bs=128k
>
Do you have
Go into the PRU support package examples directory. See if you can get the
PRU_Halt to compile. This is the simplest possible C program for the PRU.
All you have to do is the command make, and this will kick off the process.
You will need to have the PRU_CGT environment variable set and also a
Hi,
I'm trying to send events from a PRU C program to the host. At the moment
my PRU code just delays for 1s, then activates PRU_EVTOUT_1 and toggles an
LED so I know it's working ok. My host program sits there waiting for the
PRU_EVTOUT_1 event, then is supposed to increment a counter and
sevgi aydın:
I have a working copy sd2828 800x1280 with 8inch screen.
On Fri, Nov 18, 2016 at 9:13 PM, Gerald Coley
wrote:
> You are loading down the boot pins with your design. .
>
> http://www.elinux.org/Beagleboard:BeagleBoneBlack#
> Expansion_Header_Pin_Usage
>
>
>
h that's my problem. I was only using
pasm -b blink2.asm
which doesn't link against anything. I had missed that because most of the
other examples that I had read where using the UIO pru loader, which
doesn't require any linking of the remoteproc. I had planned on switching
to C in the
How did you compile the assembly code? The compilation has to be done with
the Remoteproc and linker files.
Remoteproc will look for certain code in the firmwares, and if it is not
there, nothing will happen.
On Friday, November 18, 2016 at 10:06:07 AM UTC-5, Zach B wrote:
>
> In trying to
In trying to test my code for the PRUs is there a good way to check and see
if binary is being loaded into the PRU properly and check whether or not it
is executing. I have a simple LED circuit running some basic blink code but
nothing seems to be occurring. Also with everything activated, the
btw, Russell's unstable-devel branch has a few more patches over xobs's repo:
http://git.arm.linux.org.uk/cgit/xf86-video-armada.git/?h=unstable-devel
Regards,
On Fri, Nov 18, 2016 at 7:45 AM, Julien Boulnois wrote:
> Yes, I agree. xorg armada driver is very confusing,
In trying to test my code for the PRUs is there a good way to check and see
if binary is being loaded into the PRU properly and check whether or not it
is executing. I have a simple LED circuit running some basic blink code but
nothing seems to be occurring. Also with everything activated, the
Greg,
Thanks for the link I to the motor controller. I actually ended up figuring
out late last night what was preventing remote_proc from running properly.
I had the line
dtb=am335x-boneblack-overlay.dtb
uncommented in my "uEnv.txt" file. I guess that device overlay prevented
the remote_proc
i want to control switching between utility source and generator source. is
it possible with beagle?
--
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
Yes, I agree. xorg armada driver is very confusing, after a close up
looking it seems that libdrm-etnaviv is not used at all and a sort of
backport of it is integrated directly in armada (
https://github.com/xobs/xserver-xorg-video-armada/blob/novena-r2/etnaviv/etnadrm.c).
Optizations is not used
You are loading down the boot pins with your design. .
http://www.elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Pin_Usage
Gerald
On Fri, Nov 18, 2016 at 5:21 AM, sevgi aydın
wrote:
>
> Dear beaglebone black users;
>
> I am working to on convert RGB to
Dear beaglebone black users;
I am working to on convert RGB to MIPI ..
I design PCB for beaglebone black .
But when I connected PCB of convert RGB to MIPI, Beagleboneblack board is
not work . User leds on beaglrbone board is not emitting..
I used to SSD2828 integrated for convert RGB to
Zach I think you mentioned you were interested in motor controllers:
http://www.ti.com/lit/ug/tidubj6/tidubj6.pdf
I just finished the Coursera course "Control of Mobile Robots".
The course has some info on a Beaglebone based robot.
I want to implement some, but probably not all. I'm going to be
Pretty much sounds correct. Did you create a file
/etc/modprobe.d/pruss-blacklist.conf
and the single line in this file is:
blacklist uio_pruss
Can you paste in your dts file change? Here is what I have:
/* pruss: pick one: */
/*
* /etc/modprobe.d/pruss-blacklist.conf
*
* blacklist
Hm, still not working. I have a MLO-file which works smoothly out of a
FatFS partition but when I try to write it to the MMC directly with
sudo dd if=./MLO of=/dev/mmcblk1 count=1 seek=1 bs=128k
and/or
sudo dd if=./MLO of=/dev/mmcblk1 count=1 bs=128k
the board does not boot afterwards,
23 matches
Mail list logo