More warnings on the EEPROM write screen + Blog V4 default EEPROM config

🙋 If you want a new feature or a change to the software then add your request here.

If it's not here then it's not going to happen.
rtlsdrblog
Posts: 1
Joined: Mon Jun 03, 2024 9:10 am

More warnings on the EEPROM write screen + Blog V4 default EEPROM config

#1

Unread post by rtlsdrblog »

Hi, this is rtlsdrblog, I manufacture the RTL-SDR Blog V3 and V4.

The V4 requires that the EEPROM have the manufacturer string be set to "RTLSDRBlog" and the product string be set to "Blog V4" for the librtlsdr drivers to differentiate between the RTL-SDR Blog V4 R828D model, and generic R828D RTL-SDR models.

One issue I'm seeing increasingly often is SDR-Console users who have corrupted their EEPROM strings on the RTL-SDR Blog V4. What some people are doing is seemingly randomly clicking around in the SDR-Console EEPROM GUI and overwriting the EEPROM strings. It seems that some people don't understand that they are doing a hardware write operation as the most common thing people say is that they were simply experimenting with SDR-Console and clicking on buttons to see what they do.

Is it possible to add more warnings about using this feature? At the same time is it possible to please add a Blog V4 default configuration that writes the correct default manufacturer and product ID strings? So at least people who messed up their EEPROM can easily revert it to working order without having to use rtl_eeprom on the command line.

Thanks

Post Reply