JeeLib I think only needs the SPI pins and associated h/w for communication with the RFM69CW radio module via SPI. Without any change, there were compile-time errors in two locations - one in the JeeLib function which was using the variable "timer0_millis" for everything other than #define ( AVR_ATtiny84/85/44/45) and another place in my code where the code to readVcc was written for ATTiny84 and was using _BV(MUX0).Īfter I modified the JeeLib to use "millis_timer_millis" when #define( AVR_ATtiny88), and replaced the code for reading Vcc on ATmega328 (I am assuming the same code would work for ATT88), it compiled without errors. While I haven't yet programmed the ATT88 IC with my sketch, I was able to compile it without errors. Your suggestions and information was most useful. I'd appreciate if you can point to an obvious down-side of using ATmega328p compared to ATT88/84 - particularly in terms of power consumption.įinally, is there anything obvious in the library code I am using that I can look for to find out if Timer/Counter2 is used? The library itself is here: GitHub - jeelabs/jeelib: JeeLib for Arduino IDE: Ports, RF12, and RF69 drivers from JeeLabs. It at least has much wider support from the community. If they don't, then my thinking is that I am better off moving to ATmega328p IC itself. The reason for trying on ATT88 is because (a) it has more I/O pins which I need on remote units and low power consumption, (b) has everything else that I think I need, and (c) I have a few ATT88 ICs with me - so if they work for me, I'll like to use them. I guess, without know more internal details of the library itself, I just have to try my luck and see if it works on ATT88. In case it gives a clue, I have tested the library on ATTiny84 and Arduino UNO. Not sure if the library I use (JeeLib) uses Timer/Counter2. Hence looked for a MCU with more I/O I don't need to use the crystal oscillator. Thanks I have used ATTiny84, but am running out of I/O pins.
0 Comments
Leave a Reply. |