[beagleboard] No free space on SD card partition after writing 2016-06-05

bone-debian-8.5-lxqt-4gb-armhf-2016-06-05-4gb.img.xz leaves no free space on the partition it creates when written to an SD card. I've done it using both dd and Etcher, on two different brands of 8GB cards. Its not a show-stopper since grow-partition.sh still works after the Beaglebone has boo

[beagleboard] Re: trouble with image bone-debian-8.5 / 2016-06-05

Why all these changes to /sys/devices tree? Its ugly and will remain ugly no matter what they do with the names, but these changes break existing code and documentation to what benefit? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are sub

Re: [beagleboard] Re: Release date update?

Hi Gerald, Any news on the X15? I noticed the "ON HOLD" at http://www.elinux.org/Beagleboard:BeagleBoard-X15 (last updated on 26 May). With regards, Patrick Tan -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google G

[beagleboard] 4DCAPE-43 cape frame rate

What frame rate can the Beaglebone Black manage through the 4D Systems 4DCAPE-43 display? Can it do smooth full colour, full size video? I'd like to either stream video off the SD card or load short clips into memory and then loop them. Digging through forum archives and datasheets doesn't find

Re: [beagleboard] Re: Release date update?

If there is any news to report, I will update the Wiki. So, assume that the information on the Wiki is the latest status. Gerald On Mon, Jun 20, 2016 at 7:52 AM, wrote: > Hi Gerald, > > Any news on the X15? > I noticed the "ON HOLD" at > http://www.elinux.org/Beagleboard:BeagleBoard-X15 (last

Re: [beagleboard] 4DCAPE-43 cape frame rate

On Mon, Jun 20, 2016 at 1:40 AM, wrote: > What frame rate can the Beaglebone Black manage through the 4D Systems > 4DCAPE-43 display? > > Can it do smooth full colour, full size video? I'd like to either stream > video off the SD card or load short clips into memory and then loop them. It's only

[beagleboard] Re: No free space on SD card partition after writing 2016-06-05

If you have access to a Linux desktop, you can take the card after you write it, then plug it in to the Linux desktop and use Gparted to expand the partition size to the limit of the card, before you ever insert it into the BBB. That way, you have full card memory available on the initial boot.

[beagleboard] codesys available for beaglebone

Just came along this one: http://store.codesys.com/codesys-control-for-beaglebone-sl.html Codesys is an implementation of iec 1131, language(s) & runtime for real-time plc applications. It's is used in industrial automation. E.g. Wago, Beckhoff en Schneider do sell plc's with codesys runtime &

Re: [beagleboard] disable edid (hdmi, rgb video output)

Hello, thanks again. so today i have try now with a HDMI TFT 1280x800 (EDID compatible) to force the Resolution to 800x480. For this, i have try to edit the uEnv.txt file: root@beaglebone:/media/root/rootfs/boot# vi uEnv.txt *then i have edit the cmdline as follow, but unfortunately the resolut

Re: [beagleboard] disable edid (hdmi, rgb video output)

On 6/20/2016 8:36 AM, epi kao wrote: > Hello, thanks again. > > so today i have try now with a HDMI TFT 1280x800 (EDID compatible) to force > the > Resolution to 800x480. > > For this, i have try to edit the uEnv.txt file: > root@beaglebone:/media/root/rootfs/boot# vi uEnv.txt > > *then i have

Re: [beagleboard] disable edid (hdmi, rgb video output)

so what i receive: root@beaglebone:/# cat /proc/cmdline console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc coherent_pool=1M quiet cape_universal=enable BTW, i have read following code on a other side in the internet: kms_force_mode=video=HDMI-A-1:800x480M@6

Re: [beagleboard] disable edid (hdmi, rgb video output)

On Mon, Jun 20, 2016 at 9:00 AM, epi kao wrote: > so what i receive: > > root@beaglebone:/# cat /proc/cmdline > > console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4 > rootwait fixrtc coherent_pool=1M quiet cape_universal=enable > > BTW, i have read following code on a other si

