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:
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
>
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
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
Eric,
When you work with an Open Source project, you are not expected to need
documentation of the overall structure of the code, or a list of the
essential files, or a timing diagram, or an explanation of the interrupt
priority (we already told you it's a busy loop, which means there is no
SM1000_SRCS in codec2-dev/stm32/Makefile
On 07/09/16 14:17, e...@vk5kbb.com wrote:
> Also while I'm looking at adding and removing parts of the code.
>
> Does any body have a list of essential files needed for building the
> SM1000.bin and nothing else.
>
> I can see a lot of test code and also
Also while I'm looking at adding and removing parts of the code.
Does any body have a list of essential files needed for building the
SM1000.bin and nothing else.
I can see a lot of test code and also now in the -DEV folder there is a
lot of SM2000 code.
I'd like to have a build folder
12 matches
Mail list logo
