Hello.
I have found that it fails in hal/arm/arch/current/src/hal_misc.c at void
breakpoint(void).
When i execute
void
breakpoint(void)
{
diag_printf("breakpoint\n");
HAL_BREAKPOINT(_breakinst);
diag_printf("breakpoint\n");
}
The second trace doesn't appear and the target reboot.
When i try to compile
void
breakpoint(void)
{
diag_printf("breakpoint %p\n", _breakinst);
HAL_BREAKPOINT(_breakinst);
diag_printf("breakpoint %p\n", _breakinst);
}
I have hal_misc.c:230: error: `_breakinst' undeclared (first use in this
function)
(i use, now gcc 3.4.3 from gnuarm).
I go on my investigations...
Andrew Lunn wrote:
On Mon, Jan 14, 2008 at 02:53:02PM +0100, Paul Chavent wrote:
Andrew Lunn wrote:
Lets try something simple. Connect to RedBoot over the serial
port. Send it a $ character. Does it crash and reboot, or does it just
go silent?
$ is the magic character that tells RedBoot to send characters to the
stub.
If it does not reboot, reboot it and send
$m0,10#2a
which i think is a valid command to read 10 bytes from address 0. Any
response or a reboot?
Andrew
Damned ! It reboots !
So look in packages/redboot/current/main.c. Put in some diag_printf()
before the HAL_THREAD_INIT_CONTEXT and HAL_THREAD_SWITCH_CONTEX calls.
Check the values of workspace_end, breakpoint, trampoline etc.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
