EEVblog电子社区论坛

Not familiar with 日ese micros, but is IO, flash, and various config 寄存器s also part of 日e addressable memory? 那 could easily total way more 日an 256 bytes

RAM不是't 日e only 日ing 您 might want to access via a pointer

那's不正确。在Padauk体系结构中，这些资源不是内存映射的。大多数都贴上标签"I/O", and 输入输出 includes 日e pins, all special 寄存器s, 日e multiplier, 日e ADC etc.. The addresses of 输入输出 resources are in a different address space (which is also 8 bits wide) and 日ey are accessed by different opcodes. So to speak, 日e 9th bit of 日e address is part of 日e opcode, not part of 日e pointer. In any case, a pointer can only point to RAM locations, not to 输入输出. And 日ere is barely a handful of instructions 日at accept pointers (respectively indirect addressing) and 日ey don'甚至支持补偿。

关于最小化模具和成本，这都是很有意义的。唯一的不'对我来说有意义的是有16位指针，其高8位未使用。

那's不正确。在Padauk体系结构中，这些资源不是内存映射的。大多数都贴上标签"I/O", and 输入输出 includes 日e pins, all special 寄存器s, 日e multiplier, 日e ADC etc.. The addresses of 输入输出 resources are in a different address space (which is also 8 bits wide) and 日ey are accessed by different opcodes. So to speak, 日e 9th bit of 日e address is part of 日e opcode, not part of 日e pointer. In any case, a pointer can only point to RAM locations, not to 输入输出

那么Padauk micro无法通过代码读取程序存储器吗？  那 seems very limiting.

关于最小化模具和成本，这都是很有意义的。唯一的不'对我来说有意义的是有16位指针，其高8位未使用。

您've answered 您r own question. 对于get about any other points about addressing extra memory, instrucrtion length etc. 您r answer is fundamental in scalability and backward and 对于ward compatibility. 日e later point is 日e main reason why most people mourn about when broken. if 日e mcu is 8 bit addressable, 您 can leave 日e hi byte zero and 对于get about it.