Skip to main content

Switching ATtiny core

I was not getting reliable I2C communication between the D1 mini and the ATtiny85, starting with TinyWireS, then moving on to the more developed TinyWire. I would send out 5 bytes from the D1 mini, then try to get 16 bytes back. It will start off well, but a few hours later, something will break and the D1 mini will start getting 0xFFs from the ATtiny85.

Then I found "ATtinyCore" by Spence Konde (V1.1.5), which appears to be a more mature ATtiny core compared to the "attiny" core by David Mellis (V1.0.2). It has integrated I2C support that manifests as the familiar "Wire" library. The installation instructions are here. I did a manual upgrade to the latest git version as some I2C issues have been fixed in the V1.1.6 milestone but have not been officially released. As recommended by the instructions, I bumped up the Arduino version to 1.8.6.

Finally, happy to see reliable I2C communication between the 2 components! The communication has been going non-stop for 2 days now, with 1-minute interval between the send/receiving of messages.

From the D1 mini end, the I2C master code is:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
  byte outbuf[5];
  outbuf[0] = random(128); for (int i=1; i<sizeof(outbuf); i++) outbuf[i] = outbuf[0] + (i*2);
  Wire.beginTransmission(I2C_SLAVE_ADDR);
  int rc = Wire.write(outbuf, sizeof(outbuf));
  Wire.endTransmission();
  debug("Wire.write (%d): %X %X %X %X %X", rc, outbuf[0], outbuf[1], outbuf[2], outbuf[3], outbuf[4]);

  byte inbuf[15];
  Wire.requestFrom(I2C_SLAVE_ADDR, 15);
  Wire.readBytes(inbuf, 15);
  Serial.print("Wire.readBytes: ");
  for (int i=0; i<sizeof(inbuf); i++) { Serial.print(inbuf[i], HEX); Serial.print(' '); } Serial.println(' ');

From the ATtiny85, the corresponding I2C code is:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
volatile byte msg[5], out[15];

void requestEvent() {
  Wire.write(out, 15);
}

void receiveEvent(uint8_t numbytes) {
  if (numbytes > sizeof(msg)) return;
  int idx = 0;
  while(idx < numbytes) {
    if (Wire.available()) 
      msg[idx++] = Wire.read();
  }
  out[0] = numbytes;
  for (int i=1; i<sizeof(out); i++) out[i] = msg[(i-1) % numbytes];
}

For testing purposes, the D1 mini sends out 5 random bytes, and the ATtiny85 basically copies the received message into the outgoing buffer, with the first byte being the length of the received message (should be always '5').

I found that the maximum number of bytes that can be sent by each requestEvent() is 15 (one less the default value of TWI_RX_BUFFER_SIZE in Wire\src\USI_TWI_Slave\USI_TWI_Slave.h. That could be increased to 32, or 64 (powers of 2 up to 256, as noted in the comment). A workaround will be for the master to make multiple requestFrom() calls, and for the slave to keep track of which block of 15 bytes to send out in requestEvent().

ESPCLOCK1 / ESPCLOCK2 / ESPCLOCK3 / ESPCLOCK4
Labels:

Comments

Post a Comment

Popular posts from this blog

Hacking an analog clock to sync with NTP - Part 5

This is how it looks after I have put everything together. The Arduino sketch is available here . The 2 jumper wires soldered to the clock mechanism are connected to pins D0 and D1 on the ESP-12 (in any order). When the device first boots up, it presents an access point which can be connected to via the PC or smartphone. Once connected, the captive portal redirects the web browser to the configuration page:     A custom field has been added to the WiFi configuration page to enter the current clock time in HHMMSS format. Try to set the clock time to as close to the current time as possible using the radial dial at the back of the clock so the clock will have less work to do catching up. In the config page, the HTML5 Geolocation API is also used to obtain your current location (so if your web browser asks if you would like to share your location, answer "yes"). This is then passed to the Google Time Zone API to obtain the time and DST offset of your time z...
23 comments
Read more

Cooling mod for the X96 Air #2

Previously, I added a USB cooling fan to the X96 Air TV box . The problem with this mod is that the fan is always running, and it runs at full speed. Ideally, the fan should kick in only when the CPU temperature is above a certain threshold. It would be even better if there is a way to control the fan speed. Dan McDonald left me a comment pointing to his project on Github . He basically connected the fan to a USB relay that can be controlled by Python script. His project inspired me to make a similar mod that would make use of the spare D1 Mini boards I have lying around. The plan is to hook up the fan to a MOSFET (2N7000) and control it via PWM. Here's the very simple circuit: The code simply reads a single character from the serial port (0 - 9). 0 will turn the fan off, while 1 - 9 will generate a proportional PWM to drive the fan, with 1 being the lowest and 9 being the highest. Here's the Arduino code: #include <Arduino.h> void setup () { Serial . begin ( 9600 ...
1 comment
Read more

Installing and customizing CoreELEC in X96 Air

I previously installed CoreELEC on another TV Box ( Ugoos X3 Pro ), which unfortunately died after only 9 months during the summer (due to the unit overheating, which I learned is a common problem for cheap Android TV boxes). So this time I purchased a X96 Air  (4GB/32Gb) and had to do the whole thing again. So this is a note-to-self in case I ever have to install CoreELEC again on some other device. Installation of CoreELEC is simple enough by following this guide . Basically, it involves downloading and writing the firmware to a microSD card using usbimager . Then insert the microSD card, reset the unit and hold the reset until the logo appears. The unit will then proceed to boot into CoreELEC. First thing is to connect to WiFi, then enable SSH. This allows me to login via ssh and execute: ceemmc -x from the terminal. This writes CoreELEC to the built-in eMMC storage, after which I am able to remove the microSD card and reboot the unit into CoreELEC via the built-in sto...
Post a Comment
Read more