Re: [beagleboard] debian testing: 2016-05-01

Robert, Do you have any tips to help this console image boot up faster ? Keep in mind I'm running sysv . . . On Fri, May 6, 2016 at 12:35 PM, Rick Mann wrote: > > > On May 6, 2016, at 08:31 , Robert Nelson > wrote: > > > > now fixed: > > > >

Re: [beagleboard] PRU and LCD display on one BBB

SO here, maybe you've seen this, maybe not. https://groups.google.com/forum/#!category-topic/beagleboard/newbies/u28ytaoNenU One thing that might help you understand how the PRU's can access the other peripherals, and even DDR3 memory, is if you understand how /dev/mem/ and mmap() work to do the

Re: [beagleboard] PRU and LCD display on one BBB

> > *Thanks for your extensive answers, that was precisely what i needed, and > could not find. Just to be sure - 1 PRU cycle is 5ns right? Not 5ms.I will > be building a simple car robot, just to get familiar with PRUs on BBB, than > to go to heavier tasks. So I am very thankful for your answer

Re: [beagleboard] Kinoma at the Embedded Linux Conference 2016

How is this different to Cloud9 IDE and bonescript? I took a brief look at their site, and I don’t see anything equivalent to LabView. All this could be achieved with Nodejs and the C/C++ Addon library to talk to I/O. The hardware with an old ARM processor and limited memory looks horrible.

Re: [beagleboard] PRU and LCD display on one BBB

Thanks for your extensive answers, that was precisely what i needed, and could not find. Just to be sure - 1 PRU cycle is 5ns right? Not 5ms. I will be building a simple car robot, just to get familiar with PRUs on BBB, than to go to heavier tasks. So I am very thankful for your answer :) it

Re: [beagleboard] PRU and LCD display on one BBB

"raming" = remaing I honestly think my keyboard is failing . . . On Fri, May 6, 2016 at 1:13 PM, William Hermans wrote: > Robert, >> >> What do you need or want to use the PRUs for ? These pins you're talking >> about are probably shared with the HDMI pins, but are not the

Re: [beagleboard] PRU and LCD display on one BBB

> > Robert, > > What do you need or want to use the PRUs for ? These pins you're talking > about are probably shared with the HDMI pins, but are not the only pins the > PRU have access to. These pins are probably the pins the single cycle(5ms) > access to > , where the PRU's can access any pin on

Re: [beagleboard] PRU and LCD display on one BBB

Robert, What do you need or want to use the PRUs for ? These pins you're talking about are probably shared with the HDMI pins, but are not the only pins the PRU have access to. These pins are probably the pins the single cycle(5ms) access to , where the PRU's can access any pin on the board, just

Re: [beagleboard] PRU and LCD display on one BBB

Decide what features you do not need, like LCD, Ethernet, etc, and redesign the board by removing those features, freeing up the pins to use them as PRU pins. Gerald On Fri, May 6, 2016 at 2:53 PM, Robert Jonathan Šimon wrote: > I have another Question on PRUs. It has 9

Re: [beagleboard] PRU and LCD display on one BBB

I have another Question on PRUs. It has 9 pins for first PRU and 15 pins for the second PRU (according to this schematic ). Is there any option to expand number of pins, which I cand use by the PRUs? Dne pátek 6. května 2016 18:25:14 UTC+2

Re: [beagleboard] debian testing: 2016-05-01

> On May 6, 2016, at 08:31 , Robert Nelson wrote: > > now fixed: > > sudo apt-get update ; sudo apt-get install bb-cape-overlays Handy, thanks! -- Rick Mann rm...@latencyzero.com -- For more options, visit http://beagleboard.org/discuss --- You received this

Re: [beagleboard] Any difference for PIN9.15 (GPIO1_16) on new BBB

You can just do a git diff between the two releases. Search google on how to do this. There are probably a lot of changes, but concentrate on just the areas that would affect the issues you are concerned about. Regards, John > On May 5, 2016, at 1:11 PM, ht...@thingmagic.com wrote: > >

Re: [beagleboard] Programming without programming discussion

Wally, Also, in addition to the above. Your friend for example, and the Nodejs / node red discussion you've been having lately. If you friend is an Engineer, then learning the quick basic of javascript would take far less time than you've been discussing the problems you've been having on this

Re: [beagleboard] How to compile and and deploy code on dsp core

The DSP core is held in reset until the ARM core releases the DSP core. There are scripts in CCSV6 which will release the DSP core from reset to enable you to develop code for the DSP. Search on TI’s e2e.com for discussions on this topic. Regards, John > On May 4, 2016, at 11:48 PM,

Re: [beagleboard] Tools to debug the driver .

I completely agree with Vesa comments and I believe Lauterbach is the gold standard when it comes to Kernel Aware debugging. It is a difficult tool to learn but it is very powerful and has everything you need to get the job done. I have learned a lot just using the T32. Several years ago, I

[beagleboard] Programming without programming discussion

