[beagleboard] the way to set MMC mode(8-bit transfer) and 384Mbps at BBBW

2021-02-17 Thread ha ppay
Hi Everyone. I'm collecting information to get even faster boot times, I have 2 questions. It is written that it is possible to boot from MMC (8bit mode) (18.1.1 MMCHS Features) using MMC mode with TRM of am335x. - Clock support -96-MHz functional clock source input -up to 384Mbit/sec

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Dennis Lee Bieber
On Wed, 17 Feb 2021 10:45:49 -0800 (PST), in gmane.comp.hardware.beagleboard.user Walter Cromer wrote: >You are correct that this application does not need to know the actual real >time but only the relative (elapsed) time since the subroutine began. I'm >familiar with clock_gettime but

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Mark A. Yoder
I fired up the Beagle at home it the PRU works out of the box. What do you get running *ls /dev/remoteproc* I get: *ls -ls /dev/remoteproc* total 0 0 lrwxrwxrwx 1 root root 33 Feb 17 17:26 pruss-core0 -> /sys/class/remoteproc/remoteproc1 0 lrwxrwxrwx 1 root root 33 Feb 17 17:26 pruss-core1 ->

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Walter Cromer
I'll get this one onto an SD card and give it a try. If I can just get this configured I think I can make quick work of this problem! On Wednesday, February 17, 2021 at 3:47:04 PM UTC-5 Mark A. Yoder wrote: > Good point, it should work I'm running a newer test image[1], but I > took

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Mark A. Yoder
Good point, it should work I'm running a newer test image[1], but I took my Beagle home so I can't do a quick check on it until later. --Mark [1]https://rcn-ee.com/rootfs/bb.org/testing/2021-02-15/buster-iot/bone-debian-10.8-iot-armhf-2021-02-15-4gb.img.xz On Wednesday, February 17,

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Walter Cromer
I asked because the ones on the page @ the link are older than the one I have installed. On Wednesday, February 17, 2021 at 2:30:58 PM UTC-5 Mark A. Yoder wrote: > On newer versions of the SD card image /var/lib/cloud9 is a git repo which > you can do a git pull to update. Your version is

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Walter Cromer
So you are saying that this version is too old? Linux beaglebone 4.14.108-ti-r137 #1stretch SMP PREEMPT *Tue Aug 25 01:48:39 UTC 2020* armv7l GNU/Linux On Wednesday, February 17, 2021 at 2:30:58 PM UTC-5 Mark A. Yoder wrote: > On newer versions of the SD card image /var/lib/cloud9 is a git

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Mark A. Yoder
On newer versions of the SD card image /var/lib/cloud9 is a git repo which you can do a git pull to update. Your version is too old. Follow the instructions at: https://markayoder.github.io/PRUCookbook/02start/start.html#_installing_the_latest_os_on_your_bone to download and install an

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Walter Cromer
Mark, git pull on /var/lib/cloud9 fails with 'fatal: Not a git repository (or any of the parent directories): .git I'm such a neophyte on git. What do I need to do? And, what do you mean by updating to a new version of the SD card? The OS is booting from the SD card and the version.sh

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Mark A. Yoder
I suggest updating to a new version of the SD card. It looks like the PRUs are getting started at boot time, but the path isn't setup right. I think we setup some links so the path* /dev/remoteproc/pruss-core0/state *points to the right place. You could also try: *cd */var/lib/cloud9 *git*

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Walter Cromer
Mark, I got the latest PRUCookbook downloaded and when trying to make the hello.pru0.c program in 1.6, I got this error. *debian@beaglebone:/var/lib/cloud9/PRUCookbook/docs/02start/code$ make TARGET=hello.pru0* */var/lib/cloud9/common/Makefile:29:

Re: [beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Walter Cromer
You are correct that this application does not need to know the actual real time but only the relative (elapsed) time since the subroutine began. I'm familiar with clock_gettime but didn't think it could give me subsecond information. I'll explore it! Thanks,! Walter On Wednesday, February

Re: [beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Michele Xiloyannis
Hi Walter, I don't think you need an RTC for relative time. clock_gettime should do the job (https://linux.die.net/man/3/clock_gettime) There are also more intuitive ways to manipulate timespec structs in the RCL (http://strawsondesign.com/docs/librobotcontrol/group__time.html). Best, Michele

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Walter Cromer
I really don't need ns. The valve 'on time' is going to be in the range of 500 ms to 2 seconds probably. I will review the PRUCookbook! Thanks! Walter On Wednesday, February 17, 2021 at 10:10:53 AM UTC-5 Mark A. Yoder wrote: > The PRUs can give you 10's of ns timing, which is more than

[beagleboard] Re: Best way to get elapsed milliseconds

2021-02-17 Thread Mark A. Yoder
The PRUs can give you 10's of ns timing, which is more than good enough for milliseconds, but might be over kill. I'd think using C on the ARM processor should be fast enough. I'd use gpiod[1]. If you really want the ns timing of the PRUs, check out the PRU Cookbook[2] --Mark [1]