<div class='quotetop'>QUOTE </div>
--- Quote Start ---
I would like to use the “new” HAL and not the old SDK, but changing the sample project from the Nios I is not very easy.[/b]
--- Quote End ---
You don't need to use the HAL (although we reccomend it). In the "more CPU settings page" of SOPC Builder, just check the legacy SDK box and fill out the fields as you did in the Nios I CPU -- then you get an SDK folder just like the old days. This is being provided for people who are moving Nios I systems to Nios II and don't want to change their software. The disadvantage of staying with the legacy SDK is that we don't provide the fancy IDE for it, and the /f version of the CPU core is not officially supported due to cache coherency issues (that is, you may have to modify your old software a bit to make it write-back cache compatible, although most software will work fine on the /f CPU with legacy mode).
The app note on upgrading Nios I --> Nios II contrasts the differences between legacy SDK and HAL, and has a little section describing the tool-flow of the legacy SDK (most utilities just have a "2" in them, nios2-build for example). If you do want to stay with HAL, this document also has a big table of the legacy SDK-specific function calls and some suggestions of how to replace them with HAL/ANSI C equivalents.