Hi all,
I've looked through all the archived posts that mention the
Relocation truncated to fit: R_ARM_PC24
and any mention of
__attribute__ (section(
in the hope of finding any hint as to why I'm failing to link with the
above relocation error.
I'm trying to ensure that a
Ok, solved it myself :)
It seems that the functions that you put in sections need to be in a
separate source file.
Unfortunately the relevant code seems to remain in flash...does the
linker place the section in ram or is it simply providing a convenient
label for Redboot to use to relocate from
On Mon, Sep 19, 2005 at 01:54:43PM +0100, Matt Sartori wrote:
Hi all,
I've looked through all the archived posts that mention the
Relocation truncated to fit: R_ARM_PC24
and any mention of
__attribute__ (section(
Take the intel Strata as an example:
int
Hi Gary and Andew,
I can see what the issue is, but I do not know how to solve. From my dsr I
call:
while ( !(pDevCtrl-rxBds[pDevCtrl-rxHeadIndex].status DMA_OWN)
(sc-funs-eth_drv-recv)(sc, pDevCtrl .);
this loops through as long as packets are coming and I checked from
eth_drv.c
Perhaps I'm missing the point here, but when faced with an instance of a
consisently full queue, I have been taught to investigate the process(es)
that are to service that queue.
Given the limiting factor of 100 frames /sec. one can pretty much rule out
CPU cycle saturation as the root problem
1. In the configtool, what is the difference between save and export, and
what is the difference between load and import?
2. What is the difference between a .ecc file and a .ecm file?
I haven't found good answers to these questions in the docs.
- Andy
--
Before posting, please read the
Hi guys,
I need to know how to increase the ip stacking processing priority. I
played around with following entries but no luck so far:
Priority level for background network processing
Priority lvel for fast network processing.
Again upon enqueueing the packets, the ipintr is NOT called to
