S12 / MagniV MicrocontrollersのトピックRe: Run in ram

Run in ram

oceansea — Wed, 24 Jul 2019 07:18:31 GMT

Our customer has a request on our bootloader, that is, the flash diver must not stored into the flash, it should download from CAN cummunication and then excute it to do flash download operation,when reset ,the data have no. I had noted that our community have some question about how to excute a function on ram, but they were all store into the flash, and when needed or program start, copy to ram, they are still store in flash. what I need is when: excute compile, I can get a section of target file in ram. not place in flash. and i have tried to do this, so I modified the prm file: use the ram as read-only type and place function in ram ,but the IDE prompt error

Re: Run in ram

kef2 — Thu, 25 Jul 2019 04:46:53 GMT

This is very simple. You need separate executable (s19, elf, etc) for flash driver, which is targeted to RAM instead of flash. You will somehow download it to RAM and execute. What you need is just change flash ROM segment address to point to RAM. Needless to say that you need to reduce RAM segment size to make it not overlapping with your new flash segment location. Of course this small flash driver executable project should be nonbanked. Since Codewarrior linker optimizes unused functions and variables out, you need to specify your driver functions in ENTRIES section of PRM file. That's it.

Re: Run in ram

lama — Thu, 25 Jul 2019 07:45:49 GMT

Hi,

In the past, when CodeWarrior 2.0 was used for debugging, there was a RAM target interface possible to be used to debug the code. The CodeWarrior directly loaded code into RAM ane executed it out of it. Unfortunately, this feature

has dissapeared with newer versions of the CodeWarrior and newer be used again.

Best regards,

Ladislav

Re: Run in ram

kef2 — Thu, 25 Jul 2019 08:25:18 GMT

Hi,

It doesn't make a lot of sense to add RAM target for each project, usually only small ones will fit the RAM, perhaps it was a right decision to not add them by default. And multiple targets in the same project still are present in CW 5.x. Project->Create Target, Project->Set Default Target menus and Targets tab still are enough for multiple targets in one project. Multiple PRM's can be readded to the project, ticking only targets which should use specified PRM. Thinking about this thread subject, hmm, it could be still the same project for loadable driver and bootloader, just an extra layer of complication.

Edward

Re: Run in ram

oceansea — Fri, 26 Jul 2019 01:41:55 GMT

thank you reply

well , i try to do follow your idea ,but it show this problem :

Re: Run in ram

kef2 — Fri, 26 Jul 2019 08:29:15 GMT

You didn't complete ...,COPY INTO destination, that's the source of your error. You shouldn't touch PLACEMENT section at all, only change SEGMENTS section to make ROM pointing to addresses in RAM, trim RAM segment to make room for ROM. Yes, it could be as you do

RAM = READ_WRITE 0x002E00 TO 0x003FFF;

ROM = READ_ONLY 0x002200 TO 0x002FFF;

please restore PLACEMENT section.

Re: Run in ram

oceansea — Sun, 28 Jul 2019 02:50:23 GMT

Thanks for your quick response, but i'm sorry that i dont't quite understand your thought.

maby is try to modify prm file follow below:

NAMES

END

SEGMENTS

RAM = READ_WRITE 0x002E00 TO 0x003FFF;

ROM = READ_ONLY 0x002200 TO 0x002FFF;

END

PLACEMENT

_PRESTART,

STARTUP,

ROM_VAR,

STRINGS,

NON_BANKED,

DEFAULT_ROM,

COPY INTO

DEFAULT_RAM

INTO RAM;RM;

END

INIT _EntryPoint

STACKSIZE 0x200

really?

Re: Run in ram

kef2 — Mon, 29 Jul 2019 12:12:09 GMT

PLACEMENT

_PRESTART,

STARTUP,

ROM_VAR,

STRINGS,

NON_BANKED,

DEFAULT_ROM,

COPY INTO

DEFAULT_RAM

INTO RAM;RM;

END

a,b,c INTO x;

d,e,f INTO y;

x and y are entries form SEGMENTS..END. You have only RAM and ROM segments, so INTO can be only into RAM or into ROM, but you made INTO pointing to DEFAULT_RAM, which is incorrect and this is why Codewarrior complained.

Re: Run in ram

oceansea — Tue, 30 Jul 2019 02:03:00 GMT

Thanks for your quick response，and i understand your thought;

but i still have a problem ,that :

//////////////////////////////////////

COPY INTO

DEFAULT_RAM

INTO RAM;RM;

/////////////////////////////////////////////////////////////////////

is copy the

//////////////////////////////////

STARTUP,

ROM_VAR,

STRINGS,

NON_BANKED,

DEFAULT_ROM,

/////////////////////////////////////////

into DEFAULT_RAM ?

and what's the meaning about: INTO RAM;RM ???

thank you very much

Re: Run in ram

kef2 — Tue, 30 Jul 2019 09:34:36 GMT

Arghh. You broke PLACEMENT section of your PRM, I explained why it is broken. You need to restore it, just that.

Re: Run in ram

oceansea — Tue, 06 Aug 2019 01:50:46 GMT

hi,

i do change follow your idea , it show :

i replace DEFAULT_RAM to RAM ,but it still show some wrong

Re: Run in ram

kef2 — Tue, 06 Aug 2019 05:56:26 GMT

Hi,

again, I suggested you to restore PLACEMENT block to it virgin state. You broke it again. RAM can't be at the same time SEGMENT and PLACEMENT. a,b,c INTO RAM INTO RAM, ROM; . If you don't know how to restore PLACEMENT block, create new project and copy PLACEMENT from there.

Edward

Re: Run in ram

oceansea — Thu, 08 Aug 2019 07:15:20 GMT

hi,

i don't know how to restore PLACEMENT block, this is my prj ,the prm file is generate by the PE,

could you help me modify it ?