What alterations would it take for this codebase to be adopted in a
bunch of commercial products in the same way as BSD Unix and Linux?
I believe new research and signal processing coding can only be done
by experts. I also believe more new implementations and ports will be
done by non-experts,
David does code in an older style and that can look odd to newer
programmers, but the newer styles look verbose to older programmers. I tend
to use every const declaration possible, etc., so that the compiler will
show me more coding errors and it has frustrated me that the codec2 code
doesn't do
A lot boils down to the question. I think codec2 is well documented and
list has always been helpful. I also think the last question asked about
the UART was really a question about how to use the UART on the STM32
without breaking Codec2. The answer was use interrupt driven UART (or DMA
UART)
No problem Eric,
Also, just to be complete, as you probably already know, but after the .elf
file is built, there is a rule to convert it to a .bin file before upload
to the device.
# Rule for building .bin files from a .elf
%.bin: %.elf
$(OBJCOPY) -O binary $< $@
which translates to:
I've often wondered how broad is the church of codec2/freeDV developers,
especially after the recent discussions ;-) ?
Some of the project developers CVs are amazing but do we include many
radio-ham / software hobbyists in our ranks?
Because my career background is broadcasting, not software, I
Thanks Steve,
You have helped me out heaps.
Better idea of what I need now.
Cheers
Eric.
On 2016-09-07 11:42, Steve wrote:
> I notice there is "feature creep" in there. I usually strip out this stuff
> and then work through all the resulting errors to find where they are
>
Thank you Glenn and I apologize to all if I offended any one and should
have kept my response to personal email.
I am just trying to get up to speed as quickly as possible and I
appreciate all the help people are giving me.
I am sorry if questions have been asked before.
Regards
Eric
I notice there is "feature creep" in there. I usually strip out this stuff
and then work through all the resulting errors to find where they are
intertwined in the other .h and .c files. But the following files are
unusable fluff right now to your specific HF radio task:
$(CODEC2_SRC)/kiss_fftr.c
Hi Eric
I retract my last comment about you being "inexperienced or poorly
skilled or both in the art."
I apologize it was uncalled for.
However.
Do consider the company you keep here. Go and read the bio on some of
these guys like Bruce.
regards
On 7/09/2016 6:44 PM, e...@vk5kbb.com
For example, the rule is:
sm1000.elf: $(SM1000_SRCS:.c=.O3.o) src/stm32f4_dac.O3.o \
src/stm32f4_adc.O3.o libstm32f4.a
$(CC) $(CFLAGS) -O3 $^ -o $@ $(LIBPATHS) $(LIBS)
Which says it needs SM1000_SRCS, src/stm32f4_dac.O3.o,
src/stm32f4_adc.O3.o, libstm32f4.a
Working
Eric
That's a bit rich in considering the company you are keeping on
this forum
I hope you don't do any really serious client software work, in my
opinion you are inexperienced or poorly skilled or both in the
art.
Now, if you
Thanks for that Steve,
That should help heaps.
I'm not up to speed with make files because I usually work in and IDE
which take care of this.
By being able to just place the files I need in a suitable folder I will
be able to much eaiser import this code into an IDE where I can begin to
The necessary files are in the stm32/Makefile
Look at the rule for sm1000.elf and work backwards. Were it I, I would copy
the Makefile and edit out the builds you don't need.
--
Hi Bruce,
This kind of thinking is the reason open source projects are not taken
seriously and are seen as little more than toys.
I am guilty myself of being lazy, fortunately there are people who don't apply
the same reasoning.
I do get frustrated when I try to get people into open source and
Bruce I have to say I take offense to a comment like that.
I'm trying to make something that will benefit the whole FreeDV
community.
Yes I don not work on much open source code for the very reason that you
describe.
It's usually poorly documented, mish mash of code, written in different
15 matches
Mail list logo