Hi Josh and all,
Should I say, I've been running a Codec2 "parrot" (store and repeat) repeater
for a couple of years 24x7!
But without ONE taker other than 5Km away, it's now off.
There are not enough Codec2 hams here in Australia.
AND, for emergency wide area comms on HF that are "semi-secure
Thanks David,
My preference is new hardware too, for several measures of "better
performance".
> Re CPU load I haven't measured the codec alone but I estimate about
half a floating point stm32, so 80 MHz or so. We run the entire FreeDV
stack (modem, codec, FEC, drivers, protocol) in a 168 MHz st
I think, based on my profressional experience with the F4 , L4, L, in
battery environments - you would be far better to use an F4 part for
this.
-aggressively down clock it when the full clock speed is unnecessary
You can save a ton of power doing that.
The chip is very good at changing cloc
Glen
> But, certainly it should compile and run and you would be able to
generate benchmarks for your implementation- that's really what you
need
to do.
That's probably what I'll do, get an L4 and just test it, though knowing
roughly if it'll work before I go through the effort of shipping a
de
On Thu, May 13, 2021 at 3:51 PM Josh Lloyd wrote:
> I'll look into the OpenRTX project, I had not heard of it so thank you.
> Though, that may be tangential to the goals of our project, which is to
> build some hardware and firmware for our own radios.
>
Obviously everybody gets to do what they
Josh
L4 has the FPU , it IS an Cortex M4 core.
but there are many many low power optimizations internally , with
respect to caching, memory bandwidth etc. Per is specificed at
1.25DMIPS/MHz for both F4 and L4. Some of the L4 low power facilities
are NOT available when running at performanc
Josh
L4 has the FPU , it IS an Cortex M4 core.
but there are many many low power optimizations internally , with
respect to caching, memory bandwidth etc. Per is specificed at
1.25DMIPS/MHz for both F4 and L4. Some of the L4 low power facilities
are NOT available when running at performanc
Hi Josh,
Yes I am in general agreement with Bruce's comments. Last I heard
(about 1 month ago) the m17 project have put their own custom hardware
development on hold and are focusing on ports to COTs HTs.
I'm quite keen on the custom open hardware approach because:
(i) re-use of COTS hardwa
Hardware floating point is required. So, your low-power CPU might not be
the right choice - I think only the ones with "F" in the part number have
hardware floating point. And don't ask anyone to rewrite the code for
fixed-point unless you have a lot of money :-)
Since OpenRTX has been getting Co
Hi Bruce, thanks for your reply.
> Hardware floating point is required. So, your low-power CPU might not
be the right choice - I think only the ones with "F" in the part number
have hardware floating point.
STM32L series are, as I understand it, an extension of the F series in
that they also hav
10 matches
Mail list logo
