Re: [beagleboard] TI PRU_ADC_onChip example

2021-05-04 Thread 'Mark Lazarewicz' via BeagleBoard
Hi Jeff Hope all is well good to here from you  Yes saw that I think that's why someone told Walter there's no way to get code into PRU with CCS. It's obvious that the poster was using CCS fine to debug PRU code it's only the examples with RPMSg where JTAG is blocked. This to me means  the ARM

Re: [beagleboard] TI PRU_ADC_onChip example

2021-05-04 Thread Jeff Andich
Very informative thread guys! Interesting article in E2E on accessing shared memory and RPMsg.. This statement by Jason Reader “…Also, if you are testing an RPMsg project you will need to use the pruss_remoteproc Linux module to load the code and not CCS over JTAG. …” could be a clue as to the

Re: [beagleboard] versioning beaglebone images with OSTree

2021-05-04 Thread Robert Nelson
On Tue, May 4, 2021 at 5:28 PM John Allwine wrote: > > Where is the source code for what u-boot runs by default on the Beaglebone > images? I see some references to patches that I assume are applied to u-boot > on the Beaglebone: >

Re: [beagleboard] versioning beaglebone images with OSTree

2021-05-04 Thread John Allwine
Where is the source code for what u-boot runs by default on the Beaglebone images? I see some references to patches that I assume are applied to u-boot on the Beaglebone: https://github.com/beagleboard/image-builder/blob/master/target/chroot/beagleboard.org-buster.sh#L276-L291 Is there

Re: [beagleboard] TI PRU_ADC_onChip example

2021-05-04 Thread 'Mark Lazarewicz' via BeagleBoard
Cheng Yes difference between the two Linux is why the E2E wants to know which Linux you running. Walter Here is a shared RAM CCS JTAG PRU discussion but as Cheng stated the user is using SDK Linux. Perhaps the code examples will help you solve your freeze up. It's possible ARM Linux is using

[beagleboard] Re: Beaglebone Ai overheating

2021-05-04 Thread Andy Panda
Hi all, a bit late but still. I'm using SUNON 25x25 MagLev fans, which matches the radiator (holes) perfectly fine. for the heavy load things I'm using MF25150V2-1000U-A99, it is quite tall 15mm, but the CPU stays cool all the time. The good thing is the noise level - it is unnoticeable. For

Re: [beagleboard] Placing integer arrays in PRU Shared memory

2021-05-04 Thread Vinicius Juvinski
Sorry my mistake, Your code is running inside the pru right? I was mistaking with host manipulating pru shared memory - in this case there is an offset on the host side. I You are mentioning when run your code is freezing, could you try to decrease the memory to try some kind of debug(pru

Re: [beagleboard] Placing integer arrays in PRU Shared memory

2021-05-04 Thread Walter Cromer
Vinicius.. Thanks for looking from your phone! Are you saying that SHARE_MEM is incorrect? I took that directly from Molloy's examples in Exploring BeagleBone. Maybe it looks incorrect on your phone? Walter On Tuesday, May 4, 2021 at 1:09:35 PM UTC-4 vinicius...@gmail.com wrote: > Hi

Re: [beagleboard] TI PRU_ADC_onChip example

2021-05-04 Thread Walter Cromer
I am glad to have helped a little bit. Stick with it. When it clicks and you start really moving forward I think you'll be pleased. Can you share the changes to the Makefile that you made? I'm curious if it might help me. Right now I am reading the ADC every 2.7ms. I'm reading three

Re: [beagleboard] Placing integer arrays in PRU Shared memory

2021-05-04 Thread Vinicius Juvinski
Hi Walter, I’m on the cellphone and that is a little hard to read your code? But I did find the offset of the pru memory , because you need allocate the memory inside the pru memory address and you is allocating at the 1000 address Sent from my iPhone > Em 4 de mai. de 2021, à(s) 13:16,

[beagleboard] Placing integer arrays in PRU Shared memory

2021-05-04 Thread Walter Cromer
I'm on a BBB Wireless running Linux beaglebone 4.19.94-ti-r61 #1buster SMP PREEMPT Wed Mar 31 15:23:20 UTC 2021 armv7l GNU/Linux The version.sh output is at the end of this post. I need to put readings from two analog inputs into two arrays so I can do some calculations on them. Basically,

Re: [beagleboard] TI PRU_ADC_onChip example

2021-05-04 Thread Cheng Chen
Hi Mark, Thanks a lot for the detailed explanation regarding the SDK. I actually made the examples work in the end. Like you said, there is difference between SDK Linux and Debian Linux. My approach is similar to what Walter refers. My understanding now is examples from TI needs to be

Re: [beagleboard] TI PRU_ADC_onChip example

2021-05-04 Thread Cheng Chen
Hi Walter, Thank you so much for the reply. I think my setup is exactly the same as what you have (win10 and BBB wireless). That really motivated me to see somebody else successfully run the system with the same setup. I actually made some preliminary progress after two nights brooding and I

Re: [beagleboard] Re: wl18xx warning - any resolution?

2021-05-04 Thread Walter Cromer
I'm getting this same message on a BBB Wireless now and I agree its annoying. Any suggestions to get this fixed would be greatly appreciated. I've recently upgraded and here's the output of version.sh debian@beaglebone:/var/lib/cloud9$ sudo /opt/scripts/tools/version.sh

Re: [beagleboard] TI PRU_ADC_onChip example

2021-05-04 Thread Walter Cromer
I haven't posted the question about this code to the E2E forum as I think it must have something to do with permissions. I don't know if they support Cloud9 on E2E. I haven't asked any questions specific to Cloud9. And, I don't do any kernel development. It's above me right now. I'm