03-21-2006 04:22 PM
03-21-2006 04:23 PM
I forgot to mention.
Development environment: Tornado 2.0.2
Target environment: Vxworks 5.4
thanks again
jim
03-23-2006 10:11 AM
03-23-2006 01:29 PM
03-23-2006 02:42 PM
03-27-2006 09:48 AM
Mark,
thanks for the information.
We did some of the byte swapping but not all of it. We're going to try that.
As for the initial setting of the memory stuff, it is required, otherwise the test program breaks a lot earlier.
the calls also isolate the values in sysLib.c away from the actual implentation..
We'll check in later.
Jim
02-21-2010 08:47 PM
to
National Instruments Engineer
You said "need to add a couple of entries to sysPhysMemDesc[ ] in sysLib.c":
/* PCI-GPIB - PBAR0 */
{
(void *) <BAR0 address>,
(void *) <BAR0 address>,
0x1000,
VM_STATE_MASK_VALID | VM_STATE_MASK_WRITABLE |
VM_STATE_MASK_CACHEABLE | VM_STATE_MASK_GUARDED,
VM_STATE_VALID | VM_STATE_WRITABLE | VM_STATE_CACHEABLE_NOT |
VM_STATE_GUARDED
},
/* PCI-GPIB - PBAR1 */
{
(void *) <BAR1 address>,
(void *) <BAR1
address>,
0x4000,
VM_STATE_MASK_VALID | VM_STATE_MASK_WRITABLE | VM_STATE_MASK_CACHEABLE |
VM_STATE_MASK_GUARDED,
VM_STATE_VALID |
VM_STATE_WRITABLE | VM_STATE_CACHEABLE_NOT | VM_STATE_GUARDED
}
If there is something defined as follow:
#ifdef INCLUDE_PCI
,
{
(void *) PCI_MEM_ADRS,
(void *) PCI_MEM_ADRS,
PCI_MEM_SIZE,
VM_STATE_MASK_VALID | VM_STATE_MASK_WRITABLE | VM_STATE_MASK_CACHEABLE | \
VM_STATE_MASK_GUARDED | VM_STATE_MASK_MEM_COHERENCY,
VM_STATE_VALID | VM_STATE_WRITABLE | VM_STATE_CACHEABLE_NOT | \
VM_STATE_GUARDED | VM_STATE_MEM_COHERENCY
}
,
{
(void *) PCI_MEMIO_ADRS,
(void *) PCI_MEMIO_ADRS,
PCI_MEMIO_SIZE,
VM_STATE_MASK_VALID | VM_STATE_MASK_WRITABLE | VM_STATE_MASK_CACHEABLE | \
VM_STATE_MASK_GUARDED | VM_STATE_MASK_MEM_COHERENCY,
VM_STATE_VALID | VM_STATE_WRITABLE | VM_STATE_CACHEABLE_NOT | \
VM_STATE_GUARDED | VM_STATE_MEM_COHERENCY
}
,
{
(void *) PCI_IO_ADRS,
(void *) PCI_IO_ADRS,
PCI_IO_SIZE,
VM_STATE_MASK_VALID | VM_STATE_MASK_WRITABLE | VM_STATE_MASK_CACHEABLE | \
VM_STATE_MASK_GUARDED | VM_STATE_MASK_MEM_COHERENCY,
VM_STATE_VALID | VM_STATE_WRITABLE | VM_STATE_CACHEABLE_NOT | \
VM_STATE_GUARDED | VM_STATE_MEM_COHERENCY
}
Whether is needed your suggestion?
02-23-2010 04:42 AM
The problem is ok!