--- Quote Start ---
HAL is just a set of code that has drivers, file system, interrupt handler functions. It can be used in an OS but it does not need it to run. I am not sure if you can re-write the interrupt handler, if the NIOS II interrupt handler is too slow. Some else may know that answer.
--- Quote End ---
spooky.... i dont need drivers or file system. so why do i need the hal ? get rid of it. if i can read and write memory thats all i need. i dont need 'printf' and all that other stuff.
--- Quote Start ---
If you want to read/write to any device or port you can use IOWR/IORD macros in "io.h" header.
--- Quote End ---
i noticed those as well but that makes the program look very strange.
instead of doing this :
a = a + 1
you'd have to do
a = ioread ( adress_of_a)
a = a+1
iorwite adress_of_a ,a )
that is just plain stupid.
--- Quote Start ---
Your lack of knowledge on how the tool works is building your frustration.
--- Quote Start ---
fully correct. these tools are completely different than what i am used to ( Keil , Raisonnance , IAR , Intel) The problem is i am pressed for time. I've got 5 engineers breathing down my neck. If i have a person next to me that know the tools and i can explain what i want to do it would take 1 hour to set it up and write the skeleton code. I will never in my life deal with that stuff again. I'm not interested in becoming a tool guru . I just need an environment so i can concentrate on the job i need the cpu to do. I'm not interested in knowing how to set up the environment. That should be done by the people making the tool.
It's like learning how to drive a car. I buy a car from intel or atmel or motorola or arm. A Vendor like Keil and IAR gives me the key and lends me a person to teach me how to drive. you also get a phone number you can call if you have trouble figuring something out.
Altera gives you a box of assorted parts. ( some of them you don't even need ) . A book on how a combustion engine works . a 10.000 page manual on how to assemble a car .... and if you have a problem : feel free to ask your neighbour ... we don't know and can't be bothered.
That's what it feels like.
--- Quote Start ---
C is the most portable language in the world. Your code will compile for NIOS II, it just may not the way you want it to. Evey CPU is different
--- Quote End ---
no n the first statement. yes on the second.
if i write this
int a _at_ 0x1000
int b _at_ 0x1001
a = b +1;
and send this through the Keil compiler for an 8051 the code it will perform as intended
If i send the same code through the compiler for an ARM it will do exactyl the same thing.
take the contents of memory location 0x1001, add '1' to it and drop the result in 0x1000
If i send it to the compiler from IAR it will also compile without a hitch.
if i send it through GCC the compiler barfs ands says :surry bub but i dont know what _at_ means....
that's what i mean.
Honored Contributor
