Memory range 0x20007F00 - 0x20007FFF, case 23

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads athttps: //www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
JamesHiebert
Offline
Last seen:5 months 1 week ago
加入:2014-10-24 14:17
Memory range 0x20007F00 - 0x20007FFF, case 23

Hello Dialog,

In scatterfile_common_581.sct, we have the following:

...
LR_IROM5 0x20000450 0x93b0 {
ER_IROM5 0x20000450 0x7ab0 {
*(InRoot$$Sections) ; All library sections that must be in a
; root region, for example, __main.o,
; __scatter*.o, __dc*.o, and * Region$$Table
boot_vectors.o (+RO)
system_ARMCM0.o (+RO)
; * armlib * (+ RO)
.ANY (+RO)
.ANY (+RW)
}

; *********************************************************************************************
; * END OF OTP - ANYTHING BELOW THIS POINT IS NOT WRITTEN WHEN THE CODE IS BURNED TO THE OTP! *
; *********************************************************************************************

RW_IRAM50 0x20008000 ZI_AT_8000 { ; ZI
.ANY (retention_mem_area0) ; application data
.ANY (+ZI)
}
...

This leaves the memory range 0x20007F00 - 0x20007FFF unallocated. May I increase the size of ER_IROM5 to 0x7bb0 without side effects? I may need those 256 bytes ;-).

Thanks!

Device:
MT_dialog
Offline
Last seen:1 month 1 week ago
工作人员
加入:2015-06-08 11:34
Hi JamesHierbert,

Hi JamesHierbert,

Yes, you can do that but, you wont be able to use the OTP (for performing an OTP copy). This area should stay clean for the OTP header to be copied.

Thanks MT_Dialog