My 3th module bricked now. 
 
After I ran the program successfully in debug mode I just wanted to upload, immediately after my mcModule was bricked, I didn't modify any code.

I hope soon the new version from the OTA update to reset the script will come out, so I can test further, because now I'm totally stuck.

I was experimenting with my SPI to WS2801 LED software. Working pretty well at first, only the first LED was flickering but I found this is a common problem with the length of the cable or the power supply to the Led's and I only tried with different speeds of the SPI-bus, recompiling and uploading again and again, than it happened.

It works    after swapping the MOSI and MISO line !

There must be an error in the documentation it says: in chapter 12.3
The Create method creates an object that describe the path to a chip by specifying Speed, Mode, SCLK, MOSI, MISO and SC.
But it's, Speed, Mode, SCLCK, MISO, MOSI, CS

I don't know why I got a signal on the input but I guess it's just because nothing was connected, so I thought I was really displaying the info from the MOSI line while it was the MISO connection.

I'm so happy to know that SPI is done by hardware and not bitbanged! Love it! Tomorrow I will start to experiment with the WS2801 LED's ! Yippeee

Thanks mr. mc Abe. And thanks mc Things for the hardware SPI, much better!

I just tried your suggestion mr mc-Abe, but no difference. Tried modus 0 till 4 I can see differences in the polarity of the clock, also switched the MOSI with the CLK line on my logic analyser. But after studying some examples on the internet and making a working example on the SPI on my Feather Huzzah, I can only conclude that the signal is totally off. The only resembling with a correct pattern is that clock is symmetric and the CS line is working but than in my example and on the internet I see mostly bursts of the clock-signal for each byte, and also the typical pattern transmitting the bytes 0, 1, 2, 3, 4 I did in both test are totally off. I give you the working test on my Feather Huzzah in attachment. You can see clearly how the information is correctly interpreted by the analyser and how the clock and Mosi line behaves in time.

[ Guests cannot view attachments ]

Hmm, I can't find the code any-more and I don't want to brick another module before I can unbrick my 2 modules first. But I think I know what my mistake was.:
Instead of :
Dim data As ListOfByte = New ListOfByte
I forgot the New statement and did:
Dim data As ListOfByte = ListOfByte 

After that I did:
data.Add(element)
spi_device.Transfer(data)

I found out about my mistake by running in the debugger, he complaint that I had a null pointer variable or something like that.
My compiler didn't complain and so my module became bricked. So I think it's good practice to debug always first. 

First of all it took me a while to figure out I had to place Spi.Create in the Shared Boot Event() instead of in Sub New()
At least to get some signal out, I don't know why but when I place Spi.create in Sub new() nothing happens on the spi-bus with Transfer.
But placed spi.create in the Shared Boot Event I can see the clock-signal and the CS working but the data is always xFF whatever I try to send and whatever speed or mode I use.
I can clearly see the amount of bytes I've send with the Transfer() command but my logic analyser shows every byte as 0xFF, indeed when I try to connect my WS2801 Leds the only thing I get out of it is plain white and no colors.