Meanwhile, I also find that, cc2520 driver is submitted, but it isWhat do you mean by "validated"?
Well, I can't find any driver about sam3's SPI on latest master tree.
Are you working with some patches not up-streamed or?
I really would like to take a look at such SPI driver.
cc2520 relies at 90% on SPI. Most of the time, bugs have been found on
And something tells me spi_sam3x_transceivec is not properly implemented.
cc2520:That's all about arduino_due GPIO specifics. In quark_se_devboard that's
==>linux cc2520 driver is very concise and clear, why don't port it toSure, because a driver from a totally different OS will just do the trick?
==>cc2520 driver defines macroYou don't have to care about that. That's internal stuff, which
application will never ever have to deal with.
We don't have plans ourselves in porting cc2520 to arduino_due.
It seems to me you are actually doing that yourself right?
cc2520 has been, for now, ported to quark_se_devboard and works well there.
However: this means providing the proper GPIO and SPI configuration.
This all goes through boards/arduino_due/<bfoard.h/board.c and Kconfig>
in your case.
Have you done that? Take a look at same files in boards/quark_se_devboard/
Do you have any patch to show so I can help you with the porting process?