Originally posted by the_fornicator you just have to understand a bit about the kernal and how certain architectures use registers and how it fits into the bigger picture of a processor/mico-control system.
the assembly code is limited to how the (micro)processor's architecture is set up, how it handles interrupts/exceptions and how/when it goes into kernal/user mode. In that case, wouldn't that indicate that the assembly code is just a variable that is dependent on the processor, and thus, not the bigger picture?
why are you guys looking at it from such a narrow viewpiont?
416 & fornicator --> without knowing 'the bigger picture,' learning how to operate a microcontroller with assembly instructions is going to be incredibly confusing and ultimately fruitless
the whole point of microcontrollers is that they can store instructions and operate them, yes the instructions are stored in memory and executed by this 'big picture' microcontroller, but ultimately those assembly instructions contain the bits that physically control the microcontroller
without knowing the system it's sort of foolish to intend on controlling it
i could play here forever, at school it feels like i can't get away from assembly/vhdl/matlab