This is the mail archive of the
ecos-bugs@sources.redhat.com
mailing list for the eCos project.
[Bug 1000134] New: Not a working ecm file for Adder board!
- From: bugzilla at ecoscentric dot com
- To: ecos-bugs at sources dot redhat dot com
- Date: Tue, 18 Jan 2005 16:10:43 +0000 (GMT)
- Subject: [Bug 1000134] New: Not a working ecm file for Adder board!
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000134
Summary: Not a working ecm file for Adder board!
Product: eCos
Version: 2.0
Platform: adder (A&M Adder PPC850 board)
OS/Version: HostOS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: high
Component: ConfigTool
AssignedTo: jld@ecoscentric.com
ReportedBy: joc@home.se
QAContact: ecos-bugs@sources.redhat.com
I'm trying to build a RedBoot bin file for A&M Adder board using first template
for A&M Adder then importing a ecm file (under ...packages/hal/powerpc/adder/misc).
I get redboot.bin file and burns it to a flash card. But nothing seems to be
working....
I have also tried to test the srec file for adder (found in the CVS) but I
coudn't get it to work either.
I have tried to swap the binary file as well.
Please, help me!
What am I doing wrong??!!
My ecm file:
cdl_savefile_version 1;
cdl_savefile_command cdl_savefile_version {};
cdl_savefile_command cdl_savefile_command {};
cdl_savefile_command cdl_configuration { description hardware template package };
cdl_savefile_command cdl_package { value_source user_value wizard_value
inferred_value };
cdl_savefile_command cdl_component { value_source user_value wizard_value
inferred_value };
cdl_savefile_command cdl_option { value_source user_value wizard_value
inferred_value };
cdl_savefile_command cdl_interface { value_source user_value wizard_value
inferred_value };
cdl_configuration eCos {
description "" ;
hardware adder ;
template redboot ;
package -hardware CYGPKG_HAL_POWERPC v2_0 ;
package -hardware CYGPKG_HAL_POWERPC_MPC8xx v2_0 ;
package -hardware CYGPKG_HAL_POWERPC_ADDER v2_0 ;
package -hardware CYGPKG_HAL_QUICC v2_0 ;
package -hardware CYGPKG_DEVS_FLASH_POWERPC_ADDER v2_0 ;
package -hardware CYGPKG_DEVS_FLASH_AMD_AM29XXXXX v2_0 ;
package -hardware CYGPKG_DEVS_ETH_POWERPC_QUICC v2_0 ;
package -hardware CYGPKG_DEVS_ETH_POWERPC_ADDER v2_0 ;
package -template CYGPKG_HAL v2_0 ;
package -template CYGPKG_INFRA v2_0 ;
package -template CYGPKG_REDBOOT v2_0 ;
package -template CYGPKG_ISOINFRA v2_0 ;
package -template CYGPKG_LIBC_STRING v2_0 ;
package -template CYGPKG_NS_DNS v2_0 ;
package -template CYGPKG_CRC v2_0 ;
package CYGPKG_IO_FLASH v2_0 ;
package CYGPKG_IO_ETH_DRIVERS v2_0 ;
};
cdl_option CYGFUN_LIBC_STRING_BSD_FUNCS {
inferred_value 0
};
cdl_option CYGNUM_HAL_COMMON_INTERRUPTS_STACK_SIZE {
user_value 4096
};
cdl_option CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT {
user_value 0
};
cdl_option CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM {
inferred_value 0
};
cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
inferred_value 1
};
cdl_option CYGSEM_HAL_ROM_MONITOR {
inferred_value 1
};
cdl_component CYG_HAL_STARTUP {
user_value ROMRAM
};
cdl_component CYGBLD_BUILD_REDBOOT {
user_value 1
};
cdl_option CYGBLD_REDBOOT_MIN_IMAGE_SIZE {
user_value 0x00030000
};
cdl_option CYGOPT_REDBOOT_FIS_REDBOOT_BACKUP {
user_value 0
};
cdl_option CYGSEM_REDBOOT_FLASH_COMBINED_FIS_AND_CONFIG {
user_value 1
};
cdl_option CYGBLD_ISO_STRTOK_R_HEADER {
inferred_value 1 <cyg/libc/string/string.h>
};
cdl_option CYGBLD_ISO_STRING_LOCALE_FUNCS_HEADER {
inferred_value 1 <cyg/libc/string/string.h>
};
cdl_option CYGBLD_ISO_STRING_BSD_FUNCS_HEADER {
inferred_value 1 <cyg/libc/string/bsdstring.h>
};
cdl_option CYGBLD_ISO_STRING_MEMFUNCS_HEADER {
inferred_value 1 <cyg/libc/string/string.h>
};
cdl_option CYGBLD_ISO_STRING_STRFUNCS_HEADER {
inferred_value 1 <cyg/libc/string/string.h>
};
cdl_option CYGBLD_ISO_DNS_HEADER {
inferred_value 1 <cyg/ns/dns/dns.h>
};
cdl_option CYGPKG_NS_DNS_BUILD {
inferred_value 0
};
cdl_option CYGHWR_DEVS_FLASH_AMD_AM29LV320D {
inferred_value 1
};
Is it possible to get a working ecc file to see what has been set up.
Best Regards
Carin
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.