I received a new Yun yesterday. It is the first and only one I have seen. Everything has been O.K. with the check out until today. I purchased an 8GB Toshiba Micro SD memory card. It won't fit into the connector on board the Yun! My Yun board uses a KINGCONN connector. It appears to have a plastic shoulder on the same side of the connector as the Micro SD memory card has a tab. The tab catches on the shoulder and won't insert more than half way. The same Toshiba Micro SD card fits on my EtherNet shields that I use on my Uno just fine.
Does anyone have an idea what is wrong? Is it possible the plastic on the side of the KINGCONN connector was melted in the manufacturing operation?
Did you try to see if you can actually access the SD card? On the Yun, the SD card does not "click" latch into the socket, nor does it insert all the way. Unlike the ethernet Shield, where the card fully inserts into the socket, on the Yun, it's normal for it to only go in half way.
This picture shows the SD card fully inserted into a Yun:
Thank you very much for the picture. That looks exactly like mine. It looks like the Yun is "designed" that way.
I haven't detected the card yet. Maybe I have some problem with the directory name. I didn't look into that very far since I didn't think the card was properly inserted. You have given me encouragement to continue the check out further. I will let you know what I find.
It should appear in Linux as /mnt/sda# where # is usually 1. If the SD card contains a folder named arduino at the root level, the Linux system will also make a symbolic link so that it can be accessed as /mnt/sd regardless if what physical number gets assigned to the card.
Note that the SD card is managed by the Linux side. If you want to access it from a sketch, you use the FileIO class of the Bridge library. The SD card is not directly accessible from the sketch using the SD library - the Yun does not behave like an Ethernet Shield, and old sketches that work with the shields networking and SD card libraries will need to be re-written. It's a side effect of the increased processing power provided by the Linux processor.
