--- Quote Start ---
I'm pretty sure the dev tree isn't populated in "free standing" applications. The issue of not populating system.h is an odd one. Each and every device that Nios II's read master is connected to should be "seen" there. I've seen issues when using bridges in the past. Posting your Qsys file might help a bit.
Also, you might consider generating a BSP using the SBT (software build tools) from the command line. It may give you a better idea of what's happening.
Cheers!
slacker
--- Quote End ---
Thanks Slacker.... I can switch to the command line but went the GIU route with Exlipse since I figured that may be easier.
I went to "free standing" application as I thought that was necessary to have the system.h generated and to have the alt_main as the entry point to set various things up such as the device list.
It is a worry if the dev tree isn't populated in "free standing" mode since I would need it to get the open of /dev/dma_0 to work . If this is correct do I need an OS similar to go ahead with DMA and the HAL ?
I would expect the DMA to have NIOS II as a read master since it has memory mapped registers.
I will post the QSYS file since it is a sample application and has no protected IP in it yet
When IO tried to attach top.qsys I got error "invalid file type"
I know the .pdf that went through the NIOS II example has a GUI section as well as a command line section ... can you give me a rough outline on what each command line step does .
Thanks in Advance.
Honored Contributor
