Do the soft spi macros work for 1284? about sdfat HOT 6 CLOSED

I will not be updating this version of SdFat. You can define symbols like VARIANT_MIGHTY in pins_arduino.h and fix the typo in this version if you wish.

I will put your variant test in the new SdFat-beta and soon the beta will replace this version of SdFat.

from sdfat.

"this version". I'm not understanding what that means.
I'm not seeing anything but the master branch in this repo.
Do you have another repo somewhere?

So are you saying that in future releases the checks using VARIANT_XXX checks will
switch to using something that is available in the pins_arduino.h header file so it will
"automagically" work without users having to manually edit any files?

Today I'm going through all the 1284 code to verify that their pin definitions are consistent in all their
variants - they have had issues with this several times in the past and if there any issues the conditional checks above may change. I had to make a change to the checks yesterday since I had done that code in 2013 and they corrected an error in 2014 the a macro I use which affected the pin mappings and
I didn't see that change until a few days ago.

I only mention this as it is possible that the above conditionals may not be the final ones for
the 1284 core if I find any issues in their mappings.

from sdfat.

This version means the SdFat repository. I am about to totally replace the code in the SdFat repository with SdFat-beta here:

https://github.com/greiman/SdFat-beta

I have made the 1284 changes in the SdFat-beta repository so please test that code. I no longer test on 1284 since there are so few users so let me know what you find.

from sdfat.

I'm curious, why a separate repo vs just creating a branch?
I can't fully test 1284 either. I only test Sleeping Beauty which is the only 1284 board I have.
I haven't played with SD cards yet on Arduino. I'm only jumped in here since some issues came up on one of the Arduino 1284 threads and I saw a few issues when I looked at the code.

from sdfat.

"I'm curious, why a separate repo vs just creating a branch?"

Most users just hit the "Download Zip" button so I have two repositories.

GitHub is not the real development site for the SdFat base code. I don't use Arduino for my projects. The base code is developed for use with RTOSs on ARM boards with SDIO and USB mass storage.

I don't plan to update SdFat very often in the future.

from sdfat.

If you want a git host that also supports download images, you could use BitBucket instead.
It allows multiple download images that users can select from and you also get download
statistics to see how many people have downloaded it.
Since you create the zip images, you can create the zip images
with a proper name and tree so users can use the Arduino IDE GUI to install the library -
something they can't do with a github repo zip image.

I do this for my openGLCD library:
https://bitbucket.org/bperrybap/openglcd/wiki/Home

You can also use google code and then put the download images in the tree or in the wiki repo for
the project and then provide links to them on the main google code page or wiki page.
Google code used to have a downloads section, but they removed it, you get around this
by putting the images in the tree or on the wiki.
Google code can also host the documentation.

I will be switching back to google code for openGLCD as that way I can
host ready to install zip images, as well as the all the doxygen generated html library documentation.

I think it is very useful for users to be able to use the Arduino IDE GUI for installation
of libraries.
It also ensures that they don't screw up the installation.

from sdfat.