Hacker Newsnew | past | comments | ask | show | jobs | submit | mycroftcomptro's commentslogin

It's pretty easy to do with one core, too - I would guess that the author didn't use interrupts or peripherals because they were writing about MCUs in general rather than a specific chipset. The K210 they used as an example is actually targeted towards ML applications.

Most chips will have some sort of PWM or advanced timer peripheral that can generate waveforms on a pin without direct CPU intervention. You write to registers to change the frequency, duty cycle, etc.

Many chips also include asynchronous DACs, but they're usually too low-resolution for high-fidelity audio.

Most microcontrollers also include some form of DMA, which can shuttle data between peripherals and memory without CPU intervention. You can also user timer peripherals to trigger DMA transfers, which lets you send buffered data to a DAC on a KHz schedule while the CPU does other things.

And of course, you can usually use timer peripherals to periodically interrupt the main thread when you don't want to wait in a busy-loop.


Maybe testing? Companies like Browserstack offer that sort of thing as their core business.

Say that you just made a big frontend change to your website. Before you release it, you can open it on the last 10 major versions of desktop and mobile Chrome/Firefox/Safari/etc. Any rendering failures that you find are the sort of bugs that can be very frustrating to debug from occasional user contacts.

But it can be tricky to automate the detection of visual bugs. And what if you have to make a few clicks and execute some javascript to get to the screen that you want to test?

Anyways, that's one use of browsers-as-a-service.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: