Okay so, as I understand it, the difference between RISC and CISC processors goes something like this:
-RISC
read-do-store
-CISC
do_x @ (mem_loc_1) & (mem_loc_2)
And so the assembly instructions for Arm processors differ in how a single cycle for an instruction is timed? So each corresponding read-do-store cycle of quickest time for, say, one command and then save it somewhere, is considered "one cycle"? Or is each operation other than load/store ops, like logic and arithmetic operations on registers? And this "lowest time in one cycle" definition is what is known as 'atmoic'?
Previous threads directed me to websites like this:
https://wiki.osdev.org/Real_mode_assembly_bare_bones - x86 aside, the concept behind it is understood.
And of course, the manual.
Just general questions though, still learning and using the raspberry pi 3 b+ has helped quite a bit. Rpi3 seems to operate differently though. Seems that some kind of EEPROM stores a startup cycle that reads from a file in a certain format. Was wondering the conceptual details behind this sequence, or if it matters if processor commands can be known and you can follow the steps in the osdev.org and just write bits to location 0x0 to 0x4 for the first 4 bytes loaded from storage "directly" into wherever. Or something like that. Details are hazy.
Others have suggested just to learn cisc instead of arm stuff. What kind of pro/cons are there to this type of choice between choosing to learn one or the other? Especially considering most things on tiny chips are super specialized? It seems that the concept of interacting with the hardware through memory at an abi level, as the efi stuff is loaded (as on the RasPi from EEPROM) on boot to make sure it boots as per manufacturer specs? Correct?
-RISC
read-do-store
-CISC
do_x @ (mem_loc_1) & (mem_loc_2)
And so the assembly instructions for Arm processors differ in how a single cycle for an instruction is timed? So each corresponding read-do-store cycle of quickest time for, say, one command and then save it somewhere, is considered "one cycle"? Or is each operation other than load/store ops, like logic and arithmetic operations on registers? And this "lowest time in one cycle" definition is what is known as 'atmoic'?
Previous threads directed me to websites like this:
https://wiki.osdev.org/Real_mode_assembly_bare_bones - x86 aside, the concept behind it is understood.
And of course, the manual.
Just general questions though, still learning and using the raspberry pi 3 b+ has helped quite a bit. Rpi3 seems to operate differently though. Seems that some kind of EEPROM stores a startup cycle that reads from a file in a certain format. Was wondering the conceptual details behind this sequence, or if it matters if processor commands can be known and you can follow the steps in the osdev.org and just write bits to location 0x0 to 0x4 for the first 4 bytes loaded from storage "directly" into wherever. Or something like that. Details are hazy.
Others have suggested just to learn cisc instead of arm stuff. What kind of pro/cons are there to this type of choice between choosing to learn one or the other? Especially considering most things on tiny chips are super specialized? It seems that the concept of interacting with the hardware through memory at an abi level, as the efi stuff is loaded (as on the RasPi from EEPROM) on boot to make sure it boots as per manufacturer specs? Correct?