• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 22 subscribers
  • Views 1262 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Nordic chip, what number are the interrupts?

Christian Wilhelmsen

Hi!

I'm new to 8051 controllers and are now using the nRF24LE1 for a school project.

I am used to the AVR architecture and writing interrupts like "ISR_interrupt_vector()" but I can see that 8051 uses "void interrupt() interrupt #number", and I can not find what #number to use.

Can anyone help me with this issue?

Thank you all in advance!

Parents
  • 0 in reply to Andy Neil

    "...assembly, something I'm not comfortable with"

    I strongly suggest that you need to get confortable with it at least to the level of being able to follow the simple examples in things like the 8052.com tutorials.

    Most of those examples are just about writing to & reading from SFRs - which is has no real differences in 'C' or ASM.

    You don't necessarily need to be able to write your own assembler - but you should really be able to follow simple examples.

    I second the motion

    in the non-OS world you will be at a great disadvantage if you can not read assembler comfortably.

    Just an example: a missing 'volatile' is blatantly obvious looking at the generated assembler and invisible in C. There are many more examples where your debugging will be greatly hampered by "assembly, something I'm not comfortable with".

    Erik

Reply
  • 0 in reply to Andy Neil

    "...assembly, something I'm not comfortable with"

    I strongly suggest that you need to get confortable with it at least to the level of being able to follow the simple examples in things like the 8052.com tutorials.

    Most of those examples are just about writing to & reading from SFRs - which is has no real differences in 'C' or ASM.

    You don't necessarily need to be able to write your own assembler - but you should really be able to follow simple examples.

    I second the motion

    in the non-OS world you will be at a great disadvantage if you can not read assembler comfortably.

    Just an example: a missing 'volatile' is blatantly obvious looking at the generated assembler and invisible in C. There are many more examples where your debugging will be greatly hampered by "assembly, something I'm not comfortable with".

    Erik

Children