Re: eCos application offset for Redboot load
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On 8/8/2011 5:51 PM, Gary Thomas wrote:
On 2011-08-08 17:25, gmail wrote:I am trying to build an eCos application (and the test suite) to load onto a board with a Redboot monitor.I've created an xxx_ram.ldi / .h for the board but don't know if I need to add in the offset in that file for the Redboot monitor or if that is done elsewhere.The monitor indicates: Platform: TS-7250 Board (ARM920T) Rev A Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc. RAM: 0x00000000-0x02000000, [0x000530c0-0x01fdd000] available FLASH: 0x60000000 - 0x68000000, 1024 blocks of 0x00020000 bytes each. Do I change the text base in the .ldi to something above 0x000530c0?Yes, e.g. 0x80000 would be suitable.
Thanks. I am now hitting another issue that doesn't make sense...While stepping through one of the test programs w/ gdb, in the vectors.S file hal_hardware_init is being called which in turn calls hal_mmu_init() which looks like is halting the program.
If I am trying to run a program loaded into ram via redboot, shouldn't the hardware (or at least the MMU) initialization be skipped? Isn't it going to wipe out RAM?
Thanks for listening... :-) --JJ-- -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss