T17 not hashing after update to new frimware

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

Quote from: sfmolavi on November 06, 2020, 07:38:53 AM

i updated to lasted version

Try custom firmware, custom means non-bitmain, try Asic.to or BraiinOS see if the miner behaves any differently, although since you upgraded to the latest version this won't be easy, not sure if the Sdcard method will work anymore.

Code:

2020-11-06 12:18:09 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 27 asic, times 0
2020-11-06 12:18:41 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 18 asic, times 0
2020-11-06 12:19:32 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2

under normal circumstances, I would say all 3 boards are dead because they don't see 30 Asics which is the normal asic count for T17, but since this only happened after the firmware upgrade (if I understood you correctly) then I would think that the firmware is causing the issue.

favebook

sr. member

Activity: 604

Merit: 416

Is it ambient temperature 29C? Is it working now on latest version?

Also, what happened before your unit stopped hashing, was it all of a sudden all three hashboards stopped mining? Was there a power surge or maybe storm during that day? Did you change anything right before your unit stopped mining? Have you cleaned it maybe before maybe?

sfmolavi

newbie

Activity: 4

Merit: 0

thank u for answering. i updated to lasted version. here is not cold temp=29 c.

favebook

sr. member

Activity: 604

Merit: 416

Hello, seems like you are loosing connection with chips. A good sign is that it is still recognising whole chains and some chips, that means that it likely isn't a big problem like loose heatsinks.

I'd suggest you to download a custom firmware or at least update to latest one from Bitmain due to this:

Quote

1. Enhance the working stability of the miner under special conditions (e.g. a certain range of low or high ambient temperature environment).

I am assuming it's cold now in your country as it is in mine. If that is the case, they might not be easy to run in cold ambient temperatures. What I had to do to make my S17+ run is this:

My Z11 is heating up my S17+ hashboards which makes them run perfectly. As soon as I move my Z11 away from intake of S17+, it loses one or sometimes even two hashboards. I'd suggest you to try the same or at least heat up them before turning on.

sfmolavi

newbie

Activity: 4

Merit: 0

Hi there. plz help me to solve this problem. i flashed with SD card but nothing changed.

Code:

2020-11-06 12:17:01 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-11-06 12:17:04 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-11-06 12:17:06 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-11-06 12:17:09 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-11-06 12:17:11 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-11-06 12:17:15 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-11-06 12:17:15 thread.c:880:create_pic_heart_beat_thread: create thread
2020-11-06 12:17:15 power_api.c:55:power_init: power init ... 
2020-11-06 12:17:15 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-11-06 12:17:15 power_api.c:46:power_off: init gpio907
2020-11-06 12:17:47 power_api.c:264:set_iic_power_to_custom_voltage: setting to voltage: 18.00 ...
2020-11-06 12:17:52 power_api.c:124:check_voltage_multi: retry time: 0
2020-11-06 12:17:54 power_api.c:86:get_average_voltage: chain[0], voltage is: 19.305967 
2020-11-06 12:17:56 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.430371 
2020-11-06 12:17:57 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.387510 
2020-11-06 12:17:57 power_api.c:97:get_average_voltage: aveage voltage is: 18.707949 
2020-11-06 12:17:57 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 18.000000 
2020-11-06 12:17:58 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-11-06 12:18:09 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 27 asic, times 0
2020-11-06 12:18:19 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 27 asic, times 1
2020-11-06 12:18:29 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 27 asic, times 2
2020-11-06 12:18:29 driver-btm-api.c:1069:check_asic_number: Chain 0 only find 27 asic, will power off hash board 0
2020-11-06 12:18:41 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 18 asic, times 0
2020-11-06 12:18:51 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 18 asic, times 1
2020-11-06 12:19:01 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 18 asic, times 2
2020-11-06 12:19:01 driver-btm-api.c:1069:check_asic_number: Chain 1 only find 18 asic, will power off hash board 1
2020-11-06 12:19:12 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-11-06 12:19:22 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-11-06 12:19:32 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-11-06 12:19:32 driver-btm-api.c:1069:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-11-06 12:19:33 driver-btm-api.c:205:set_miner_status: ERROR_SOC_INIT
2020-11-06 12:19:33 driver-btm-api.c:146:stop_mining: stop mining: soc init failed!
2020-11-06 12:19:33 thread.c:930:cancel_read_nonce_reg_thread: cancel thread
2020-11-06 12:19:33 driver-btm-api.c:131:killall_hashboard: ****power off hashboard****

Topic: T17 not hashing after update to new frimware (Read 149 times)