vxWorks_romCompress

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

I've encountered a problem on a 32-bits 133MHzMIPS platform with
Tornado2.2
I use the Tornado project environment to generate the run-time image
"vxWorks_romCompress".  It's 1Mbytes in size.  I burn it onto my 2M
Flash memory.  But after I started the system only this:

////////////////////////////////////////////////////////////

Attached TCP/IP interface to motfec unit 0

Atta
////////////////////////////////////////////////////////////
printed on the terminal.  Then system is dead.

I think there may be something wrong with the Ram address allocation.
Because a 9Mbytes- application compressed with the BSP and VxWorks,
that can run successfully in standalone mode.

My application is 13Mbytes in archive form. I think maybe there is
something wrong when uncompress the code to the Ram. The address
allocation is:

    --------------  0x02000000 = RAM_SIZE = RamTop
    |            |
    |            |
    |            |
    |            |
    |            |
    | ROM image  |
    |----------- |  0x01C80000  = RAM_HIGH_ADRS
    |            |
    |            |
    |            |  
    |            |
    |            |
    |            |
    |------------|            
    |            |  0x00001000  = RAM_ADRS & RAM_LOW_ADRS
    |            |
    |            |  exc vectors, bp anchor, exc msg, bootline
    |            |
    |            |
    --------------  0x00000000  = LOCAL_MEM_LOCAL_ADRS

But i don't know the uncompression process of "VxWorks_RomCompress",
and the position of the uncompressed code in RAM.

So could you tell me what is the problem?

Or could you tell me more about the uncompression process of
"Vxworks_RomCompress".

THANKS A LOT.

Site Timeline