spi: add SPI driver for STM32 family #12

superna9999 · 2017-04-29T11:51:28Z

Add a SPI master and slave driver for the STM32 SoCs.

Originally submitted on Gerrit: https://gerrit.zephyrproject.org/r/#/c/12286/6 for STm32Lx as native driver.

Changes since gerrit revision 6:

Converted uint*_t to u*_t

Then @ldts and @erwango helped move to ST HAL to have a LL based driver for all STM32 SoCs.

nashif · 2017-04-29T12:53:03Z

rebase and resubmit please, the ARM branch was out of date

superna9999 · 2017-05-15T08:37:36Z

Hi, @galak, is there something missing for this driver ?

MaureenHelm · 2017-05-16T12:44:30Z

drivers/spi/spi_stm32lx.c

+	}
+
+	for (br = 0 ; br < BR_SCALER_COUNT ; ++br) {
+		u32_t clk = clock / baud_rate_scaler[br];


Since baud_rate_scaler is always a power of two, it would be more efficient to do a shift instead of a divide

MaureenHelm · 2017-05-16T12:45:47Z

drivers/spi/spi_stm32lx.c

+}
+#endif
+
+#define BR_SCALER_COUNT		8


It would be safer to define this after baud_rate_scaler and use the ARRAY_SIZE() macro

Done, I removed the table since the br matches the >> value.

MaureenHelm · 2017-05-16T12:52:02Z

drivers/spi/spi_stm32lx.c

+
+	return 0;
+}
+


Should there be a SPI_0 instance here?

No, @erwango insists on having a 1:1 relationship with the numbering scheme used in the ST documentation
It's already the case for UART and I2C drivers.

MaureenHelm · 2017-05-16T12:55:34Z

drivers/spi/spi_stm32lx.c

+
+DEVICE_AND_API_INIT(spi_stm32lx_1, CONFIG_SPI_1_NAME, &spi_stm32lx_init,
+		    &spi_stm32lx_dev_data_1, &spi_stm32lx_cfg_1,
+		    PRE_KERNEL_2, CONFIG_KERNEL_INIT_PRIORITY_DEVICE,


Does this need to be initialized in PRE_KERNEL_2? Can we postpone to POST_KERNEL?

We can, it's a copy paste issue.

tbursztyka · 2017-05-16T13:08:18Z

drivers/spi/Kconfig

+	int "Port 3 default baud rate"
+	depends on SPI_3
+	default 500000
+


remove these 2 options above as you don't seem to use it. This was introduced by qmsi spi shim driver, for no good reason actually (and will become obsolete as soon as new spi API gets in)

tbursztyka · 2017-05-16T13:35:29Z

drivers/spi/spi_stm32lx.c

+	int br;
+
+	clock_control_get_rate(data->clock,
+			(clock_control_subsys_t *)&cfg->pclken, &clock);


parameters alignement:
foo(param1, ...
paramn, ... );

Seems like you could break a line before &clock to get it

This rules applies everywhere on function declaration and call, please apply it where relevant, I see many places where it could be applied.

tbursztyka · 2017-05-16T13:39:17Z

drivers/spi/spi_stm32lx.c

+	/* NOP */
+
+	return 0;
+}


you can remove that function altogether and not fill in a value in api_funcs, if NULL the public api will return 0

ldts · 2017-05-18T11:23:59Z

@superna9999 , have you tried hardwiring MISO/MOSI lines - leaving NSS open - and executing a loopback test? I am testing on nucleo and carbon that way with an old SPI driver we did for Zephyr last year and noticed a change seems to be needed in pinmux . Not sure if it is a problem in our old driver so I thought I'd check with you the behavior of this new driver.

superna9999 · 2017-05-18T13:04:19Z

@ldts Let me check back, but we use this driver in a near production ready product, so I assume it should work

superna9999 · 2017-05-19T14:05:16Z

@ldts I tested on a Nucleo_L432KC board and it worked fine

I fixed a small issue when CS is not exposed on a pin, but MISO input was good when connected to MOSI.

By forcing SSM to 1 and SSI to 1, it ignores the NSS IO input value.

ldts · 2017-05-19T15:28:54Z

@superna9999 thanks! I'll pull again and retest.
just so you know, I am using your driver on nucleo_401re and works as expected.

ldts · 2017-05-30T10:11:23Z

@superna9999 just checking that you are still ok with upstreaming your driver with the LL API instead of the original native version? I am only asking in case I need to start tracking :) TIA!

