Re: Problem with STM32 pin configuration
Uwe Bonnes <bon-1JbLm1bU5j5ZIx36JBfelj3+ndqKAYMe9FMPySWZwLkb1SvskN2V4Q@public.gmane.org>
| Newsgroups | gmane.comp.hardware.microcontrollers.ethernut |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "Ole" == Ole Reinhardt <ole.reinhardt-L1vi/[email protected]> writes: Ole> Hi Uwe, Am 06.10.2015 11:46, schrieb Uwe Bonnes: >> In the long run, I tend to rewrite the spi-driver as one driver as >> stm32_i2cbus_v2.c already is. This will also require run-time >> decision on the pins used and remove the defines. Ole> I think, this would be the most elegant solution, and as extra Ole> benefit it saves code space, as stm32_spi.c ist not compiled in Ole> multiple times. Those multiple file inclusion also chew up Debugger breakpoints: (gdb) b Stm32SpiBusNodeInit Breakpoint 1 at 0x8005774: Stm32SpiBusNodeInit. (3 locations) (gdb) -- Uwe Bonnes bon-1JbLm1bU5j5ZIx36JBfelj3+ndqKAYMe9FMPySWZwLkb1SvskN2V4Q@public.gmane.org Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- _______________________________________________ http://lists.egnite.de/mailman/listinfo/en-nut-discussion