Honored Contributor
Honored ContributorI'm pretty sure you're going to want to go the no mmu route for now. If you don't know that you need it, that's your answer.
--- Quote Start --- actris: ...when i tried to customize the kernel myself i just changed to custom_fpga --- Quote End --- I'm not sure that this is necessary. As far as I understand, this is taken care of by the "make vendor_hwselect ..." command. (but I could be wrong) However, I do know that command is necessary, otherwise the tool has no idea what the hardware looks like and can't build the image appropriately. I am also using Ubuntu 9.10 and Quartus 9.1 and found that I could not use the pre-built toolchain. I didn't know why, but I just moved on and built it. I have done this before with previous versions of Ubuntu and Quartus (for a design for the Candian Altera design competition - 3rd place), but I, too have run into a problem with this new configuration (that it seems you have overcome). Once the image is built, I cannot load it onto the board using "nios2-download -g ..." which is a Quartus tool. I'm pretty sure this is not a problem with the build, but a problem with the load(er) [version incompatibility? I'm not sure yet] because it doesn't even work with the images provided by the wiki. Yes, the jtagconfig shows a jtag cable. Yes, I've selected the cable, etc. scilattji: since we're having problems on the same OS (what version of Quartus are you using?), I thought we could help each other out. Maybe you could provide your *.ptf file and I could see if I could get it to build on my system? Meanwhile, you could build the toolchain and see if that works. I also found a guy who has a vmware image of a fully functional/tested system, so I'm going to try that. What do you think? *EDIT* Actually, I was thinking that you may want to try to build the image for one of the examples on the wiki first. You know that those are 'working' ptf files, so this would be a good next step before you build the toolchain.
