From acb51aeda3f8f1f743be419d43ec1000b2a1f721 Mon Sep 17 00:00:00 2001 From: David Sidrane Date: Thu, 10 Aug 2017 09:18:14 -1000 Subject: [PATCH] rgbled:Updated comment, removing reference to PX4FMUv1 Comment expressly referenced PX4FMUv1, but the EEPROM, could be used on any board. --- src/drivers/rgbled/rgbled.cpp | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/src/drivers/rgbled/rgbled.cpp b/src/drivers/rgbled/rgbled.cpp index 7a82260d86..1bbb6f5daf 100644 --- a/src/drivers/rgbled/rgbled.cpp +++ b/src/drivers/rgbled/rgbled.cpp @@ -189,12 +189,11 @@ RGBLED::probe() /** this may look strange, but is needed. There is a serial - EEPROM (Microchip-24aa01) on the PX4FMU-v1 that responds to - a bunch of I2C addresses, including the 0x55 used by this - LED device. So we need to do enough operations to be sure - we are talking to the right device. These 3 operations seem - to be enough, as the 3rd one consistently fails if no - RGBLED is on the bus. + EEPROM (Microchip-24aa01) that responds to a bunch of I2C + addresses, including the 0x55 used by this LED device. So + we need to do enough operations to be sure we are talking + to the right device. These 3 operations seem to be enough, + as the 3rd one consistently fails if no RGBLED is on the bus. */ unsigned prevretries = _retries;