Re: [beagleboard] disable edid (hdmi, rgb video output)

*>remove the "#" and set the video parameters you need.* still not working... Am Montag, 20. Juni 2016 16:04:32 UTC+2 schrieb RobertCNelson: > > On Mon, Jun 20, 2016 at 9:00 AM, epi kao > > wrote: > > so what i receive: > > > > root@beaglebone:/# cat /proc/cmdline > > > > console=tty0 conso

Re: [beagleboard] disable edid (hdmi, rgb video output)

On 6/20/2016 9:25 AM, epi kao wrote: > />remove the "#" and set the video parameters you need./ > > still not working... Provide your uEnv.txt, /etc/dogtag, and /proc/cmdline and we might be able to make a suggestion for what to try next. Otherwise, we're just guessing. -- Charles Steinkuehler

Re: [beagleboard] disable edid (hdmi, rgb video output)

On Mon, Jun 20, 2016 at 9:25 AM, epi kao wrote: >>remove the "#" and set the video parameters you need. > > still not working... okay, post your full, /boot/uEnv.txt and what rootfs is this? cat /etc/dogtag Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://be

Re: [beagleboard] disable edid (hdmi, rgb video output)

as requested (it seems that uEnv.txt has different directorys?, anyway I have changed uEnv.txt on the directory /media/root/rootfs/boot): root@beaglebone:/# cat /etc/dogtag BeagleBoard.org Debian Image 2016-01-24 root@beaglebone:/# cat /proc/cmdline console=tty0 console=ttyO0,115200n8 root=/dev/

Re: [beagleboard] disable edid (hdmi, rgb video output)

There's two uEnv.txt's for compatibility with old eMMC's.. /uEnv.txt -> /boot/uEnv.txt HOWEVER, /uEnv.txt doesn't have the features of /boot/uEnv.txt So make sure your uEnv.txt is found in /boot/uEnv.txt Otherwise your /boot/uEnv.txt looks fine.. Regards On Mon, Jun 20, 2016 at 9:40 AM, epi k

Re: [beagleboard] disable edid (hdmi, rgb video output)

ok. now please find below the uEnv.txt directly from /boot (not from rootfs..)! but it don't work although #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_3.0 uname_r=4.1.15-ti-rt-r43 #uuid= #dtb= ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..) ##Beag

Re: [beagleboard] disable edid (hdmi, rgb video output)

On Mon, Jun 20, 2016 at 9:57 AM, epi kao wrote: > ok. now please find below the uEnv.txt directly from /boot (not from > rootfs..)! but it don't work although > > #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_3.0 > > uname_r=4.1.15-ti-rt-r43 > #uuid= > #dtb= > > ##BeagleBone Bla

Re: [beagleboard] disable edid (hdmi, rgb video output)

ok. thank, it works :-) failure was two command line, and the cmdline from the uEnv.txt at /boot was still wrong, below the correct: #In the event of edid real failures, uncomment this next line: cmdline=coherent_pool=1M quiet video=HDMI-A-1:800x480M@60e cape_universal=disable init=/lib/systemd

Re: [beagleboard] disable edid (hdmi, rgb video output)

On 6/20/2016 10:17 AM, epi kao wrote: > > so now i am really interested if resolution like 1920x720 or 320x240 also > works... maybe anyone still know this? You should be able to craft any resolution within the frequency range of the AM335x LCD pixel clock. Very low resolutions (like 320x240) m

Re: [beagleboard] disable edid (hdmi, rgb video output)

it seems that 320x240 is not working? what is the reason? it's to low? and how can i access now this resolution? thanks Am Montag, 20. Juni 2016 17:17:25 UTC+2 schrieb epi kao: > > ok. thank, it works :-) failure was two command line, and the cmdline > from the uEnv.txt at /boot was still wrong

Re: [beagleboard] trouble with image bone-debian-8.5 / 2016-06-05

