Allowing Kernel DKM r/w access to RTP task's .data, .bss without disabling hardware MMU
Jay
sections (volatile var/const) of RTP applications for Model-In-The-
Loop testing using XCP over Ethernet protocol.
Using a (default) Flat Memory Model...
Writing a test DKM module, the module should be able to get the
loaded .data, .bss base address of a running task, and configure the
MMU / TLB? to allow the test DKM r/w memory access to the .data
sections of the RTP without a hardware exception being raised by the
MMU.
This should be done without disabling the hardware MMU, to maintain
the benefits of MMU memory protection, and ideally should give the
test DKM only r/w access to the requested .data sections, not r/w
access to all memory space. Currently, with the MMU enabled, the DKM
causes an Access Violation exception when it tries to read any data
owned by a running RTP. I also do not have a reliable method for
getting the loaded .data, .bss base address for a running RTP task.
Can anyone point me in the right direction for:
1) Code sample / Function calls for getting the .data,.bss base
address, size of a running task?
2) Code sample / Function calls for adding above RTP .data, .bss
address space to DKM module MMU memory view context for read/write
access.
---
DKM : Downloadable Kernel Module
MMU : Memory Management Unit
RTP : Real Time Process
TLB : Translation lookaside buffer
XCP : Universal Calibration Protocol
Jay
Platform: VxWorks 6.7, WindRiver Workbench 6.1
Target: VxSim (SIMNTdiab) for testing on WinXP
PPC32 Final Hardware