| ??? 03/15/10 13:10 Read: times |
#174151 - So why on an 8051? Responding to: ???'s previous message |
Given that your requirement is defeated by a basic feature of the chip, and you are just trying to work around that feature, why would you want to do this on this chip?
Why not just use a chip that doesn't have this feature (which is a "limitation" in your application)? I want to make a system that has a basic operating system and set of drivers for a few peripherals such as a graphic LCD display. The system could then run various programs on top of this simple OS depending on what MIDI gear the user wants to control. The 8051 is not a great choice for that kind of thing. As David Prentice prentice asked here, are you just using this chip because you happen to have a big pile of 'em to use up? Or do you want this to be a particular "challenge" to your students? |
| Topic | Author | Date |
| Controlling /EA with a port pin? | 01/01/70 00:00 | |
| Why would you want do this?? | 01/01/70 00:00 | |
| Allowing system upgrades via MIDI sysex in the field | 01/01/70 00:00 | |
| So why on an 8051? | 01/01/70 00:00 | |
| Challenge?? | 01/01/70 00:00 | |
| Old fashioned 8031 dev boards | 01/01/70 00:00 | |
| Helpful points | 01/01/70 00:00 | |
| Good match | 01/01/70 00:00 | |
Budget | 01/01/70 00:00 | |
| See value to an extent... | 01/01/70 00:00 | |
| Internal XDATA addresable as XCODE? | 01/01/70 00:00 | |
| Executing code from XRAM | 01/01/70 00:00 | |
| Code in OnBoard XRAM | 01/01/70 00:00 | |
| Don't overlook other options ... | 01/01/70 00:00 | |
| FX2 | 01/01/70 00:00 | |
| I bet you can't | 01/01/70 00:00 | |
| Ideally a single chip design | 01/01/70 00:00 |