What was ugly was the original board files with duplicate code in the kernel source for each platform. Anyway, why is this ugly? It is simply a device address and a label. The driver needs this information, so you can either hard code it (not a good idea because it leads to duplicate code) or yo

[beagleboard] Re: BBB boot from SPI flash

I just tried the latest u-boot 2016.05 and it worked this time without any difficulty. I just had to edit configs/am335x_boneblack_defconfig and replace option CONFIG_SYS_EXTRA_OPTIONS with CONFIG_SYS_EXTRA_OPTIONS="SPI_BOOT" and add line CONFIG_SPI_FLASH_STMICRO=y (because my SPI flash chip

Re: [beagleboard] trouble with image bone-debian-8.5 / 2016-06-05

Am Montag, 20. Juni 2016 18:09:36 UTC+2 schrieb john3909: > > It is simply a device address and a label. The driver needs this > information, so you can either hard code it (not a good idea because it > leads to duplicate code) or you can define it in the device tree. Same > thing for gpio numb

Re: [beagleboard] trouble with image bone-debian-8.5 / 2016-06-05

Because Devicetree is new and there is an effort to achieve consistency between all architectures. Remember, devicetree started on the PowerPC platform and it was only when Linus complained about the code duplication and conflicts between ARM platforms that Devicetree was adopted by the ARM comm

Re: [beagleboard] trouble with image bone-debian-8.5 / 2016-06-05

On Mon, Jun 20, 2016 at 12:10 PM, TJF wrote: > > Am Montag, 20. Juni 2016 18:09:36 UTC+2 schrieb john3909: >> >> It is simply a device address and a label. The driver needs this >> information, so you can either hard code it (not a good idea because it >> leads to duplicate code) or you can define

[beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

I'm looking to write a simple app for BBB. When started from the command line, it would set up the ADC in continuous mode and read ~1 M samples from e.g. AN0 into memory. After the capture is complete, it would write the data to a file and exit. Ideally, it would run at the hardware limit of

[beagleboard] Capture analog input at near maximum sample rate?

I'm looking to write a simple app for BBB. When started from the command line, it would set up the ADC in continuous mode and read ~1 M samples from e.g. AN0 into memory. After the capture is complete, it would write the data to a file and exit. Ideally, it would run at the hardware limit of

Re: [beagleboard] disable edid (hdmi, rgb video output)

so because cmdline does not work with qvga i must study the variant with following link: https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BONE-LCD7-01-00A1.dts#L230 does anyone know, if I can see also a result on the hdmi-output with that, or does I disable the hdmi-output w

Re: [beagleboard] Capture analog input at near maximum sample rate?

the best woud be the PRU because you can store the data in the share memory. That is the fastest way. you can stop the acquisition whenever you want or let it go back at the beginning of your memory and go on. Le lun. 20 juin 2016 à 21:29, a écrit : > I'm looking to write a simple app for BBB.

Re: [beagleboard] Capture analog input at near maximum sample rate?

on the am355x processor the ADC used is 12 bit SAR ADC with a sample rate of 200 KSPS any faster and you will need an external ADC On 6/20/2016 12:53 PM, Micka wrote: > the best woud be the PRU because you can store the data in the share > memory. That is the fastest way. > > you can stop the ac

Re: [beagleboard] Re: Is there Beaglebone Black Guide for LED diagnostics?

Hey gerald, and william. I bought the serial cable and I got this: can you figure out what's wrong here? On Thursday, June

Re: [beagleboard] Re: Is there Beaglebone Black Guide for LED diagnostics?

On Mon, Jun 20, 2016 at 3:14 PM, wrote: > Hey gerald, and william. I bought the serial cable and I got this: > > > > > > can y

Re: [beagleboard] Re: Is there Beaglebone Black Guide for LED diagnostics?

no, I think the beaglebone black is connected via the serial port cable, not the usb. I want to connect to the BBB through the USB. On Monday, June 20, 2016 at 3:19:21 PM UTC-5, RobertCNelson wrote: > > > > On Mon, Jun 20, 2016 at 3:14 PM, > wrote: > >> Hey gerald, and william. I bought the seri

Re: [beagleboard] Capture analog input at near maximum sample rate?

The ADC block is rated for 200Ksps max. The easiest thing to do is a quick char device driver that configure the ADC with the right settling times and have the DMA engine gather the data. Once you have that all you need to do is cat /dev/foobar > file. The block doesn't run from 24MHz. It is di

Re: [beagleboard] Re: Is there Beaglebone Black Guide for LED diagnostics?

On Mon, Jun 20, 2016 at 3:23 PM, wrote: > no, I think the beaglebone black is connected via the serial port cable, > not the usb. I want to connect to the BBB through the USB. > So, "YOU" need to configure the usb port to do that. It's not a hardware default. It's done in software, using the g

Re: [beagleboard] Re: Is there Beaglebone Black Guide for LED diagnostics?

perfect, it worked, thanks! :) On Monday, June 20, 2016 at 3:28:38 PM UTC-5, RobertCNelson wrote: > > > > On Mon, Jun 20, 2016 at 3:23 PM, > wrote: > >> no, I think the beaglebone black is connected via the serial port cable, >> not the usb. I want to connect to the BBB through the USB. >> > > S

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

I have been working on adding DMA to the ADC driver, but it currently it throws overflow errors before DMA starts. The DMA should trigger when the ADC fifo reaches a predefined threshold, but for some reason there is a delay before DMA triggers. The ADC driver uses the IIO framework and I’m usin

Re: [beagleboard] Capture analog input at near maximum sample rate?

I have been working on adding DMA to the ADC driver, but it currently it throws overflow errors before DMA starts. The DMA should trigger when the ADC fifo reaches a predefined threshold, but for some reason there is a delay before DMA triggers. The ADC driver uses the IIO framework and I’m usin

Re: [beagleboard] Capture analog input at near maximum sample rate?

Thanks for the reply. I'm looking at the AM335x Technical Reference Manual, downloaded from http://phytec.com/wiki/images/7/72/AM335x_techincal_reference_manual.pdf Section 12.2.2 reads (in part): Clock Signal Max Freq adc_clk24 MHz ADC clock(typ) Section12.3.

Re: [beagleboard] apt-get -y install ntp gives error Failed to fetch http://security...

Thanks Robert. Worked like a charm. Did have to also install libopts25 with apt-get -y install libopts25 On Thursday, June 9, 2016 at 4:10:55 PM UTC-7, RobertCNelson wrote: > > On Thu, Jun 9, 2016 at 5:47 PM, Matt99eo > wrote: > > Hi, > > > > I am trying to reinstall ntp on some BBB runnin

Re: [beagleboard] Capture analog input at near maximum sample rate?

> the best woud be the PRU because you can store the data in the share memory. Do you mean the 12KB data memory? As I understand it, it's only shared between PRUs, not directly with the CPU. Moving data from there to the CPU would require DMA, as 'programmed' access would not keep up with 1.6

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

The ADC module is a 200ksps SAR module . . .You're only going to be able to sample 200k samples per second . . . Additionally you can use: 1. PRUs ( Programmable Real-time Units ) 2. IIO ( industrial IO ) 3. /dev/mem/ + mmap() To read 200ksps. Personally, I've proven that /dev/mem + m

Re: [beagleboard] Capture analog input at near maximum sample rate?

http://lmgtfy.com/?q=AM335c+ADC+module -> http://processors.wiki.ti.com/index.php/AM335x_ADC_Driver's_Guide#Introduction An analog-to-digital converter (abbreviated ADC) is a device that uses > sampling to convert a continuous quantity to a discrete time representation > in digital form. > > The T

Re: [beagleboard] Capture analog input at near maximum sample rate?

> > The ADC block is rated for 200Ksps max. The easiest thing to do is a quick > char device driver that configure the ADC with the right settling times and > have the DMA engine gather the data. Once you have that all you need to do > is > cat /dev/foobar > file. > No point. IIO is already includ

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

You should read the info Steward provided. There is a conflict in the AM3358 datasheet because it does say max 200ksps, but in the register settings, it does show you can configure the ADC for 1.6msps. There are discussions on E2E about this issue and no one from TI has said you cannot achieve 1

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

Wow, I think that /dev/mem + mmap() is the easy solution! Many thanks. But can you please confirm that by "200ksps for 7 channel simultaneously" you mean that each of the 7 channels is being sampled 200k times per second. If so, that's 1.4M captures per second, enough for my project. > But CP

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

um no the 7 channels go into a analog mux and you can only have one selected input at a time. On 6/20/2016 3:35 PM, snelson.st...@gmail.com wrote: > Wow, I think that /dev/mem + mmap() is the easy solution! Many thanks. > > But can you please confirm that by "200ksps for 7 channel > simultaneousl

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

You don’t read the IIO driver that way. You read the samples from /dev/iio:device0. You can modify the open delay, sample delay, in the devicetree, but because the current driver uses interrupts, the cpu utilization increases as you increase the sample rate. Also, the convertor is specified as

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

http://e2e.ti.com/support/arm/sitara_arm/f/791/p/382609/1349287#1349287 Regards, John > On Jun 20, 2016, at 12:00 PM, Stewart wrote: > > I'm looking to write a simple app for BBB. When started from the command > lin

[beagleboard] Re: No free space on SD card partition after writing 2016-06-05

I know that, that is why I said its not a show-stopper, and Windows users can still boot the card and run grow_partition.sh, but the previous testing lxqt images were apparently sized to match the 4GB eMMC. If there is a reason for it, (new slightly smaller eMMC chip to save a few pennies on so

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

I'm well aware of the analog mux and fully understand that if N channels are being sampled, the maximum sample rate for each channel is reduced by a factor of N. However, Mr. Hermans, who clearly knows what he is talking about, stated "I've proven that /dev/mem + mmap() can work for reading 200

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

> > However, Mr. Hermans, who clearly knows what he is talking about, stated > "I've proven that /dev/mem + mmap() can work for reading 200ksps for 7 > channel simultaneously." > It's reasonable to assume that he would not have included the "7 channel > simultaneously" part unless it was somehow re

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

http://www.ti.com/lit/ds/sprs717j/sprs717j.pdf Page 3: – 12-Bit Successive Approximation Register (SAR) ADC • 200K Samples per Second • Input can be Selected from any of the Eight Analog *Inputs Multiplexed* *Through an 8:1 Analog Switch* • Can be Configured to Operate as a 4-Wire, 5-Wire, or 8-W

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

The ADC uses a sequencer and you can only read the sample when the samples are complete. The sequencer provides an interrupt or triggers a DMA transfer when the EOC (End of Conversion) is achieved. Since you cannot service interrupts in userspace, you will have to poll repeatedly to wait for the

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

> You're not understanding correctly . . . the ADC module is rated for 200ksps only. Not 1M, not 2M, 200ksps. So your "7 channel simultaneously" comment had nothing to do with the total sample rate, but merely indicates that this 200 KSPS rate was achieved even though some additional overhead (

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

Stop second guessing what I mean by what I type, and just read that dammed datasheet. I even pasted a quote of the relevant information, and it's quite clear. On Mon, Jun 20, 2016 at 5:06 PM, wrote: > > You're not understanding correctly . . . the ADC module is rated for > 200ksps only. Not 1M,

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

Currently the ADC driver is configured for 16x oversample, Open Delay = 152 cycles and Sample Delay = 1 cycles. time in us for processing a single channel, calculated as follows: num cycles = open delay + (sample delay + conv time) * averaging num cycles: 152 + (1 + 13) * 16 = 376 clock f

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

Thanks for the link. Given the recent update to the data sheet, it seems pretty likely that the 200 kSPS total sample rate limit is correct, even though that conflicts with both the (older) TRM and the comments in 2014 by Biser Gatchev-XID . So, it appears t

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

Well, I think that is still to be determined if the ADC can sample higher than 200ksps and that is why I’m adding DMA to this driver. But in any case, why not use a higher speed ADC connected via SPI or McASP? You can purchase boards that sample at a higher rate and connect those to the BBB. R

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

So going back to what I said earlier. When using /dev/mem + mmap() yes, I was (actually ) reading more than 200ksps from 7 channels simultaneously. For a total of somewhere around 1.5Msps BUT Only 1 sample in ~8-9 per second was valid. So what I proved is possible is comp

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

That is a totally different issue. You were reading the same sample over and over again as opposed to increasing the sample rate by changing the clock divider, open delay, sample delay, etc. In any case, at 200ksps, each sample occurs every 5uS. How is a user space app going to process samples a

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

The ADC is a SAR ADC. Overclocking it is likely to have side effects on the analog end of things which will reduce accuracy. Ignoring that it is a very bad idea to keep doing things in userland: On Monday, June 20, 2016 18:06:09 John Syne wrote: > That is a totally different issue. You were read

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

When you're writing directly to memory addresses ( registers ), you can't tell me what is, and what isn't. *This* is exactly what the PRU does when accessing peripherals modules. But, you'd be surprised what you can accomplish from userland when you pay close attention to what you should *not* do

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

You make a very good point and we have no idea what the ADC front end bandwidth is. You would think that TI would add some provisions in the ADC setup that can be whatever you want as long as you do not exceed 200ksps. The 200ksps I believe comes from a setting where clock divider = 8, open dela

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

The latency in the RT kernel is only relevant for interrupts (preemption). The scheduler will still swap out user space apps to service background tasks and that is the same as the regular kernel. In any case, the ADC uses a sequencer to do the samples and those samples get stored in the fifo, s

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

I never shared my /dev/mem + mmap() code with the group / publicly. For what should be obvious reasons. I fact I do not think I shared it with anyone. My reasoning is that if someone can figure out how to do this on their own, then they probably earned the right, and with that comes knowledge and r

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

I seemed to have lost a post here that I made. *Somehow* . . . Anyway, I never shared my /dev/mem + mmap() code with anyone, and I will never post it on this group. So no one here would know what I've done in code concerning that. My reason is simple. In order to use code of that nature, you need

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

BY the way, when I say read from the ADC buffer. I do not mean that piece of garbage /dev/iio:device0. I mean the ADC hardware buffer. FIFO0DATA described on page 1095 of the TRM. On Mon, Jun 20, 2016 at 7:27 PM, William Hermans wrote: > I seemed to have lost a post here that I made. *Somehow* .

Re: [beagleboard] Re: No free space on SD card partition after writing 2016-06-05

On Mon, Jun 20, 2016 at 6:05 PM, Wally Bkg wrote: > I know that, that is why I said its not a show-stopper, and Windows users can > still boot the card and run grow_partition.sh, but the previous testing lxqt > images were apparently sized to match the 4GB eMMC. > > If there is a reason for it,

[beagleboard] Re: Power up initialisation failure/PMIC reset

I played around a bit with this and it is quite strange: When I reset the board by pressing the reset-button on BBG, on next boot-up the Ethernet PHY is working smoothly. When I do the same programmatically by invoking a cold reset on SoC (by writing a 0x02 into reset register 0x44E00F00, the P

Re: [beagleboard] Capture one Analog channel in continuous mode at near maximum speed?

Ah, I thought you were talking about this solutions: http://www.embeddedhobbyist.com/2015/10/beaglebone-black-adc/ Otherwise, you would have to replicate much of the ADC driver in userspace and then loop, waiting for FIFO0COUNT>0,