Hello everybody,

finally I manged to contribute my Project to the MySensors Contest 2015.
It is a 3d printable Wall Remote control for Home Automation. The Size is 55x55mm, so it fits into many "switch frames" (e.g. Berger, Gira, Merten etc.) The project consists of the 3d printed Parts, the PCB (with Eagle sources), the Sketch, an FHEM example and of cause a detailed documentation which describes howto rebuild this Project on your own. All this is included in the zip file I will provide.

Because the pdf, where the building is described precisely, is quiet long (20 pages I guess, but many photos) I don't want to put it here in the post. If you are intrested in the Project just have a look at the pdf inside the zip file. There are also more pictures included.

WallRemote.zip

To finish this project you need the following equipment/skills: 3D printer, SMD soldering capabilites, AVR Programmer (to install bootloader)

Enough of talking, lets let the pictures speak for themselve:

A 3d preview of the printer parts can also be found on Thingiverse: http://www.thingiverse.com/thing:692238

@Gulpman @hek
Hello everybody,
I just added a pullrequest which will support SST25 Series flash for OTA Bootloader:
https://github.com/mysensors/Arduino/pull/445

SST25 Series flash mentioned by Gulpman as 1st and 2nd Alternative are currently not supported, because the dont support pagewriting with opcode 0x02. Instead they support Automatic Address Increment Word writing (opcode 0xAD). I updated teh SPIFlash.cpp and .h so they will take care of that if #define MY_SPIFLASH_SST25TYPE is set somewhere.
I tested with this SPI Flash: http://www.reichelt.de/25PF020B80-4C-S/3/index.html?&ACTION=3&LA=446&ARTICLE=137365&artnr=25PF020B80-4C-S&SEARCH=25pf020b80 which is of Type SST25PF020B-80-4C-SAE (2MBit) and working now.

I only hat a short look at the ISSI and Winbond flash Datasheets mentioned by Gulpman before. At first look I think they both could work with the current Mysensors / SPIFlash Version becuase they support Pagewriting with opcode 0x02 and seem to implement the other relevant opcodes. However I did not test..!

Best Regards
DirkH / D-H-R :)

-edited on 2016-06-01 to take care of changed Name for define (added "MY_")

@jaumard
yes nrf24L01+ works fine. in fact only the plus version works fine because mysensors typically uses the slower but more power effective 250kbps mode which was introduced with the + version. Older version (without +) needs some tweaks to work..

Glad it helped David. I just thought about it again, maybe sleep(0xff, 0x00, 0) does work too. I did not test it but I think it calls the same function anyway.

However the method of direct calling sleep(0xff, 0x00, 0xff, 0x00, 0) should save some clocks because one less jmp is required :)

Yes the AT25DF512 seems to outperform other memories and is truly a good chip. However unfortunately its hard to get in Germany (and maybe other parts of the world ;) ). The common distributors here do not have it in stock...

Sorry for replying this late, just having some "real world" issues ;)
Yes, with the new driver it works. Do we have a comparison about pros/cons of the new RFM69 driver. As I'm migrating all my nodes from nrf24 to rfm69 its no problem to use the new driver in all sketches. Just wondering what has changed in the new driver..

Thanks, DirkH

About the AT25F512N wich was proposed by @AWI: tbowmo was right, I got confused by Sector, Page and Block erase. Like tbowmo said atmel does call blocks sectors... The AT25F512 does not support Block Erase 64k, which is defined but AFAIK not used in SPIFlash.cpp BUT it is used in the Bootloader if the "Imagesize" is > 32k. But I dont know how Image size is retrieved. Also I think for an ATMega 328p the image size should never be >32k. So this Flashtype could probably work as long as the image size is below 32k. I'd expect the Bootloader to crash or fail when program size is >32k.

About the S25FL... @bjacobse proposed I see the problem that it does not support the Bock Erase 32k opcode which is used in SPIFlash.cpp and Bootloader. Both must be changed when S25FL... should be used. (I would emulate the 32k Block erase by 8 times 4k Block erase.) However remember that Dualoptiboot must also be altered which requires "non-arduino" programming and some work / knowlegde about makefiles / compiler/linker settings in IDE.

@sundberg84
It does not work for me with softspi too. Although the debug output does not look that bad..

MCO:BGN:INIT GW,CP=RPNGA---,FQ=16,REL=255,VER=2.3.2<\n>
4 TSM:INIT<\n>
5 TSF:WUR:MS=0<\n>
8 TSM:INIT:TSP OK<\n>
10 TSM:INIT:GW MODE<\n>
12 TSM:READY:ID=0,PAR=0,DIS=0<\n>
14 MCO:REG:NOT NEEDED<\n>
577 GWT:TIN:IP=192.168.178.203<\n>
1581 MCO:BGN:STP<\n>
1583 MCO:BGN:INIT OK,TSP=1<\n>
1585 TSM:READY:NWD REQ<\n>

@sundberg84 Hi, I'm not using level converters becuse I use a ProMini with 3,3V (with W5100 and rfm69hw).

Maybe I have a small clue: The Interrupt Pin is high all the time. It seems that the interrupt request from the RFM Module is not processed. I cant see interrupts when I start a node. (With a working setup with ESP8266 and RFM69, the pin is low most of the time except when new packets arrive from a sensor).