This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
地址偏移量从0x24 直接跳到 0x2c，和技术手册上的不一样。
是因为库的版本问题吗？？
哦....
这里应该是hw_upp.h定义错了，starterware里没有upp的driver和example，估计也就没有测试发现这个错误。
BSL里的evmc6748_uPP.h定义就是对的，因为EVM板的BSL是有测试过的。
typedef struct{ volatile uint32_t UPPID; // 0x0000 volatile uint32_t UPPCR; // 0x0004 volatile uint32_t UPDLB; // 0x0008 volatile uint32_t NA1; // 0x000c not accessable volatile uint32_t UPCTL; // 0x0010 volatile uint32_t UPICR; // 0x0014 volatile uint32_t UPIVR; // 0x0018 volatile uint32_t UPTCR; // 0x001c volatile uint32_t UPISR; // 0x0020 volatile uint32_t UPIER; // 0x0024 volatile uint32_t UPIES; // 0x0028 volatile uint32_t UPIEC; // 0x002c volatile uint32_t UPEOI; // 0x0030 volatile uint32_t NA2; // 0x0034 not accessable volatile uint32_t NA3; // 0x0038 not accessable volatile uint32_t NA4; // 0x003c not accessable volatile uint32_t UPID0; // 0x0040 volatile uint32_t UPID1; // 0x0044 volatile uint32_t UPID2; // 0x0048 volatile uint32_t NA5; // 0x004c not accessable volatile uint32_t UPIS0; // 0x0050 volatile uint32_t UPIS1; // 0x0054 volatile uint32_t UPIS2; // 0x0058 volatile uint32_t NA6; // 0x005c not accessable volatile uint32_t UPQD0; // 0x0060 volatile uint32_t UPQD1; // 0x0064 volatile uint32_t UPQD2; // 0x0068 volatile uint32_t NA7; // 0x007c not accessable volatile uint32_t UPQS0; // 0x0070 volatile uint32_t UPQS1; // 0x0074 volatile uint32_t UPQS2; // 0x0078} uPP_regs_t;
自已手动改一下吧。
