Actions
Engagement
  • Author Author: tariq.ahmad
  • Date Created: Date Created
  • Last Updated Last Updated:
  • Views 650 views
  • Likes 0 likes
  • Comments 10 comments
Related
Recommended

Project14 | Poll to Decide July 18' Competition

Parents

  • Hi Tariq,

     

    For an upcoming Project14 how about a 1K MCU challenge. Essentially any idea is allowed but must include a single 8-bit microcontroller using no more than 1KByte of program memory/internal flash. No other external flash or program storage is allowed but you can use as much of the data memory/non-volatile RAM as you want. Therefore the Arduino Uno could be used if members want to test out their C skills; but some will just jump into assembler with their favourite MCU.

     

    Along a similar track we could also have an Eight Pin MCU challenge (or 6 pin even !). e.g. using a device that has only 8/6 pins in total.

     

    Rod

  • in reply to 14rhb

    Man, talk about putting a restrictor plate on a dev. I like the idea though.  Would this be restricted to just a single 8-bit 8/6 pin MCU or could one cluster a set of similar chips to expand functionality? 

  • in reply to jomoenginer

    Hi Jon,

     

    I was narrowing it down in my suggestion as that would force entrants to be really clever with code use...a skill that is gradually lost as we compile in higher level languages & get spoilt by the available program memory sizes (if your code doesn't fit then you can usually upgrade to the next part with the same footprint for £0.02 extra).

     

    But good point; it would be a shame to exclude people form taking part just because they are geared up for 16-bit or 32-bit MCU.

     

    Perhaps your suggestion of multiprocessors could be a different month's Project 14 - "Clustered MCU's - design something that uses two or more MCU".

     

    Rod

Comment
  • in reply to jomoenginer

    Hi Jon,

     

    I was narrowing it down in my suggestion as that would force entrants to be really clever with code use...a skill that is gradually lost as we compile in higher level languages & get spoilt by the available program memory sizes (if your code doesn't fit then you can usually upgrade to the next part with the same footprint for £0.02 extra).

     

    But good point; it would be a shame to exclude people form taking part just because they are geared up for 16-bit or 32-bit MCU.

     

    Perhaps your suggestion of multiprocessors could be a different month's Project 14 - "Clustered MCU's - design something that uses two or more MCU".

     

    Rod

Children
No Data