superna9999 · 2017-05-30T10:24:22Z

@ldts yes, I still need to do 2/3 changes and I'll switch this PR to it

Feat: NFFS sample app Closes zephyrproject-rtos#12 See merge request blik/embedded/zephyr!21

This makes the gatt metrics also available for gatt write-without-rsp-cb so it now prints the rate of each write: uart:~$ gatt write-without-response-cb 1e ff 10 10 Write zephyrproject-rtos#1: 16 bytes (0 bps) Write zephyrproject-rtos#2: 32 bytes (3445948416 bps) Write zephyrproject-rtos#3: 48 bytes (2596929536 bps) Write zephyrproject-rtos#4: 64 bytes (6400 bps) Write zephyrproject-rtos#5: 80 bytes (8533 bps) Write zephyrproject-rtos#6: 96 bytes (10666 bps) Write zephyrproject-rtos#7: 112 bytes (8533 bps) Write zephyrproject-rtos#8: 128 bytes (9955 bps) Write zephyrproject-rtos#9: 144 bytes (11377 bps) Write zephyrproject-rtos#10: 160 bytes (7680 bps) Write zephyrproject-rtos#11: 176 bytes (8533 bps) Write zephyrproject-rtos#12: 192 bytes (9386 bps) Write Complete (err 0) Write zephyrproject-rtos#13: 208 bytes (8533 bps) Write zephyrproject-rtos#14: 224 bytes (9244 bps) Write zephyrproject-rtos#15: 240 bytes (9955 bps) Write zephyrproject-rtos#16: 256 bytes (8000 bps) Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

This makes the gatt metrics also available for gatt write-without-rsp-cb so it now prints the rate of each write: uart:~$ gatt write-without-response-cb 1e ff 10 10 Write #1: 16 bytes (0 bps) Write #2: 32 bytes (3445948416 bps) Write #3: 48 bytes (2596929536 bps) Write #4: 64 bytes (6400 bps) Write #5: 80 bytes (8533 bps) Write #6: 96 bytes (10666 bps) Write #7: 112 bytes (8533 bps) Write #8: 128 bytes (9955 bps) Write #9: 144 bytes (11377 bps) Write #10: 160 bytes (7680 bps) Write #11: 176 bytes (8533 bps) Write #12: 192 bytes (9386 bps) Write Complete (err 0) Write #13: 208 bytes (8533 bps) Write #14: 224 bytes (9244 bps) Write #15: 240 bytes (9955 bps) Write #16: 256 bytes (8000 bps) Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

This makes the gatt metrics also available for gatt write-without-rsp-cb so it now prints the rate of each write: uart:~$ gatt write-without-response-cb 1e ff 10 10 Write zephyrproject-rtos#1: 16 bytes (0 bps) Write zephyrproject-rtos#2: 32 bytes (3445948416 bps) Write zephyrproject-rtos#3: 48 bytes (2596929536 bps) Write zephyrproject-rtos#4: 64 bytes (6400 bps) Write zephyrproject-rtos#5: 80 bytes (8533 bps) Write zephyrproject-rtos#6: 96 bytes (10666 bps) Write zephyrproject-rtos#7: 112 bytes (8533 bps) Write zephyrproject-rtos#8: 128 bytes (9955 bps) Write zephyrproject-rtos#9: 144 bytes (11377 bps) Write zephyrproject-rtos#10: 160 bytes (7680 bps) Write zephyrproject-rtos#11: 176 bytes (8533 bps) Write zephyrproject-rtos#12: 192 bytes (9386 bps) Write Complete (err 0) Write zephyrproject-rtos#13: 208 bytes (8533 bps) Write zephyrproject-rtos#14: 224 bytes (9244 bps) Write zephyrproject-rtos#15: 240 bytes (9955 bps) Write zephyrproject-rtos#16: 256 bytes (8000 bps) Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

