This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
rc@unusus.com wrote:
Don't use the official release. It's obsolete, and only there because we haven't yet put together a package that replaces some of the things the installer provides (but eCosCentric are actively working on this!).Hi all, Can somebody indicate a combination of GNU tools, eCos snapshot and MPC860 HAL that is known to be working properly together (preferably under cygwin environment), so I can have a good starting point for my custom HAL (BSP)? I want to port eCos to a MPC860 custom designed board. As the “HAL Platform Porting Process” document says (http://sources.redhat.com/ecos/docs-latest/porting/hal-plf-process.html) it is easier to start from an existing HAL. Unfortunately I was not able to find a combination of eCos release/snapshot, GNU tools and MPC860 HAL that compiles OK. The official release (1.3.1)
in the documentation (gcc-2.95.2, binutils-2.10.1 + recommended patches) willRedBoot/cygmon were never ported to fads. The stubs should work though. Any more detail on the error.
compile OK the “fads860 default” target, but not the stubs or any other target
involving the stubs (RebBoot or cygmon).
You are on Windows, and this is a line ending problem. I guess this might have been your problem with building for stubs.I also noticed a preprocessor problem with gcc-2.95.2: it does not understand macros that are extending on more than 1 line. Like in this example: #define MACRO_TEST(a, b){\ a+=b;\ } This can be an inconvenient if you have to port existing code that uses this type of macros.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |