longcall probelm (RE: was MVME2304 Exception 3 )

[Till Straumann]

Try the attached patch - it provides SBRK. This should enable you to
load modules until the first 32M are exhausted. SBRK will then release the
rest of your memory to the system but after that happens modules cannot
be loaded anymore.

HTH

-- Till

Kate Feng wrote:

>Paul D Jines wrote:
>
>  
>
>>>>>The error I got while loading the object code is :
>>>>>
>>>>> "Relocation of type 'R_PPC_REL24' failed: The relocation was
>>>>>          
>>>>>
>>performed,
>>    
>>
>>>>> but there was an overflow (check compiler flags!)"
>>>>>
>>>>>          
>>>>>
>>>I  wonder  if Paul ever got this error message in loading >his object
>>>      
>>>
>>code.
>>
>>I don't recall seeing that message.
>>
>>    
>>
>
>Paul, which version of GeSys did you use ?  I got the same error message
>with the three versions of GeSys that Till posted on the WEB.  Did
>you use cexpModuleLoad() to load your object code (eg.
>cexpModuleLoad("telnetd.obj")) ?  If so, could you please
>send me a copy of your telnetd.obj and the compilation process/flags?
>
>  
>
>>>What is Paul's status now ?
>>>Did Paul get the MVME2304-0143 working with the  version
>>>Till build for  his  exception 3 diagnosis ?
>>>      
>>>
>>By using the NBH/manually shutting down the network
>>method that Till describes, everything works.  (Another
>>thing that complicated our situation was a buggy terminal
>>emulator.)
>>
>>    
>>
>>>>No - I suppose the exception 3 occurs (spuriously) because
>>>>PPCbug's NBO command fails to shut down the ethernet interface.
>>>>Therefore, the ethernet chip could still DMA when RTEMS is
>>>>already executing (memory that were PPCbug's network buffers
>>>>are now used by RTEMS).
>>>>        
>>>>
>>>I have not gotten exception 3 with  the MVME2306 (32Mb) >lately,
>>>and not yet with the MVME2304-0141 (128MB) board.   I think
>>>you might be right about the NBO command.  I rarely got the
>>>exception 3 with the  MVME2306 in the past.  It seems that >it went
>>>away lately.
>>>      
>>>
>>One of the things that Till suggested that we try on our
>>board during the diagnosis was to reset the memory size to
>>32MB.  When we did that, things worked, even without
>>resetting the network interface....
>>
>>    
>>
>
>Do you mean to change the "memory ending size" from 08000000
>to 02000000 via the  ppc-BUG "env" command ?  I still get the same
>error message (not the exception 3 but the relocation overflow)
>by doing that.  The sysem always return the message:
>"Residual-Data Located at: $07F88000".
>
>
>Till, I  am looking at a vxworks-longcall.patch submitted by someone
>for the PPC2.95.3, it mentioned that it is only valid for the
>SysV/EABI calling convention.  I recall  an excerpt of your cexp README
>"when compiling loadable modules, the compiler's -msdata flag must not be
>
>set to either of 'eabi', 'sysv' or 'use'. If you try to load code
>compiled with
>an improper -msdata setting, you will get a
>'Relocation of unsupported size/type requested' error. I do not
>know if I am wasting time on barking the wrong tree about the longcall.
>
>
>Thanks,
>Kate
>
>
>
>  
>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mvme23xx-sbrk.diff
URL: <http://lists.rtems.org/pipermail/users/attachments/20030918/2fb70010/attachment-0001.ksh>