Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #31463
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: DSP like MCUs, or MCU like DSPs? |
| Date | 2022-12-22 22:31 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <87wn6ibpgq.fsf@nightsong.com> (permalink) |
| References | <c0dc506e-e26c-4629-8971-65432f8dcf15n@googlegroups.com> <to1mha$1cndn$1@dont-email.me> <to254j$1e5vh$1@dont-email.me> <f0da0c28-b449-499a-ba11-26800024118dn@googlegroups.com> |
Rick C <gnuarm.deletethisbit@gmail.com> writes: > I was just curious about what people have used for DSP applications, > but in particular if anyone had used one of the "crossover" parts. So > far, the answer has been "no". I've done some audio stuff on ordinary CPU's, that in an embedded system would probably go on something like a Cortex M4, if that's what you call a crossover part. The next thing after that is probably a GPU or FPGA, either of which contains a stupendous amount of parallel MAC's. As others have said, dedicated DSP's are now pretty niche. FPGA's may have displaced general purpose processors for some realtime applications as well, since you get low latency and deterministic timing without having to go crazy worrying about caches and interrupts. I didn't personally work on it, but spent a while studying a cryptography app that ran on the now ancient Motorola DSP 56000 series. The model number came from the architecture's 24 bit words and 56 bit MAC accumulator. The app wasn't particularly connected with realtime or with signal processing. Rather, the 24*24->56 MAC came in handy for high precision arithmetic used by the crypto algorithm.
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
DSP like MCUs, or MCU like DSPs? Rick C <gnuarm.deletethisbit@gmail.com> - 2022-12-21 09:30 -0800
Re: DSP like MCUs, or MCU like DSPs? David Brown <david.brown@hesbynett.no> - 2022-12-22 14:36 +0100
Re: DSP like MCUs, or MCU like DSPs? Grant Edwards <invalid@invalid.invalid> - 2022-12-22 15:54 +0000
Re: DSP like MCUs, or MCU like DSPs? David Brown <david.brown@hesbynett.no> - 2022-12-22 21:56 +0100
Re: DSP like MCUs, or MCU like DSPs? Grant Edwards <invalid@invalid.invalid> - 2022-12-23 01:40 +0000
Re: DSP like MCUs, or MCU like DSPs? David Brown <david.brown@hesbynett.no> - 2022-12-23 09:38 +0100
Re: DSP like MCUs, or MCU like DSPs? Dimiter_Popoff <dp@tgi-sci.com> - 2022-12-22 19:45 +0200
Re: DSP like MCUs, or MCU like DSPs? Rick C <gnuarm.deletethisbit@gmail.com> - 2022-12-22 11:57 -0800
Re: DSP like MCUs, or MCU like DSPs? Dimiter_Popoff <dp@tgi-sci.com> - 2022-12-22 22:24 +0200
Re: DSP like MCUs, or MCU like DSPs? David Brown <david.brown@hesbynett.no> - 2022-12-22 22:03 +0100
Re: DSP like MCUs, or MCU like DSPs? Rick C <gnuarm.deletethisbit@gmail.com> - 2022-12-22 17:11 -0800
Re: DSP like MCUs, or MCU like DSPs? David Brown <david.brown@hesbynett.no> - 2022-12-23 10:48 +0100
Re: DSP like MCUs, or MCU like DSPs? Rick C <gnuarm.deletethisbit@gmail.com> - 2022-12-23 03:44 -0800
Re: DSP like MCUs, or MCU like DSPs? Paul Rubin <no.email@nospam.invalid> - 2022-12-22 22:31 -0800
Re: DSP like MCUs, or MCU like DSPs? Rick C <gnuarm.deletethisbit@gmail.com> - 2022-12-23 00:14 -0800
Re: DSP like MCUs, or MCU like DSPs? David Brown <david.brown@hesbynett.no> - 2022-12-23 10:54 +0100
Re: DSP like MCUs, or MCU like DSPs? Clifford Heath <no.spam@please.net> - 2023-01-17 12:15 +1100
Re: DSP like MCUs, or MCU like DSPs? dalai lamah <antonio12358@hotmail.com> - 2022-12-23 15:07 +0100
csiph-web