Hi Thomas and Marius,
Thomas Chen wrote:
> i am using an OKI chip that has remaping capability (ie maping memory page
> to bank 0).... and it is pretty tricky... you have to build/link with the
> linker setting.... questions is where is your armboot running from????
> RAM??? FLASH??? did you somehow mess up the stack on the way of
> switching??? i have seen this a few times before, mostly due to the memory
On power up the FLASH is located at 0x0, after a basic hardware init running
from FLASH, I copy the bootloader from FLASH to RAM - run the remapping code -
then jump to the start_armboot in RAM (at 0x800004a4). The thing that makes
this confusing is, after remapping the same RAM exists at both 0x80000000 and
0x0. So I guess the problem could be in the remapping activities. Would you
suggest trying to run in the remapped bootloader - ie not jumping to 0x80000000
but staying at 0x0? Also do where do you locate the kernel in you OKI setup?
Thanks for responding.
> location error and overwritting something
> for example, my system (OKI) starts out by mapping the FLASH to bank 0,
> so i am executing nicely from location 0x000x xxxx area, and then when i do
> the remapping, i have to make sure the PC is jump to 0xc80x xxxx and not
> continuing the 0x000x xxxx
> Matt Waddel wrote:
>>I have been working on an armboot port to a custom board
>>and I am down to one last problem that is driving me crazy.
>>The gunzip portion of a bootm command crashes.
>>It is a uClinux project with 2M of flash and 8M of RAM. I
>>have downloaded an uncompressed copy of the kernel+filesystem
>>to memory and executed successfully. All the user apps I
>>have tried seem to work correctly also.
>>It is a ARM940T based system, that remaps the flash and the
>>RAM early in the boot procedure. The flash starts at 0x0
>>then gets remapped to 0x20000000, RAM starts at 0x80000000
>>and gets remapped to 0x0. I install the kernel and filesystem
>>I create the target image using the following parameters:
>>./armboot-1.0.2/tools/mkimage -A arm -O linux -T standalone \
>>-C gzip -a 40000 -e 40000 -n uClinux -d image.bin.gz image.pkg
>>When I run the following bootm command it crashes during the
>>inflate command in zlib.c:
>># tftp 400000 image.pkg
>># bootm 400000
>>## Booting image at 00400000 ...
>>Image Name: uClinux
>>Image Type: ARM Linux Standalone Program (gzip compressed)
>>Data Size: 1262609 Bytes = 1233 kB = 1 MB
>>Load Address: 00040000
>>Entry Point: 00040000
>>Verifying Checksum ... OK
>>Uncompressing Standalone Application ... data abort
>>pc : [<80009f74>] lr : [<e1a0c00d>]
>>sp : 80035b34 ip : 1e71a953 fp : 00000000
>>r10: 00404888 r9 : 00000000 r8 : 00000000
>>r7 : 00000001 r6 : 00050150 r5 : 80035bd0 r4 : 00045f60
>>r3 : 00000002 r2 : 0004934d r1 : 00126960 r0 : 00000000
>>Flags: nzCv IRQs off FIQs off Mode SVC_32
>>Resetting CPU ...
>> ### ERROR ### Please RESET the board ###
>>If I change the value of the dstlen in the call to gunzip
>>it won't abort, but it still won't boot so I know that's not
>>the correct solution.
>>Anybody else seen this problem? Suggestions would be appreciated.
>>This sf.net email is sponsored by: Jabber - The world's fastest growing
>>real-time communications platform! Don't just IM. Build it in!
>>ARMboot-users mailing list