Re: Migration from 4.2 to 5.0

Sounds like a config.bib problem. You must ensure that the memory you use
for your image is *physically* contiguous. For example, if you have two RAM
banks, most likely only one can be used to run your image (only one can be
used with the RAMIMAGE section in config.bib).

--
Dean Ramsier - eMVP
BSQUARE Corporation


"TaN" <TaN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:116F31F3-5EEF-4C71-BC7A-21EACD18DB8B@xxxxxxxxxxxxxxxx
> Hi,
>
> I am migrating a 4.2 PXA 255 BSP/drivers to 5.0. I have removed the GWE
> from
> my platform, though I have added the 'minimal GWES' sysgen and NLED sysgen
> variable from the catalogue. There are just the display, battery, touch
> panel
> divers included. On downloading, the following errors throw up on the
> serial
> port:
>
> ERROR! XIP region span accross discontigious memory!!! System Halted!
>
> OEMGetExtensionDRAM, no upper bank detected
>
> Sp=ffffc7cc
>
> DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions at
> (Driver
> s\BuiltIn\AFD). Driver cannot be unloaded.
>
> DeviceFolder::LoadDevice!Enumerate
> Fou
> nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver cannot be
> unloa
> ded.
> NLedDriverInitialize: Create File errorGteCurrentLEDState:
> DeviceIoControl I
> OCTL_DMHID_GETLED failedPrefetch Abort: Thread=83aeb5a0 Proc=820b5a50
> 'gwes.exe'
>
>
> AKY=00000009 PC=02be9000(mstscax.dll+0x00079000)
> RA=03f8c6b0(coredll.dll+0x0001c
> 6b0) BVA=02be9000 FSR=000004f0
>
> SA2VIDEO: IOCTL_POWER_CAPABILITIES
>
> NLedDriverInitialize: Create File errorLedOff: DeviceIoControl
> IOCTL_DMHID_SETLE
> D failed
>
> I have removed the entries to the platform.gen and platform.bib for the
> nled driver,but still cant get thru this.
>
> Could somebody please help. Thanks in advance.
>


.

Relevant Pages

  • Re: Ram Card Design Help
    ... 32k banks actually are pretty bad. ... 16/48 will work OK for MP/M, but if one wants to implement CP/NET ... extensions and need to be completely in common memory. ... For CP/M 3 any scheme works and it doesn't matter. ...
    (comp.os.cpm)
  • Please help with following NUMA-related questions
    ... Difference between memory bank interleaving and node interleaving ... AUTO allows memory access to spread out over banks on the same node or across ...
    (Linux-Kernel)
  • Re: FBDIMM vs DIMM - any compatibility?
    ... measurably faster if all four channels have the same size of memory on ... performance through interleaving. ... branches can have different banks open, ... each channel will slow you down to the tune of about 5 ns per DIMM ...
    (comp.arch)
  • Re: [PATCH] Mantaining turnstile aligned to 128 bytes in i386 CPUs
    ... block copy then to have an inner per-PAGE loop. ... and/or memory systems are remarkably sensitive to bank interleave. ... accidentally starts up with perfect miscoloring for banks. ... the coloring becomes random with respect ...
    (freebsd-current)
  • Re: I Should Surrender to Opteron
    ... but instead a very high-speed path to external memory. ... type of cache that scalar CPUs rely on to get some performance. ... same memory banks at the same time - vector machines have thousands of ... Which recent machines have thousands of banks? ...
    (comp.arch)