~snip~
I never heard of HulkOS before but the image shows the wrong sensor type and then calibrate temp sensor failed.
Is this only happen in chain 1 or does all hashboard have the same error?
What steps that you already tried? Did you recently replace the miner with a new hashboard without a code editor or Pickit?
If you already tried changing PSU as suggested above and if this is not a hardware issue then can you try dumping the PIC firmware from the other 2 known working hashboard and then flash it to this hashboard(chain 1)?
Don't forget to dump the PIC firmware first from (chain 1) just in case you can revert it back to its original state.
This firmware is developed by us privately. It is currently in the public testing stage. This is the built-in maintenance mode of the firmware. It only supports testing one computing power board at a time, similar to the official maintenance fixture, so my log is only testing one computing power board, this board is a normal operating computing power board
When I was analyzing this problem, I kept trying to start the test program, and I often reproduced the problem that the temp_sensor could not be read. I analyzed the log and found that it would initially read the component model of the temp_sensor, and the hardware used was NCT218. , if it is read correctly, then he will work normally, if the identified component model is inaccurate or not read, then he will replace the identified model with the default TMP451, then he will not be able to calibrate Temp_sensor Get the correct parameters, resulting in a temperature reading error and an error
This test log is the result of testing under the same machine
If it is read correctly, it will prompt:
temp_sensor_type=26 is NCT218
If it is not read correctly, then he will prompt:
temp_sensor_type=0 then he will set this temp_sensor as TMP451 by default
NCT218=type26
TMP451=type0
Also, our firmware does not depend on the PIC firmware in the EEPROM chip attached to the PIC chip. We directly issue the operating frequency of the asic chip and the power supply voltage of the PSU from the hulkos firmware, which completely bypasses the problem of the PIC, and the frequency and voltage are dynamically adjusted, so even if the PIC chip is not flashed with firmware, or our three-chip computing power The PIC information of the board is not uniform, and our hashboard can still work normally, so it has nothing to do with the PIC, which simplifies the work difficulty of on-site operation and maintenance personnel. To a certain extent, you can understand that hulkos automatically sends the PIC program to the hashboard to run