I used to say that, but so much of the really nice libraries are supplied in C. USB, Ethernet, anything for the 16bit or 32bit PICs
Thanks to 3V0 I've been learning C18 (my old brain cells are fighting learning a new thing)
Only real gripe is C was invented almost 60yrs ago and it feels like something designed for punch cards and UNIVAC.
thank you for your replays Nigel Goodwin & blueroomelectronics ,
I have a question, how can I send ,via PIC's output ports, hundreds of ns (nano seconds) timing frames (Attached Thumbnails in one of my lasts posts) ?
should I use timers and prescalers to get this short cycles or is it possible by another way ?
thank you for your replays Nigel Goodwin & blueroomelectronics ,
I have a question, how can I send ,via PIC's output ports, hundreds of ns (nano seconds) timing frames (Attached Thumbnails in one of my lasts posts) ?
It won't, C is probably too slow and clumsy for such short timings - with C you probably wouldn't need any delays at all - the code itself would delay enough.
It's an old Parallax app note on interfacing dynamic RAM with the ancient 16F54 using the obscure CVASM assembler (I used to love this assembler). Might give you some insight.
It's an old Parallax app note on interfacing dynamic RAM with the ancient 16F54 using the obscure CVASM assembler (I used to love this assembler). Might give you some insight.
The nS delays are all less than a single assembler NOP, any C instructions are going to be longer than that - so there's no problem about exceeding the minimum times.
The nS delays are all less than a single assembler NOP, any C instructions are going to be longer than that - so there's no problem about exceeding the minimum times.