From fca113c3734a7a02da3270bb9b2cbee501511a33 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Fri, 26 Sep 2003 20:23:35 +0000 Subject: 2003-09-26 Till Straumann PR 497/bsps * BOOTING: Document letting the bootloader shut down the network interface since it continues to run after loading RTEMS application and has to be dealt with. --- c/src/lib/libbsp/powerpc/motorola_powerpc/BOOTING | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) (limited to 'c/src/lib/libbsp/powerpc/motorola_powerpc/BOOTING') diff --git a/c/src/lib/libbsp/powerpc/motorola_powerpc/BOOTING b/c/src/lib/libbsp/powerpc/motorola_powerpc/BOOTING index 5565fbb2b3..a8e58c3f27 100644 --- a/c/src/lib/libbsp/powerpc/motorola_powerpc/BOOTING +++ b/c/src/lib/libbsp/powerpc/motorola_powerpc/BOOTING @@ -6,6 +6,24 @@ This file documents the on board monitor (PPCBUG) configuration used to be able to boot the archives located in powerpc-rtems/c/mcp750/bin. This information was provided by Eric Valette +NOTE (by Till Straumann , 2003): +Apparently, PPCBug fails to shut down the network interface after +loading an image. This means that the ethernet chip is still able +to write into its descriptors and network buffer memory which +can result in the loaded system to be corrupted if that system +relocates itself!. The proper place to shut down the interface +would be PPCBug itself or a 'PPCBug startup script' - unfortunately, +PPCBug doesn't offer such a feature. Therefore, the bootloader +is by default compiled with the +#ifdef USE_PPCBUG +compile-time option ENABLED. It will then use a PPCBug system +call to shut down the ethernet chip during an early stage of +the boot process. +NOTE: THIS (i.e. the system call) WILL FAIL IF YOU USE SOFTWARE +OTHER THAN PPCBUG TO BOOT THE BSP. In such a case, you must +recompile with #undef USE_PPCBUG and make sure the ethernet +interface is quiet by other means. + ----------------------- ENV command-------------- PPC1-Bug>env Bug or System environment [B/S] = B? -- cgit v1.2.3