--- Quote Start ---
originally posted by badomen@Aug 9 2004, 12:10 PM
if you have a lot of look up tables why not store them into a secondary memory location (like flash for example) and make sure that it does not get reset everytime you dump new software out onto the board (i.e. allocate the memory yourself).
also what kind of times are we talking here, anything under a minute i would say is acceptible (anything more means you just need to be checking your work more and reducing the number of compiles like hardware developers do (i think you can guess what i do)). --- Quote End ---
Look up tables was an example, not saying that's what I've used it for. The problem is that using either the serial or parallel port from my point of view is far too slow, I'm used to fast speeds, i.e download in a couple of seconds max, a minute would absolutely kill me! Very rarely do you get routines right first time, compile, debug, fix, compile, debug, fix etc - if it takes a minute to download only to find an error 10 seconds later then it's incredibly frustrating. Hardware guys I'm guessing generally don't have thing problem because they're able to simulate, but I'm stuck with using real hardware.
The first test app I did on Nios I "included" a whole load of data into the code, because that was most convenient, I was working with a number of different pieces of data and had rather large executables, consequently if I used the "nios-run" command I could go off, have a nap, wake back up, read a magazine and still find that it hadn't finished downloading!
Upon realising that the "default configuration" of the board ran a web server that let you upload code revolutionised my life, it took less than a second to upload and start executing my code.
I'd personally love to see a feature like this because from my point of view it makes massive sense, it's not as if the stub would be hard to implement, the only complexity would be integration into eclipse, which i'm sure would be doddle.
Each to their own though!
Adrian