So wally I didn't want to step all over Jason's post by discussing this further, there. Also keep in mind that this is just a discussion. There is not right or wrong, only right or wrong for individuals. Or personal beliefs if you will. I won't disagree with what you say, but it ignores a few

Re: [beagleboard] Kinoma at the Embedded Linux Conference 2016

On Wednesday, May 4, 2016 at 11:17:43 PM UTC-5, William Hermans wrote: > > The concept I think is flawed. Programs like these that create > "programmers" without the ability to write code, or at minimum write decent > code. Flawed as in that the end result is a "programmer" that can not think

Re: [beagleboard] PRU and LCD display on one BBB

Ok. Great. Thanks for your time. Dne pátek 6. května 2016 18:21:47 UTC+2 William Hermans napsal(a): > > Better yet, I'll tell you what's better to do. Contact the manufacturer of > that screen, and ask what you're options are. > > If you're lucky, it could be possible to rewrite the device

Re: [beagleboard] Re: v4.4.x-ti changes (r25+)

> > *From there release notes, it needs wayland 1.9..* > > *jessie: 1.6.0* > > *stretch: 1.10 * > > *Not a lot depends on wayland, so i think it would be a safe backport.. ;)* > > *Regards,* Looking forward to reading that guide when and if ones made. And watching a demo video ;) On Fri, May 6,

Re: [beagleboard] PRU and LCD display on one BBB

Better yet, I'll tell you what's better to do. Contact the manufacturer of that screen, and ask what you're options are. If you're lucky, it could be possible to rewrite the device tree overlay file for that screen to work using alternate pins. If you're unlucky, you'll have to buy a different

Re: [beagleboard] PRU and LCD display on one BBB

Sorry, i send the wrong link. On this link , there is a picture, where you can see precisely which pin it is using Dne pátek 6. května 2016 18:12:17 UTC+2 William Hermans napsal(a): > > Ok, so, I do not

Re: [beagleboard] PRU and LCD display on one BBB

Ok, so, I do not have time to read through all the literature for that screen. Which pins does it use, what is the specific function of each pin, and what "protocol" does the screen use ? Is it one of those modified 9pin SPI + GPIO screens ? On Fri, May 6, 2016 at 9:02 AM, Robert Jonathan Šimon

Re: [beagleboard] Re: v4.4.x-ti changes (r25+)

On Thu, May 5, 2016 at 9:29 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 5/5/2016 4:27 PM, Robert Nelson wrote: > > > > The sgx modules for stretch were successfully built, the build farm is > currently > > working on all of them, so they should get pushed to the deb repo

Re: [beagleboard] PRU and LCD display on one BBB

I have this LCD screen and it user most of the second PRU pins and one of the first PRU unit. I am not sure, if this is problem or not. Dne pátek 6. května 2016 17:59:11 UTC+2 William Hermans napsal(a): > > *Hi,* >> *I am starting to

Re: [beagleboard] PRU and LCD display on one BBB

> > *Hi,* > *I am starting to play with PRU on BBB, and I noticed, that when I want to > use PRU on BBB and on the same time use LCD display through GPIO, i cant > (they use the same pins). Is there any workarounds?* > *Thanks a lot* I suppose that depends on how far you're willing to go, and

[beagleboard] PRU and LCD display on one BBB

Hi, I am starting to play with PRU on BBB, and I noticed, that when I want to use PRU on BBB and on the same time use LCD display through GPIO, i cant (they use the same pins). Is there any workarounds? Thanks a lot -- For more options, visit http://beagleboard.org/discuss --- You received

Re: [beagleboard] Re: debian testing: 2016-05-01

> > *now fixed:* > > > *sudo apt-get update ; sudo apt-get install bb-cape-overlays* > > *Regards,* > *-- * *Robert Nelson* *https://rcn-ee.com/ * Thanks Robert, but it was not my intention to create more work for you . . . after all the bb.org-overlay git is there and is

Re: [beagleboard] Re: debian testing: 2016-05-01

On Wed, May 4, 2016 at 6:29 PM, Robert Nelson wrote: > > > On Wed, May 4, 2016 at 6:22 PM, William Hermans wrote: > >> bone-debian-8.4-console-armhf-2016-05-01-2gb.img.xz >> >> Is the image I have. Supposed to be the standalone sdcard image. >> >>

Re: [beagleboard] debian testing: 2016-05-01

> > *I'll argue the opposite unless you have enough customer volume to have a > technical support department behind you.* > > *For most of my working career my product was generally a custom system > for a specific purpose and six instances would be a raging success, but the > systems were located

Re: [beagleboard] debian testing: 2016-05-01

On Friday, May 6, 2016 at 12:58:33 AM UTC-5, William Hermans wrote: > > william@beaglebone:~$ df -h / > Filesystem Size Used Avail Use% Mounted on > /dev/mmcblk0p1 1.7G 1004M 536M 66% / > > Thats also why I recommend to anyone who will listen. That they should > create two different