Update DS-019 Pixhawk versions and revisions.md

[vincentpoont2]

Add Holybro FMUv6x rev8 sensor set.

The current sensor set is getting outdated so we would like to add a new sensor set that replace the current Rev3/4.

[vincentpoont2]

@mrpollo @davids5 Can we proceed with this?

[mrpollo]

@davids5 can you confirm this is available and viable?

[davids5]

@davids5 can you confirm this is available and viable?

It is. We have allocated quite a few for HB. We need to look at using the EEPROM for the Next HB sensor set.

[vincentpoont2]

@davids5 can you confirm this is available and viable?

It is. We have allocated quite a few for HB. We need to look at using the EEPROM for the Next HB sensor set.

What are the steps to use the EEPROM?

[vincentpoont2]

@davids5 Since there are still a few open allocation, can we proceed with the REV8 for this one? We have prototype hardware ready.

At the moment, we are unfamiliar with the steps to use EEPROM. We can review the steps to use EEPROM and if we have another REV in the future, we can certainly use the EEPROM for that.

[davids5]

@davids5 can you confirm this is available and viable?

It is. We have allocated quite a few for HB. We need to look at using the EEPROM for the Next HB sensor set.

What are the steps to use the EEPROM?

The HW resisters on the FMUM are set to Code point 7. (R1 46.4K and R2 84.5K A code point is reserved from above 0x10 (say 0x1009) it is marked | EEPROM | Holy Bro Rev 9 Sensor Set | In production the IMU board's EEPROM is loaded with the information here. Drone Code will provide you a tools to do this this.

[davids5]

@davids5 Since there are still a few open allocation, can we proceed with the REV8 for this one? We have prototype hardware ready.

Yes

At the moment, we are unfamiliar with the steps to use EEPROM. We can review the steps to use EEPROM and if we have another REV in the future, we can certainly use the EEPROM for that.

[vincentpoont2]

@mrpollo Please merge

[mrpollo]

Thanks @davids5 @vincentpoont2