Hi Gary, thanks for your quick response.
Here are the following dumps: RedBoot> fconfig -l edBoot> fconfig -l Run script at boot: true Boot script: Boot script timeout (1000ms resolution): 0 Use BOOTP for network configuration: true Default server IP address: 10.10.1.10 Console baud rate: 115200 DNS server IP address: 10.10.1.10 Network hardware address [MAC]: 0x7C:0x71:0x43:0xA6:0x7C:0x92 GDB connection port: 9000 Force console for special debug messages: false Network debug at boot time: false RedBoot> fis list Name FLASH addr Mem addr Length Entry point RedBoot 0xFF800000 0x00100000 0x00040000 0x00100000 RedBoot config 0xFFFE0000 0xFFFE0000 0x00010000 0x00000000 FIS directory 0xFFFF0000 0xFFFF0000 0x00010000 0x00000000 RedBoot> This is the actual configuration with the latest RedBoot loader which I run, and as you can see above the actual baudrate is configured with 115200 and bootp=true BUT actually I am connected with terraterm on baudrate=9600 and I didn't get an ip address from my DHCP/BOOTP server assigned, if I "reboot" with the "old" bootloader everything works fine. Maybe your suggestion about the different partition location is true, but then how can I change it ??? Marc -----Ursprüngliche Nachricht----- Von: Gary Thomas [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 09. August 2006 16:44 An: Marcello Presulli Cc: ecos-discuss@ecos.sourceware.org Betreff: Re: [ECOS] RedBoot config parameter mismatch Marcello Presulli wrote: > Hi all, > > i have the following situation: > > If I run my board (opus103) with the "original" RedBoot loader the > config parameters (fconfig -l) like > baudrate=115200,bootp=true and so on are recognised correctly while > booting, > but when I flash my board with the latest RedBoot loader then the > RedBoot config parameters are not > recognised (e.g. baudrate=9600,bootp=false) even if I reinitialise the > config section with fconfig -i again. Your description is a bit vague. Maybe you could show the output from RedBoot which describes the problem you are seeing. One thing that could be different is that your original version was built with the fconfig data in a separate FIS image [partition]. The default is to combine this with the FIS directory. If this is the case, the new RedBoot will be looking for its fconfig data in a different place than the old one. -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
