You can use the latest EDK if you don't enable any of the new features in MicroBlaze.
Each new feature that is added to MicroBlaze is by default disabled.
This is to ensure that we can be 100% backward compatible.
The changes in GCC for MicroBlaze has been to fix bugs.
Shawn Tan Ser Ngiap wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 17 September 2004 09:32, John Williams wrote:It's probably possible, but why? Pre-3.x versions of EDK were pretty sketchy, certainly the mb-gcc that came with those releases has too many bugs to successfully build a kernelAw.. that's not good...Perhaps if you can explain what you are trying to achieve, there might be a better solution?I've built a verilog model of the MB and I am going to release it on OpenCores.. It would be nice to be able to run uClinux on it.. At the moment, it's tested by running assembly codes that are compatible with EDK2.1.. I've run through each instruction at least once.. So, I know that it works with EDK2.1 codes.. It would be nice to be able to run a 'open' OS on an 'open' chip as well.. that's what I figured..Regards, John- -- with metta, Shawn Tan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBSnm3UgUYbQRKphMRAkxsAJ45rxVtYwbJyKhI8RTuINEvrbWxpwCfUa4z CyWmw6eFXRdv4NJI4U0We3Q= =JjiE -----END PGP SIGNATURE----- ___________________________ microblaze-uclinux mailing list firstname.lastname@example.org Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/