--- Quote Start ---
I typically work from the command line so I forget where it is but a debug profile would normally contain -O0 optimization (i.e. no optimization). For that updated code that polls for 9 to be read back from memory try making the 'j' variable volatile, regardless of whether optimizations are enabled or not that should prevent the loop from being removed.
Also are you sure your both processors are actually running code? Each CPU should have it's own BSP (can't have them both sharing read/write, heap, and stack regions) so you should be able to run them independent of eachother to make sure they execute code properly up to a certain point. Once that's verified then you can download the code as a multi-download group (whatever it's called in the IDE). I normally find it easier to coordinate multiple processor downloads from the command line like this:
nios2-download -i 0 -g <elf1.elf>
nios2-download -i 1 -g -r <elf2.elf>
nios2-terminal -i 0
nios2-terminal -i 1
The -i lets you pick which Nios II JTAG debug module/JTAG UART you are using. The -g tells nios2-download to start executing code and -r means reset the target. Normally I open one terminal window per command shell so that I can watch the output of all the processors at the same time.
--- Quote End ---
Yes I'm using same things: command lines
I put j as volatile but I've always same problem, Nios2 read a false value from the shared memory
Honored Contributor
