Of course. The snippet has to be written in a smart way, to be as portable as possible, with very clean indication, what has to be changed to adopt it to a different hardware.
Remember, the best thing about '51's is that they really keep a high degree of backward compatibility, so, usually, there is little to be chenged for testing the rudimentary features.


Of course, 2 different snippets for these.


Multipress, autorepeat - those are not needed for rudimentary tests. Might perhaps been contained in separate snippets, if one wants to test those (no reason for autorepeat but multipress might be interesting for fully decodable matrix (with diodes)).


All available languages :-) IMHO it is easy to port assembler to C of any kind for short tests, isn't it? If written in some of the freely available asms (asem, metalink's), one could quite easily donwload, "install" and produce the hex for modified "snippet".


Good point. However, a good example is worth 1000 tutorials+guidelines.


Another good point. The snippets should contain "what should it do" and "what might be wrong if it does not do what expected" sections.

OT: Sometimes my head is cleanest at 3am... In fact, the best pieces I ever wrote I wrote during night. There is too much distraction during the day - even the artificial noises from the street. At least this is how it works with me.


The problem is, it is "stuff". To be of any value, it must be a masterpiece in 10 lines, carefully hand crafted, wrapped with the appropriate information.

Teaching is a hard work!

Jan Waclawek