SAM4E16E build configuration

[leoyu]

Hi,i want to replace SAM4E8E with SAM4E16E. I don’t know if there are any other differences than the amount of flash. The CoreNG only has build configuration with SAM4E8E, could this configuration work for SAM4E16E?

[chrishamm]

@leoyu AFAICS they are mostly identical except for the adress of CHIPID_EXID register. It might suffice to replace __SAM4E8E__ with __SAM4E16E__ in the CoreN2G project settings and to recompile the firmware then. Also, you'd have to use a different linker script if you wanted to use the full flash memory.

[leoyu]

@chrishamm Thank you, this is good info

[leoyu]

@chrishamm hi chrishamm, when compile SAM4E16E , i get the question with link script, hope to get your help.
1.which folder is the linker script file located,how can i find the linker script for SAM4E16E

2.if I get the linker script, may I just modify some parameters in linker script of SAM4E8E to match SAM4E16E, when I attempt to use the same coreng to be compatible with SAM4E8E and SAM4E16E in different project

3 .what if i write the BIN file built under SAM4E8E project into SAM4E16E chip
Many thanks

[dc42]

@leoyu said in SAM4E16E build configuration:

@chrishamm hi chrishamm, when compile SAM4E16E , i get the question with link script, hope to get your help.
1.which folder is the linker script file located,how can i find the linker script for SAM4E16E

It's in src/Hardware/SAM4E in the RRF project

2.if I get the linker script, may I just modify some parameters in linker script of SAM4E8E to match SAM4E16E, when I attempt to use the same coreng to be compatible with SAM4E8E and SAM4E16E in different project

Yes. I think the only change you need to make for the SAM4E16 is to change the LENGTH field of the rom section from 0x80000 to 0x100000.

3 .what if i write the BIN file built under SAM4E8E project into SAM4E16E chip

Yes that should work.

[Jonecy]

@dc42 thanks so much

[jazbaatbadalgaye]

@leoyu Hey, did you get any answers? I would be interested as well