spi transfer

RE: spi transfer

awneil — Wed, 30 Dec 2015 21:40:50 GMT

Where, exactly, is this "uart_tx" you are talking about? I don't see it anywhere in the EFM32 port.

In the original ble-sdk-arduino, it appears only in the examples - it is not part of the library itself. And, as I said, it sends data over the air using the Nordic UART-over-BLE service - it has nothing to do with the communication between the host MCU and the nRF8001.

RE: spi transfer

Mohsen — Wed, 30 Dec 2015 17:12:45 GMT

thank you awneil for your answer. can you explain more for me about my question number 3 . I really cant find any relationship between "uart_tx" and spi hardware functions.

RE: spi transfer

awneil — Wed, 30 Dec 2015 10:05:55 GMT

This seems to be a continuation of your previous question:

devzone.nordicsemi.com/.../

If you feel that question is now closed, then please accept my answer there.

Porting the ble-sdk-arduino is really not that hard; the main things are

Pulling out the Arduino-specific stuff;
Getting it to compile in Keil.

It seems that the EFM32 port has already done that - so you should just have to adjust the hardware-specific bits; ie, the SPI, IO lines, and interrupt.

You really don't need to touch any of the actual ACI code.

The only disadvantage with the EFM32 port seems to be that there are no examples with it. But it shouldn't be hard to adapt the original Arduino examples.

I guess the "uart_tx" function name come from the case of using the Nordic UART-over-BLE service - it has nothing to do with the communication between the host MCU and the nRF8001?