Saw this crash with heavily loaded system in mimxrt1050_evk: <err> os: ***** MPU FAULT ***** <err> os: Data Access Violation <err> os: MMFAR Address: 0xc <err> os: r0/a1: 0x80000ab0 r1/a2: 0x800f6a60 r2/a3: 0x00000000 <err> os: r3/a4: 0x800f72a0 r12/ip: 0x00000000 r14/lr: 0x6000eb43 <err> os: xpsr: 0x41000000 <err> os: Faulting instruction address (r15/pc): 0x6000dc82 <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0 <err> os: Current thread: 0x80001a18 (rx_workq) <err> os: Halting system Where the fault at 0x6000dc82 points to ethernet_recv() uint16_t type = ntohs(hdr->type); 6000dc82: 89ab ldrh r3, [r5, #12] Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>

This makes the gatt metrics also available for gatt write-without-rsp-cb so it now prints the rate of each write: uart:~$ gatt write-without-response-cb 1e ff 10 10 Write #1: 16 bytes (0 bps) Write #2: 32 bytes (3445948416 bps) Write #3: 48 bytes (2596929536 bps) Write #4: 64 bytes (6400 bps) Write #5: 80 bytes (8533 bps) Write #6: 96 bytes (10666 bps) Write #7: 112 bytes (8533 bps) Write #8: 128 bytes (9955 bps) Write #9: 144 bytes (11377 bps) Write #10: 160 bytes (7680 bps) Write #11: 176 bytes (8533 bps) Write #12: 192 bytes (9386 bps) Write Complete (err 0) Write #13: 208 bytes (8533 bps) Write #14: 224 bytes (9244 bps) Write #15: 240 bytes (9955 bps) Write #16: 256 bytes (8000 bps) Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

Flush all messages and invoke `abort()` when a k_panic() or k_oops() is hit in native_posix mode. One of the main purposes of `native_posix` is to provide debug convenience. When running in a debugger, `abort()` stops execution which provides a backtrace and the ability to inspect all variables. A practical use case is fuzzing failures in SOF, see an example in: thesofproject/sof#8632 In such a case, this commit adds value even before using a debugger. Without this commit, confusingly meaningless stack trace: ``` INFO: seed corpus: files: 1097 min: 1b max: 428b total: 90853b rss: 58Mb Exiting due to fatal error ==314134== ERROR: libFuzzer: fuzz target exited #0 0x81d9637 in __sanitizer_print_stack_trace (zephyr.exe+0x81d9637) #1 0x80cc42b in fuzzer::PrintStackTrace() (zephyr.exe+0x80cc42b) zephyrproject-rtos#2 0x80ab79e in fuzzer::Fuzzer::ExitCallback() FuzzerLoop.cpp.o zephyrproject-rtos#3 0x80ab864 in fuzzer::Fuzzer::StaticExitCallback() (zephyr.exe+ zephyrproject-rtos#4 0xf783dfe8 (/usr/lib32/libc.so.6+0x3dfe8) zephyrproject-rtos#5 0xf783e1e6 in exit (/usr/lib32/libc.so.6+0x3e1e6) zephyrproject-rtos#6 0x82a5488 in posix_exit boards/posix/native_posix/main.c:51:2 SUMMARY: libFuzzer: fuzz target exited ``` Thanks to this commit the `k_panic()` location is immediately available in the logs without even running anything: ``` INFO: seed corpus: files: 1097 min: 1b max: 428b total: 90853b rss: 58Mb ==315176== ERROR: libFuzzer: deadly signal LLVMSymbolizer: error reading file: No such file or directory #0 0x81d9647 in __sanitizer_print_stack_trace (zephyr.exe+0x81d9647) #1 0x80cc43b in fuzzer::PrintStackTrace() (zephyr.exe+0x80cc43b) zephyrproject-rtos#2 0x80ab6be in fuzzer::Fuzzer::CrashCallback() FuzzerLoop.cpp.o zephyrproject-rtos#3 0x80ab77b in fuzzer::Fuzzer::StaticCrashSignalCallback() zephyrproject-rtos#4 0xf7f3159f (linux-gate.so.1+0x59f) zephyrproject-rtos#5 0xf7f31578 (linux-gate.so.1+0x578) zephyrproject-rtos#6 0xf788ea16 (/usr/lib32/libc.so.6+0x8ea16) zephyrproject-rtos#7 0xf783b316 in raise (/usr/lib32/libc.so.6+0x3b316) zephyrproject-rtos#8 0xf7822120 in abort (/usr/lib32/libc.so.6+0x22120) zephyrproject-rtos#9 0x82afbde in ipc_cmd src/ipc/ipc3/handler.c:1623:2 NOTE: libFuzzer has rudimentary signal handlers. Combine libFuzzer with AddressSanitizer or similar for better crash reports. SUMMARY: libFuzzer: deadly signal ``` Full stack trace When running zephyr.exe in gdb: ``` ./scripts/fuzz.sh -- -DEXTRA_CFLAGS="-O0 -g3" gdb ./zephyr.exe backtrace zephyrproject-rtos#2 0xf783b317 in raise () from /usr/lib32/libc.so.6 zephyrproject-rtos#3 0xf7822121 in abort () from /usr/lib32/libc.so.6 zephyrproject-rtos#4 0x082afbdf in ipc_cmd (_hdr=0x8b...) at src/ipc/ipc3/handler.c:1623 zephyrproject-rtos#5 0x082fbf4b in ipc_platform_do_cmd (ipc=0x8b161c0) at src/platform/posix/ipc.c:162 zephyrproject-rtos#6 0x082e1e07 in ipc_do_cmd (data=0x8b161c0 <heapmem+1472>) at src/ipc/ipc-common.c:328 zephyrproject-rtos#7 0x083696aa in task_run (task=0x8b161e8 <heapmem+1512>) at zephyr/include/rtos/task.h:94 zephyrproject-rtos#8 0x083682dc in edf_work_handler (work=0x8b1621c <heapmem+1564>) at zephyr/edf_schedule.c:32 zephyrproject-rtos#9 0x085245af in work_queue_main (workq_ptr=0x8b15b00 <edf_workq>,...) at zephyr/kernel/work.c:688 zephyrproject-rtos#10 0x0823a6bc in z_thread_entry (entry=0x8523be0 <work_queue_main>,.. at zephyr/lib/os/thread_entry.c:48 zephyrproject-rtos#11 0x0829a6a1 in posix_arch_thread_entry (pa_thread_status=0x8630648 .. at zephyr/arch/posix/core/thread.c:56 zephyrproject-rtos#12 0x0829c043 in posix_thread_starter (arg=0x4) at zephyr/arch/posix/core/posix_core.c:293 zephyrproject-rtos#13 0x080f6041 in asan_thread_start(void*) () zephyrproject-rtos#14 0xf788c73c in ?? () from /usr/lib32/libc.so.6 ``` Signed-off-by: Marc Herbert <marc.herbert@intel.com>

Flush all messages and invoke `abort()` when a k_panic() or k_oops() is hit in native_posix mode. One of the main purposes of `native_posix` is to provide debug convenience. When running in a debugger, `abort()` stops execution which provides a backtrace and the ability to inspect all variables. A good, sample use case is fuzzing failures in SOF, see an example in: thesofproject/sof#8632 In such a case, this commit adds value even before using a debugger. Without this commit, confusingly meaningless stack trace: ``` INFO: seed corpus: files: 1097 min: 1b max: 428b total: 90853b rss: 58Mb Exiting due to fatal error ==314134== ERROR: libFuzzer: fuzz target exited #0 0x81d9637 in __sanitizer_print_stack_trace (zephyr.exe+0x81d9637) #1 0x80cc42b in fuzzer::PrintStackTrace() (zephyr.exe+0x80cc42b) zephyrproject-rtos#2 0x80ab79e in fuzzer::Fuzzer::ExitCallback() FuzzerLoop.cpp.o zephyrproject-rtos#3 0x80ab864 in fuzzer::Fuzzer::StaticExitCallback() (zephyr.exe+ zephyrproject-rtos#4 0xf783dfe8 (/usr/lib32/libc.so.6+0x3dfe8) zephyrproject-rtos#5 0xf783e1e6 in exit (/usr/lib32/libc.so.6+0x3e1e6) zephyrproject-rtos#6 0x82a5488 in posix_exit boards/posix/native_posix/main.c:51:2 SUMMARY: libFuzzer: fuzz target exited ``` Thanks to this commit the `k_panic()` location is now immediately available in test logs without even running anything locally: ``` INFO: seed corpus: files: 1097 min: 1b max: 428b total: 90853b rss: 58Mb @ WEST_TOPDIR/sof/src/ipc/ipc3/handler.c:1623 ZEPHYR FATAL ERROR: 3 ==315176== ERROR: libFuzzer: deadly signal LLVMSymbolizer: error reading file: No such file or directory #0 0x81d9647 in __sanitizer_print_stack_trace (zephyr.exe+0x81d9647) #1 0x80cc43b in fuzzer::PrintStackTrace() (zephyr.exe+0x80cc43b) zephyrproject-rtos#2 0x80ab6be in fuzzer::Fuzzer::CrashCallback() FuzzerLoop.cpp.o zephyrproject-rtos#3 0x80ab77b in fuzzer::Fuzzer::StaticCrashSignalCallback() zephyrproject-rtos#4 0xf7f3159f (linux-gate.so.1+0x59f) zephyrproject-rtos#5 0xf7f31578 (linux-gate.so.1+0x578) zephyrproject-rtos#6 0xf788ea16 (/usr/lib32/libc.so.6+0x8ea16) zephyrproject-rtos#7 0xf783b316 in raise (/usr/lib32/libc.so.6+0x3b316) zephyrproject-rtos#8 0xf7822120 in abort (/usr/lib32/libc.so.6+0x22120) zephyrproject-rtos#9 0x82afbde in ipc_cmd src/ipc/ipc3/handler.c:1623:2 NOTE: libFuzzer has rudimentary signal handlers. Combine libFuzzer with AddressSanitizer or similar for better crash reports. SUMMARY: libFuzzer: deadly signal ``` The full stack trace is now immediately available when running zephyr.exe in gdb: ``` ./scripts/fuzz.sh -- -DEXTRA_CFLAGS="-O0 -g3" gdb build-fuzz/zephyr/zephyr.exe run backtrace zephyrproject-rtos#2 0xf783b317 in raise () from /usr/lib32/libc.so.6 zephyrproject-rtos#3 0xf7822121 in abort () from /usr/lib32/libc.so.6 zephyrproject-rtos#4 0x082afbdf in ipc_cmd (_hdr=0x8b...) at src/ipc/ipc3/handler.c:1623 zephyrproject-rtos#5 0x082fbf4b in ipc_platform_do_cmd (ipc=0x8b161c0) at src/platform/posix/ipc.c:162 zephyrproject-rtos#6 0x082e1e07 in ipc_do_cmd (data=0x8b161c0 <heapmem+1472>) at src/ipc/ipc-common.c:328 zephyrproject-rtos#7 0x083696aa in task_run (task=0x8b161e8 <heapmem+1512>) at zephyr/include/rtos/task.h:94 zephyrproject-rtos#8 0x083682dc in edf_work_handler (work=0x8b1621c <heapmem+1564>) at zephyr/edf_schedule.c:32 zephyrproject-rtos#9 0x085245af in work_queue_main (workq_ptr=0x8b15b00 <edf_workq>,...) at zephyr/kernel/work.c:688 zephyrproject-rtos#10 0x0823a6bc in z_thread_entry (entry=0x8523be0 <work_queue_main>,.. at zephyr/lib/os/thread_entry.c:48 zephyrproject-rtos#11 0x0829a6a1 in posix_arch_thread_entry (pa_thread_status=0x8630648 .. at zephyr/arch/posix/core/thread.c:56 zephyrproject-rtos#12 0x0829c043 in posix_thread_starter (arg=0x4) at zephyr/arch/posix/core/posix_core.c:293 zephyrproject-rtos#13 0x080f6041 in asan_thread_start(void*) () zephyrproject-rtos#14 0xf788c73c in ?? () from /usr/lib32/libc.so.6 ``` Signed-off-by: Marc Herbert <marc.herbert@intel.com>

Signed-off-by: Connor Graydon <connor.graydon@intel.com>

…ache net: dns: Add DNS cache for improved performance

Fix null pointer exception when fs_unmount is invoked concurrently while threads are doing file I/O Approved-by: Fabian van den IJssel Approved-by: Bas van Loon

nashif force-pushed the arm branch from eab63b5 to c40239d Compare April 29, 2017 12:48

superna9999 force-pushed the spi_stm32lx branch from 69f98f6 to ba4c71e Compare April 29, 2017 19:55

galak self-assigned this Apr 29, 2017

galak force-pushed the arm branch 2 times, most recently from 78c0221 to a1c74b7 Compare May 4, 2017 14:02

erwango approved these changes May 5, 2017

View reviewed changes

galak force-pushed the arm branch 2 times, most recently from 34a8649 to 255f198 Compare May 9, 2017 15:42

erwango approved these changes May 11, 2017

View reviewed changes

MaureenHelm requested changes May 16, 2017

View reviewed changes

MaureenHelm requested a review from tbursztyka May 16, 2017 13:00

tbursztyka requested changes May 16, 2017

View reviewed changes

superna9999 force-pushed the spi_stm32lx branch from ba4c71e to a1c91f4 Compare May 17, 2017 08:52

superna9999 force-pushed the spi_stm32lx branch 2 times, most recently from 0aabcf8 to 2977cf3 Compare May 19, 2017 14:04

galak force-pushed the arm branch from 42dad4a to ed187eb Compare May 19, 2017 17:40

superna9999 force-pushed the spi_stm32lx branch from 2977cf3 to 165f9be Compare June 1, 2017 07:53

superna9999 changed the title ~~stm32lx: spi: add SPI driver for STM32Lx family~~ spi: add SPI driver for STM32 family Jun 1, 2017

galak force-pushed the arm branch 3 times, most recently from 1d365cc to 0a8ad73 Compare June 9, 2017 14:38

galak force-pushed the arm branch from adce86e to 8b5c982 Compare June 12, 2017 16:45

frasa added a commit to blik-GmbH/zephyr that referenced this pull request Mar 25, 2019

Merge branch 'feat-nffs-sample-app' into 'dev'

89d31dc

Feat: NFFS sample app Closes zephyrproject-rtos#12 See merge request blik/embedded/zephyr!21

This was referenced Jun 13, 2019

kernel timeout_list repeatedly add a thread #16793

Closed

Bluetooth: Mesh: Rx buffer exhaustion causes deadlock #16864

Closed

xiaoliang314 mentioned this pull request Jun 26, 2019

Bluetooth: Fix various deadlock issues when running low on buffers #16870

Closed

Philipp-Wohlgenannt-Tridonic-com mentioned this pull request May 26, 2020

net: openthread: Add config for NCP vendor hook #25450

Closed

anchao mentioned this pull request Jul 30, 2020

Bluetooth: Mesh: Fix tx seg buffer with NULL pointer reference #27251

Merged

RafaelLeeImg mentioned this pull request Jan 19, 2022

Kernel usage fault when using semaphore with multi-threading #41963

Closed

piotrParf mentioned this pull request Feb 9, 2022

BLE Testing functions do not work properly #42534

Closed

NickolasLapp pushed a commit to NickolasLapp/zephyr that referenced this pull request Oct 19, 2022

[MFI] Encrypt mode 2 packets before transmitting (zephyrproject-rtos#12)

7eed017

sjanc mentioned this pull request May 16, 2023

Assert when executing GATT/SR/GAW/BV-14-C test #57930

Closed

talih0 mentioned this pull request Dec 13, 2023

subsys: shell_telent: don't close connection on EAGAIN #66287

Merged

LukaszMrugala pushed a commit to LukaszMrugala/zephyr that referenced this pull request Jul 3, 2024

Add no fast-fail to fms-ci-self-test (zephyrproject-rtos#12)

83aff08

Signed-off-by: Connor Graydon <connor.graydon@intel.com>

ldenefle added a commit to ldenefle/zephyr that referenced this pull request Aug 5, 2024

Merge pull request zephyrproject-rtos#12 from converge-io/lucas/dns-c…

bb47630

…ache net: dns: Add DNS cache for improved performance

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

spi: add SPI driver for STM32 family #12

spi: add SPI driver for STM32 family #12

superna9999 commented Apr 29, 2017 •

edited

Loading

nashif commented Apr 29, 2017

superna9999 commented May 15, 2017

MaureenHelm May 16, 2017

superna9999 May 16, 2017

MaureenHelm May 16, 2017

superna9999 May 16, 2017

superna9999 May 17, 2017 •

edited

Loading

MaureenHelm May 16, 2017

superna9999 May 16, 2017

erwango May 16, 2017

MaureenHelm May 16, 2017

superna9999 May 16, 2017

superna9999 May 17, 2017

tbursztyka May 16, 2017

tbursztyka May 16, 2017

superna9999 May 17, 2017

tbursztyka May 16, 2017

superna9999 May 17, 2017

ldts commented May 18, 2017

superna9999 commented May 18, 2017

superna9999 commented May 19, 2017 •

edited

Loading

ldts commented May 19, 2017

ldts commented May 30, 2017

superna9999 commented May 30, 2017

spi: add SPI driver for STM32 family #12

spi: add SPI driver for STM32 family #12

Conversation

superna9999 commented Apr 29, 2017 • edited Loading

nashif commented Apr 29, 2017

superna9999 commented May 15, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

superna9999 May 17, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ldts commented May 18, 2017

superna9999 commented May 18, 2017

superna9999 commented May 19, 2017 • edited Loading

ldts commented May 19, 2017

ldts commented May 30, 2017

superna9999 commented May 30, 2017

superna9999 commented Apr 29, 2017 •

edited

Loading

superna9999 May 17, 2017 •

edited

Loading

superna9999 commented May 19, 2017 •

edited

Loading