Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

loading modules into memory on a vxWorks running target

226 views
Skip to first unread message

pappuda

unread,
Mar 18, 2009, 8:42:44 PM3/18/09
to
Hi Vxworks experts,

we know in general we run the vxWorks image in RAM and download any
kernel modules (or executables with extension *.out) on the vxWorks
running target board. this also loads into the RAM and we then spawn
the respective task.
In the above operation, we see the modules when loaded are assigned
memory locations dynamically from the MMU.

Is there any way out wherein i create a partition on the RAM space
after vxWorks is loaded and then load my executables into this
partition itself?

Please let me know the answers ASAP. Reasons for YES and NO type of
answers.

Regards,
Swaroop

osi...@gmail.com

unread,
Mar 20, 2009, 4:01:02 AM3/20/09
to

Use RamDisk

PAD

unread,
Mar 20, 2009, 3:36:51 PM3/20/09
to
You can use the loadModuleAt() API and control where module's text,
data and bss segments go.

Since loadModuleAt() requires that the caller gives the base addresses
of the segments you could indeed create a memory partition
(memPartCreate()) and then manage this pool of memory yourself (i.e.
make sure that there is nothing else using the memory, make sure that
the segments do not overlap, the unloader will not free the memory
used for the segments in this memory partition).

Hope this helps,

--
PAD

0 new messages