I have not been able to get the CMake stuff to work. I'm using the Makefile.
I have found that some newer versions of Debian based distros have an issue with gcc and newlib. The Arm distributed toolchain works fine, I plan on using that in the future (until something else changes...). Don On Mon, Sep 10, 2018 at 09:45:00PM +1000, Alan Beard wrote: > Hi all, > > I'm trying to build the stm32 code on my Pi running Fedora 29. > > I get the following with "cmake ../../stm32" trying to get a working C > compiler: > > /usr/bin/arm-none-eabi-gcc -Wall -std=gnu11 -mlittle-endian -mthumb > -mthumb-interwork -nostartfiles -mcpu=cortex-m4 -fsingle-precision-constant > -Wdouble-promotion -mfpu=fpv4-sp-d16 -mfloat-abi=hard -D__FPU_PRESENT=1 > -D__FPU_USED=1 -rdynamic CMakeFiles/cmTC_da013.dir/testCCompiler.c.o -o > cmTC_da013 > > arm-none-eabi-gcc: error: unrecognized command line option '-rdynamic' > > I cannot find where option "-rdynamic" is added. > > Do I need to run the GNU Arm Embedded Toolchain, a later version. This I'll > have to compile from sauce. > > There is no ARM binary. > > It's always the small things...... > > Turbo blew in my Holden Jackaroo (GM Trouper) I have it in sight but the > bolts are frozen. > > These turbos are going cheap, cheap, cheap, $200 so I thought.... > > Alan VK2ZIW > > On Fri, 7 Sep 2018 07:39:15 +0200, Jacob Falzon wrote > > Yes I figured that memory is the key issue! > > > > When I was trying to implement the project with Keil I noticed that if I > > allocated too much memory to heap or stack (heap mostly because of the > > malloc calls) I was getting overrun behaviour from the ADC and transfer > > errors from the DMA just after the code turns on the ADC. > > > > When I decreased the Heap allocation to something more modest that > > behaviour stopped. > > > > Which I think is what's going on with the OFDM mode if you try getting it > > to work as it is right off the bat on the STM32 but funnily enough when I > > tried debugging it and noticed register values for the ADC and DMA they > > both seemed to be working properly which I found very strange. > > > > On Fri, Sep 7, 2018 at 12:37 AM David Rowe <da...@rowetel.com> wrote: > > > Can I be helpful trying to get the STM32 code running on the Nucleo64 > > > boards that I have for the MMDVM project? > > > Or perhaps, the Teensy 3.6? > > > > Pls feel free to work on anything you like Alan. Don has been building > > up a set of unit tests for the stm32 that may be useful. > > > > - David > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Freetel-codec2 mailing list > > Freetel-codec2@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > > > > Alan > > Evil flourishes when good men do nothing. > Consider the Christmas child. > --------------------------------------------------------------------------- > Alan Beard Unix Support Technician from 1984 to today > 70 Wedmore Rd. Sun Solaris, AIX, HP/UX, Linux, SCO, MIPS > Emu Heights N.S.W. 2750 Routers, terminal servers, printers, terminals etc.. > +61 2 47353013 (h) Support Programming, shell scripting, "C", assembler > 0414 353013 (mobile) After uni, electronics tech > > > _______________________________________________ > Freetel-codec2 mailing list > Freetel-codec2@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 _______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
