Author

Topic: Antminer S9 SE Troubleshooting (Read 317 times)

jr. member
Activity: 51
Merit: 16
January 16, 2024, 09:03:27 PM
#23
With forced air I had one inline 6" duct fan rated at 345 CFM in the enclosure inlet side. Now I have two inline fans running at maximum. I have settled on a design so the enclosure has two air tight chambers to separate the cool air intake from the hot air exhaust.

I did a battery of tests today but when the APW7 voltage was dropping I could tell it was bad. If I'm not mistaken the PSU should maintain a voltage of 11.9 - 12.9 even with all three hash boards powered.

I listed the tests in order of which I performed them.

Note:
The voltage is measured at a power jack that is not being used.

APW7 PSU:

Ambient temp 15C

No hash boards: 12.04v
Test 1 - Chain# 1: Elapsed 45 min., 60 ASICs, 5630GH/S (avg), didn't measure voltage
Test 2 - Chain# 1,2: Elapsed 10 min., 120 ASICs, 0GH/S (avg), 8.07v
Test 3 - Chain# 1,3: Elapsed 10 min., 120 ASICs, 0 GH/S (avg), 8.20v
Test 4 - Chain# 2,3: Elapsed 20 min., 120 ASICs, 0 GH/S (avg), 7.60v
Test 5 - Chain# 2: Elapsed 32 min., 60 ASICs, 3,430GH/S (avg), 9.69v
Test 6 - Chain# 3: Elapsed 36 min., 60 ASICs, 3,232GH/S (avg), 9.54v
Test 7 - Chain# 1: Elapsed 1h 5 min., 60 ASICs, 0GH/S (avg), 8.65v

Chain Force Cannon PSU (2000W) - Model LL2000MINI:

Ambient temp 15.6C

No hash boards: 12.25v
Test 1 - Chain# 1: Elapsed 23 min., 60 ASICs, GH/S 5,707 (avg), didn't measure voltage
Test 2 - Chain# 1,2: Elapsed 23 min., 120 ASICs, GH/S 11,423 (avg), 12.23v
Test 3 - Chain# 1,2,3: Elapsed 4 min., 180 ASICs, GH/S 16,432 (avg), didn't measure voltage

Yup. It's the power supply. So the miner works fine I suppose, not perfect, but it works. it's just trying to keep it cool and have at least a PSU that works.
I think the APW7 I have is pretty much trash, so i'll have to return it.
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
January 09, 2024, 03:28:08 AM
#22
I would simply detach the center board from the 3 power jacks. Mine ran well for years like that.

That would certainly help cool the miner by a lot, unlike removing the hashboard altogether because that would mess with the airflow since air would pass easily through the no-resistance without removing enough heat.

The middle board is the best one to unplug especially given that it is the one that is subject to fail before the other two because of the stupid design on these miners where the front chips of the middle board are right behind the fan motor getting too little airflow.
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
January 08, 2024, 08:06:27 PM
#21
To be able to enable the fan control follow the guide by mikeywith posted from the link below once you enable it try to run it at 85% or higher and let see any changes on the hashboard temp and it should help to cool down a bit your unit.

If he gets temp errors then setting static fan won't help him, the miner would push the fan to it's limit or closet to it before sending any warning, and thus mean, his miner has already tried what you are suggesting but it still failed to operate at reasonable temp, what he should do instead if

1- provide better airflow.
or
2- underclock the miner.

it has been a while since I worked with an S9 SE, but if he follows my guide that you linked to unlock the hidden settings, it's possible to find clock and voltage settings which he can play with.

I would simply detach the center board from the 3 power jacks. Mine ran well for years like that.
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
January 08, 2024, 12:16:18 PM
#20
To be able to enable the fan control follow the guide by mikeywith posted from the link below once you enable it try to run it at 85% or higher and let see any changes on the hashboard temp and it should help to cool down a bit your unit.

If he gets temp errors then setting static fan won't help him, the miner would push the fan to it's limit or closet to it before sending any warning, and thus mean, his miner has already tried what you are suggesting but it still failed to operate at reasonable temp, what he should do instead if

1- provide better airflow.
or
2- underclock the miner.

it has been a while since I worked with an S9 SE, but if he follows my guide that you linked to unlock the hidden settings, it's possible to find clock and voltage settings which he can play with.
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
January 06, 2024, 03:22:37 PM
#19
Two hashboards will work, but I was running in to a problem of the miner over heating. Probably not enough air flow and I'm trying to solve that problem with adding more forced air.

What do you mean by adding forced air you mean by adding an extra fan in front of the unit intake fan?

I think based on your previous post the unit is not running at top speed.
If you want to run the fan at top speed you need to enabled the fan control it's hidden and you can't find this option on the WebGUI.

To be able to enable the fan control follow the guide by mikeywith posted from the link below once you enable it try to run it at 85% or higher and let see any changes on the hashboard temp and it should help to cool down a bit your unit.

- https://bitcointalksearch.org/topic/m.53945847
jr. member
Activity: 51
Merit: 16
January 05, 2024, 03:01:47 AM
#18
The differences in hashboards is interesting and would make sense.

I will definitely have to do more testing and look for that drop in voltage if there is one, which there might be when I have all three powered. I'm just glad I don't have to buy a $500 3000 watt PSU to get it to work.

Two hashboards will work, but I was running in to a problem of the miner over heating. Probably not enough air flow and I'm trying to solve that problem with adding more forced air.

I hope it's not the wires, but it could be the adapter, especially if the wires have sharp bends after tightening the housing of the adapter down. Damn. Which means I should buy a new power cable without an adapter and try that.
The wires used to install that subpanel were 10/3 Romex with ground, fed from a 30 amp circuit, but the same 10/3 gauge wire is also attached to the 15 amp breakers and might need to be changed to 14 to get the correct size for the breakers to detect overloads and for the receptacles. The power cable I bought for the miner is 14 AWG, which is correct for 15 amps.
So yeah, there could be multiple contributing factors.
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
January 04, 2024, 04:30:40 PM
#17
Fifth test, powering the 1st and middle hash board using jacks 1-6 hashed at an AVG of 10,694 GH/S in 2 min. Jacks tested at 12.07V.
So if it looks consistent the PSU being the fault

I wouldn't rush to replace the PSU just yet, this could be a mix and match issue between the 3 hashboards although the kernel log states that they are all of the same exact type, but to be 100% that is not the problem you are going to have to try a few combinations

You already tried 1 and 2 so you know they mix well.
You need to try 1 and 3, if they mix well, then you know 2 and 3 can also mix.

Then you want to do one last test, with all 3 hash boards on boards just measure the output of the PSU, you may want to open the top cover so have easy access to the leads (be extra careful tho).

the reason why you need to do this test is the fact that you reported all 9 jacks output >12DC which means they all are fine, so it's possible that the PSU fails only when on-load, if you see voltage drop somewhere, then you can be sure it's a bad PSU.

It's also possible that your AC voltage (input side) drops at some point due to the adapter you using or the wires feeding that socket being to small for the current.

So is there a way to get all three hash boards running? Would a 3000 watt PSU do it? Current one is 1800 watts.

NO! 3000w PSU is too much for the S9 SE, it's just a waste of money, anything above 1500w is going to be more than enough.
jr. member
Activity: 51
Merit: 16
January 04, 2024, 02:23:40 PM
#16
So is there a way to get all three hash boards running? Would a 3000 watt PSU do it? Current one is 1800 watts.
jr. member
Activity: 51
Merit: 16
January 01, 2024, 09:03:15 PM
#15
You guys were right on the nose.

Here's pic to sum it up.


I labeled all the unplugged power jacks "1"-"9" before starting.

Preliminary test, I first tested all 6 leads of all 9 power jacks, just to make sure they all read the same and there's no broken leads. They all tested at 12.05V.

Second test, powering the 1st hash board with jacks 1-3 assumed bad hashed at an AVG of 5529 GH/S in 7 min. The jacks tested at 12.08V.

Third test, powering the middle hash board with jacks 6-8. Previously hashed with a very low hash rate, of only a few hundred GH/S, this test it hashed at an AVG of 5511 GH/S in 5 min. Jacks 1-4 tested at 12.08V and all the others tested at 12.07V

Fourth test, powering the 3rd hash board with jacks 4,5,9 assumed bad hashed at an AVG of 5701 GH/S in 2 min. Jacks tested at 12.07V.

Fifth test, powering the 1st and middle hash board using jacks 1-6 hashed at an AVG of 10,694 GH/S in 2 min. Jacks tested at 12.07V.

So if it looks consistent the PSU being the fault, I could replace the PSU. If there is a PSU that can supply power all 3 hash boards. Or just live with using only two and keep one stored away as a replacement part.

I did look at the kernal log while doing this and I still saw that CPU 1 failed to boot.

But I'm really happy with this test that the hash boards do work. Thank you for helping.

So from here would a new kernal log help?
jr. member
Activity: 51
Merit: 16
January 01, 2024, 06:16:51 PM
#14
I'm gonna get started on the testing.
Something else though, just to make sure is not a factor. What about the length and gauge of the power cable going to the PSU? From the 220v receptacle to the PSU.

I'm using an 6-15P adapter.
https://www.amazon.com/dp/B07SZLMCSR?psc=1&ref=ppx_yo2ov_dt_b_product_details
Which I spliced to an already existing 6-15P to C13 cord
https://www.amazon.com/dp/B07MCN2B7J?ref=ppx_yo2ov_dt_b_product_details&th=1

I made sure the connections were tight. I used the 90 degree adapter cause I felt it would put less strain and pulling on the cord coming out from the receptacle.
The adapter does not have the backstab quick connect, cause I have heard they have poor connection which can lead to arcing and fire. It has the straight blade wiring which I've heard has even a better, tighter connection than a shepherds hook.
The cord is currently at 10 feet cause I didn't know how much I needed, but there is a possibility I can trim 3-4 feet.
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
January 01, 2024, 12:20:32 PM
#13
So testing a PSU looks pretty straight forward, just probe the leads for 12v DC, plus or minus a half volt and it should be ok if it falls in those parameters, right?

testing the psu is best done on a fully working unit as it will draw enough amps.

you can test a psu on an s9 by just plugging in the controller. and make sure  all white info cables connect to hash boards.

the fans will run. and you will have nine unplugged leads.

just see if a few of the lead cables are over 11.9 volts. first test.

if you are 11.9 to 12.9 good.

shut gear off.

plug three leads into 1 board.

fire it up 🆙. test a few leads  to see if you are at 11.9 to 12.9 volts.

I suspect one of two issues weak psu or some poor boards that draw to much current.


So at this point you have 1 controller and 1 board hook up 🆙.
 if it all runs you know that board is good. and you still are not sure of the psu.

power off. unplug just the one working board say on the left.

all white info cable stay plugged in.

now plug in the three jacks to the center board.

run a while and see if it works. if it works you know that it is a good board.


shut gear done

do the same for third board. if it works all three boards are good.

an you likely have a weak psu.

next series of tests are try boards left side and center .


see what happens.

if it is a weak psu you may notice a drop in volts.

many of the psus can do 1 or 2 boards but not 3.

or some times 1 board is shitty and draws a lot of power.

you have the worst s9 model that has had the worst record of not working well.

but I suspect we can get one or two boards working. on it.


jr. member
Activity: 51
Merit: 16
January 01, 2024, 11:22:38 AM
#12
So testing a PSU looks pretty straight forward, just probe the leads for 12v DC, plus or minus a half volt and it should be ok if it falls in those parameters, right?
jr. member
Activity: 51
Merit: 16
January 01, 2024, 11:09:14 AM
#11

very typical of the 9k.

board 0 looks bad

board 1 looks good

board 2 looks bad..

each board has 1 white info cable leave them in

each board has 3 power six pin jacks.

pull the power cables out on the left board.
leave the white info cables in run for  a bit.

check the hash .

post the logs.

If you are lucky we can get two of the boards to work

I think we certainly will get one board to work.

I think all three working will not happen
I think all three not  working will hot happen.

I had eight of the 9k units 2 worked great the other 6 would allow only two boards to work.

bitmax could be correct.

but you are feeding 240 and that psu if weak may do 2 of 3 boards.

Also sorry, I swore I left a post saying I would be out for the night. A little bit later I'll start the tests cause I'm really curious. So take the power cables off of the first hashboard and leave the data cables in? I also might look up how to test PSUs for faults.
jr. member
Activity: 51
Merit: 16
January 01, 2024, 10:58:09 AM
#10
What things have you already done so far?

According to your logs, it seems the issue is related power supply.

Would you mind to try test the hashboard one by one?
What I guess is PSU is running abnormally.

What, really? Both PSUs? That makes me think there's a problem with the wiring (by wiring I mean the house wiring and power cables). But I tested the voltage and ground and it all seems normal. Yeah I will have to try some different powering methods with the baseboards.
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
December 31, 2023, 07:00:50 PM
#9
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
December 31, 2023, 06:58:28 PM
#8
What things have you already done so far?

According to your logs, it seems the issue is related power supply.

Would you mind to try test the hashboard one by one?
What I guess is PSU is running abnormally.
jr. member
Activity: 51
Merit: 16
December 31, 2023, 06:14:59 PM
#7
okay s9 k sucks 


but let me see the second part.

I have a good idea of what is wrong.

I have a bit of a cooldown between posts.

2 of 2:
Code:
...(continued)


bring up chain 0
2023-12-31 21:33:09 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2023-12-31 21:33:10 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:33:12 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 0, find asic num = 60
2023-12-31 21:33:15 driver-btm-soc.c:4816:set_freq_by_chain: chain[0] set freq:100.00
2023-12-31 21:33:16 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 0
2023-12-31 21:33:16 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:33:16 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:33:16 temperature.c:801:calibration_sensor_offset: Chain[0] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:33:17 temperature.c:801:calibration_sensor_offset: Chain[0] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:33:17 asic.c:1176:set_baud_by_chain: chain 0 set baud=1
2023-12-31 21:33:17 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:33:17 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:33:19 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:33:19 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 125
2023-12-31 21:33:22 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 150
2023-12-31 21:33:24 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 175
2023-12-31 21:33:26 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 200
2023-12-31 21:33:28 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 225
2023-12-31 21:33:30 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 250
2023-12-31 21:33:32 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 275
2023-12-31 21:33:34 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 300
2023-12-31 21:33:36 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 325
2023-12-31 21:33:39 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 350
2023-12-31 21:33:41 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 375
2023-12-31 21:33:43 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 400
2023-12-31 21:33:45 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 425
2023-12-31 21:33:47 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 450
2023-12-31 21:33:49 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:33:49 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[0] increaseing the diff freq ...
2023-12-31 21:33:49 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 0 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:33:49 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:33:50 driver-btm-soc.c:6938:re_open_core_by_chain: reopen chain 0 finished, chain 0 chip temp 30 - 67
2023-12-31 21:33:50 driver-btm-soc.c:6939:re_open_core_by_chain: all chain chip temp 30 - 88
2023-12-31 21:33:50 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[0] slowly setting to voltage: 09.50 ...
2023-12-31 21:33:51 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:33:54 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:33:55 driver-btm-soc.c:6955:re_open_core_by_chain: re_open_core done!
2023-12-31 21:33:55 dspic33ep16gs202.c:213:dsPIC33EP16GS202_pic_heart_beat: ERROR! failed on Chain[0] after 3 times try!
2023-12-31 21:34:25 driver-btm-soc.c:6911:re_open_core_by_chain:

reopen chain 1, current pwm 11
2023-12-31 21:34:27 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[1] slowly setting to voltage: 09.50 ...
2023-12-31 21:34:27 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:34:34 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:34:34 asic.c:1176:set_baud_by_chain: chain 1 set baud=26
2023-12-31 21:34:34 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 1
2023-12-31 21:34:34 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2023-12-31 21:34:35 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:34:37 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 1, find asic num = 60
2023-12-31 21:34:40 driver-btm-soc.c:4816:set_freq_by_chain: chain[1] set freq:100.00
2023-12-31 21:34:41 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 1
2023-12-31 21:34:41 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:34:41 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:34:41 temperature.c:801:calibration_sensor_offset: Chain[1] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:34:42 temperature.c:801:calibration_sensor_offset: Chain[1] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:34:42 asic.c:1176:set_baud_by_chain: chain 1 set baud=1
2023-12-31 21:34:42 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:34:42 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:34:44 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:34:44 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 125
2023-12-31 21:34:47 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 150
2023-12-31 21:34:49 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 175
2023-12-31 21:34:51 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 200
2023-12-31 21:34:53 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 225
2023-12-31 21:34:55 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 250
2023-12-31 21:34:57 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 275
2023-12-31 21:34:59 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 300
2023-12-31 21:35:01 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 325
2023-12-31 21:35:04 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 350
2023-12-31 21:35:06 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 375
2023-12-31 21:35:08 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 400
2023-12-31 21:35:10 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 425
2023-12-31 21:35:12 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 450
2023-12-31 21:35:14 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:35:14 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[1] increaseing the diff freq ...
2023-12-31 21:35:14 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 1 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:35:14 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:35:15 driver-btm-soc.c:6938:re_open_core_by_chain: reopen chain 1 finished, chain 1 chip temp 35 - 75
2023-12-31 21:35:15 driver-btm-soc.c:6939:re_open_core_by_chain: all chain chip temp 31 - 75
2023-12-31 21:35:15 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[1] slowly setting to voltage: 09.50 ...
2023-12-31 21:35:16 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:35:21 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:35:22 driver-btm-soc.c:6955:re_open_core_by_chain: re_open_core done!
2023-12-31 21:35:22 dspic33ep16gs202.c:213:dsPIC33EP16GS202_pic_heart_beat: ERROR! failed on Chain[1] after 3 times try!
2023-12-31 21:35:52 driver-btm-soc.c:6911:re_open_core_by_chain:

reopen chain 2, current pwm 5
2023-12-31 21:35:54 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[2] slowly setting to voltage: 09.50 ...
2023-12-31 21:35:54 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:36:00 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
2023-12-31 21:36:00 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:36:01 asic.c:1176:set_baud_by_chain: chain 2 set baud=26
2023-12-31 21:36:01 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 2
2023-12-31 21:36:01 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2023-12-31 21:36:02 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:36:03 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 2, find asic num = 60
2023-12-31 21:36:07 driver-btm-soc.c:4816:set_freq_by_chain: chain[2] set freq:100.00
2023-12-31 21:36:07 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 2
2023-12-31 21:36:07 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:36:08 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:36:08 temperature.c:801:calibration_sensor_offset: Chain[2] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:36:08 temperature.c:801:calibration_sensor_offset: Chain[2] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:36:09 asic.c:1176:set_baud_by_chain: chain 2 set baud=1
2023-12-31 21:36:09 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:36:09 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:36:11 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:36:11 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 125
2023-12-31 21:36:13 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 150
2023-12-31 21:36:15 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 175
2023-12-31 21:36:17 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 200
2023-12-31 21:36:19 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 225
2023-12-31 21:36:22 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 250
2023-12-31 21:36:24 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 275
2023-12-31 21:36:26 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 300
2023-12-31 21:36:28 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 325
2023-12-31 21:36:30 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 350
2023-12-31 21:36:32 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 375
2023-12-31 21:36:34 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 400
2023-12-31 21:36:36 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 425
2023-12-31 21:36:39 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 450
2023-12-31 21:36:41 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:36:41 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[2] increaseing the diff freq ...
2023-12-31 21:36:41 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 2 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:36:41 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:36:42 driver-btm-soc.c:6938:re_open_core_by_chain: reopen chain 2 finished, chain 2 chip temp 40 - 64
2023-12-31 21:36:42 driver-btm-soc.c:6939:re_open_core_by_chain: all chain chip temp 34 - 95
2023-12-31 21:36:42 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[2] slowly setting to voltage: 09.50 ...
2023-12-31 21:36:42 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:36:48 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
2023-12-31 21:36:48 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:36:49 driver-btm-soc.c:6955:re_open_core_by_chain: re_open_core done!
now setting chain[0]-volt[09.51]-data[027] chain[1]-volt[09.51]-data[027] chain[2]-volt[09.51]-data[027]
2023-12-31 21:37:21 power.c:1278:slowly_set_iic_power_voltage_t11: parallel set all chain to working voltage end!
now setting chain[0]-volt[09.50]-data[027] chain[1]-volt[09.50]-data[027] chain[2]-volt[09.50]-data[027]
2023-12-31 21:42:26 driver-btm-soc.c:6911:re_open_core_by_chain:

reopen chain 0, current pwm 13
2023-12-31 21:42:28 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[0] slowly setting to voltage: 09.50 ...
2023-12-31 21:42:29 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:42:32 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:42:33 asic.c:1176:set_baud_by_chain: chain 0 set baud=26
2023-12-31 21:42:33 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 0
2023-12-31 21:42:33 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2023-12-31 21:42:34 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:42:35 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 0, find asic num = 60
2023-12-31 21:42:39 driver-btm-soc.c:4816:set_freq_by_chain: chain[0] set freq:100.00
2023-12-31 21:42:40 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 0
2023-12-31 21:42:40 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:42:40 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:42:40 temperature.c:801:calibration_sensor_offset: Chain[0] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:42:41 temperature.c:801:calibration_sensor_offset: Chain[0] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:42:41 asic.c:1176:set_baud_by_chain: chain 0 set baud=1
2023-12-31 21:42:41 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:42:41 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:42:43 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:42:43 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 125
2023-12-31 21:42:45 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 150
2023-12-31 21:42:47 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 175
2023-12-31 21:42:49 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 200
2023-12-31 21:42:52 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 225
2023-12-31 21:42:54 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 250
2023-12-31 21:42:56 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 275
2023-12-31 21:42:58 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 300
2023-12-31 21:43:00 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 325
2023-12-31 21:43:02 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 350
2023-12-31 21:43:04 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 375
2023-12-31 21:43:06 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 400
2023-12-31 21:43:09 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 425
2023-12-31 21:43:11 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 450
2023-12-31 21:43:13 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:43:13 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[0] increaseing the diff freq ...
2023-12-31 21:43:13 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 0 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:43:13 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:43:14 driver-btm-soc.c:6938:re_open_core_by_chain: reopen chain 0 finished, chain 0 chip temp 33 - 77
2023-12-31 21:43:14 driver-btm-soc.c:6939:re_open_core_by_chain: all chain chip temp 33 - 99
2023-12-31 21:43:14 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[0] slowly setting to voltage: 09.50 ...
2023-12-31 21:43:15 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:43:18 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:43:18 driver-btm-soc.c:6955:re_open_core_by_chain: re_open_core done!
2023-12-31 21:43:18 dspic33ep16gs202.c:213:dsPIC33EP16GS202_pic_heart_beat: ERROR! failed on Chain[0] after 3 times try!
2023-12-31 21:43:48 driver-btm-soc.c:6911:re_open_core_by_chain:

reopen chain 1, current pwm 80
2023-12-31 21:43:50 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[1] slowly setting to voltage: 09.50 ...
2023-12-31 21:43:51 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:43:57 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:43:58 asic.c:1176:set_baud_by_chain: chain 1 set baud=26
2023-12-31 21:43:58 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 1
2023-12-31 21:43:58 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2023-12-31 21:43:59 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:44:00 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 1, find asic num = 60
2023-12-31 21:44:04 driver-btm-soc.c:4816:set_freq_by_chain: chain[1] set freq:100.00
2023-12-31 21:44:05 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 1
2023-12-31 21:44:05 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:44:05 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:44:05 temperature.c:801:calibration_sensor_offset: Chain[1] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:44:06 temperature.c:801:calibration_sensor_offset: Chain[1] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:44:06 asic.c:1176:set_baud_by_chain: chain 1 set baud=1
2023-12-31 21:44:06 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:44:06 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:44:08 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:44:08 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 125
2023-12-31 21:44:10 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 150
2023-12-31 21:44:12 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 175
2023-12-31 21:44:15 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 200
2023-12-31 21:44:17 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 225
2023-12-31 21:44:19 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 250
2023-12-31 21:44:21 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 275
2023-12-31 21:44:23 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 300
2023-12-31 21:44:25 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 325
2023-12-31 21:44:27 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 350
2023-12-31 21:44:29 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 375
2023-12-31 21:44:32 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 400
2023-12-31 21:44:34 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 425
2023-12-31 21:44:36 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 450
2023-12-31 21:44:38 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:44:38 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[1] increaseing the diff freq ...
2023-12-31 21:44:38 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 1 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:44:38 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:44:39 driver-btm-soc.c:6938:re_open_core_by_chain: reopen chain 1 finished, chain 1 chip temp 39 - 60
2023-12-31 21:44:39 driver-btm-soc.c:6939:re_open_core_by_chain: all chain chip temp 35 - 61
2023-12-31 21:44:39 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[1] slowly setting to voltage: 09.50 ...
2023-12-31 21:44:40 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:44:44 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:44:45 driver-btm-soc.c:6955:re_open_core_by_chain: re_open_core done!
2023-12-31 21:44:45 dspic33ep16gs202.c:213:dsPIC33EP16GS202_pic_heart_beat: ERROR! failed on Chain[1] after 3 times try!
2023-12-31 21:45:15 driver-btm-soc.c:6911:re_open_core_by_chain:

reopen chain 2, current pwm 5
2023-12-31 21:45:17 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[2] slowly setting to voltage: 09.50 ...
2023-12-31 21:45:18 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:45:24 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
2023-12-31 21:45:24 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:45:25 asic.c:1176:set_baud_by_chain: chain 2 set baud=26
2023-12-31 21:45:25 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 2
2023-12-31 21:45:25 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2023-12-31 21:45:26 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:45:27 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 2, find asic num = 60
2023-12-31 21:45:30 driver-btm-soc.c:4816:set_freq_by_chain: chain[2] set freq:100.00
2023-12-31 21:45:31 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 2
2023-12-31 21:45:31 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:45:31 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:45:32 temperature.c:801:calibration_sensor_offset: Chain[2] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:45:32 temperature.c:801:calibration_sensor_offset: Chain[2] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:45:32 asic.c:1176:set_baud_by_chain: chain 2 set baud=1
2023-12-31 21:45:33 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:45:33 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:45:35 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:45:35 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 125
2023-12-31 21:45:37 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 150
2023-12-31 21:45:39 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 175
2023-12-31 21:45:41 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 200
2023-12-31 21:45:43 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 225
2023-12-31 21:45:45 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 250
2023-12-31 21:45:47 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 275
2023-12-31 21:45:50 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 300
2023-12-31 21:45:52 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 325
2023-12-31 21:45:54 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 350
2023-12-31 21:45:56 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 375
2023-12-31 21:45:58 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 400
2023-12-31 21:46:00 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 425
2023-12-31 21:46:02 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 450
2023-12-31 21:46:04 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:46:04 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[2] increaseing the diff freq ...
2023-12-31 21:46:04 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 2 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:46:04 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:46:05 driver-btm-soc.c:6938:re_open_core_by_chain: reopen chain 2 finished, chain 2 chip temp 41 - 59
2023-12-31 21:46:05 driver-btm-soc.c:6939:re_open_core_by_chain: all chain chip temp 37 - 95
2023-12-31 21:46:05 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[2] slowly setting to voltage: 09.50 ...
2023-12-31 21:46:06 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:46:12 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
2023-12-31 21:46:12 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:46:12 driver-btm-soc.c:6955:re_open_core_by_chain: re_open_core done!
2023-12-31 21:46:42 driver-btm-soc.c:3646:check_system_work: Reboot cost 256 sec !
2023-12-31 21:46:42 driver-btm-soc.c:3657:check_system_work: re_open_core [1] times!
now setting chain[0]-volt[09.51]-data[027] chain[1]-volt[09.51]-data[027] chain[2]-volt[09.51]-data[027]
2023-12-31 21:46:45 power.c:1278:slowly_set_iic_power_voltage_t11: parallel set all chain to working voltage end!
now setting chain[0]-volt[09.50]-data[027] chain[1]-volt[09.50]-data[027] chain[2]-volt[09.50]-data[027]
2023-12-31 21:51:49 driver-btm-soc.c:6911:re_open_core_by_chain:

reopen chain 0, current pwm 24
2023-12-31 21:51:51 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[0] slowly setting to voltage: 09.50 ...
2023-12-31 21:51:53 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:51:56 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:51:57 asic.c:1176:set_baud_by_chain: chain 0 set baud=26
2023-12-31 21:51:57 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 0
2023-12-31 21:51:57 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2023-12-31 21:51:58 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:51:59 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 0, find asic num = 60
2023-12-31 21:52:03 driver-btm-soc.c:4816:set_freq_by_chain: chain[0] set freq:100.00
2023-12-31 21:52:03 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 0
2023-12-31 21:52:03 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:52:03 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:52:04 temperature.c:801:calibration_sensor_offset: Chain[0] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:52:04 temperature.c:801:calibration_sensor_offset: Chain[0] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:52:05 asic.c:1176:set_baud_by_chain: chain 0 set baud=1
2023-12-31 21:52:05 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:52:05 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:52:07 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:52:07 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 125
2023-12-31 21:52:09 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 150
2023-12-31 21:52:11 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 175
2023-12-31 21:52:13 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 200
2023-12-31 21:52:15 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 225
2023-12-31 21:52:17 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 250
2023-12-31 21:52:20 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 275
2023-12-31 21:52:22 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 300
2023-12-31 21:52:24 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 325
2023-12-31 21:52:26 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 350
2023-12-31 21:52:28 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 375
2023-12-31 21:52:30 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 400
2023-12-31 21:52:32 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 425
2023-12-31 21:52:34 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 450
2023-12-31 21:52:37 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:52:37 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[0] increaseing the diff freq ...
2023-12-31 21:52:37 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 0 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:52:37 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:52:38 driver-btm-soc.c:6938:re_open_core_by_chain: reopen chain 0 finished, chain 0 chip temp 29 - 63
2023-12-31 21:52:38 driver-btm-soc.c:6939:re_open_core_by_chain: all chain chip temp 29 - 85
2023-12-31 21:52:38 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[0] slowly setting to voltage: 09.50 ...
2023-12-31 21:52:38 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:52:41 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:52:42 driver-btm-soc.c:6955:re_open_core_by_chain: re_open_core done!
2023-12-31 21:52:42 dspic33ep16gs202.c:213:dsPIC33EP16GS202_pic_heart_beat: ERROR! failed on Chain[0] after 3 times try!
2023-12-31 21:53:12 driver-btm-soc.c:6911:re_open_core_by_chain:

reopen chain 1, current pwm 28
2023-12-31 21:53:14 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[1] slowly setting to voltage: 09.50 ...
2023-12-31 21:53:15 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:53:21 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:53:22 asic.c:1176:set_baud_by_chain: chain 1 set baud=26
2023-12-31 21:53:22 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 1
2023-12-31 21:53:22 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2023-12-31 21:53:23 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:53:24 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 1, find asic num = 60
2023-12-31 21:53:28 driver-btm-soc.c:4816:set_freq_by_chain: chain[1] set freq:100.00
2023-12-31 21:53:28 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 1
2023-12-31 21:53:28 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:53:28 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:53:29 temperature.c:801:calibration_sensor_offset: Chain[1] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:53:29 temperature.c:801:calibration_sensor_offset: Chain[1] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:53:30 asic.c:1176:set_baud_by_chain: chain 1 set baud=1
2023-12-31 21:53:30 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:53:30 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:53:32 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:53:32 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 125
2023-12-31 21:53:34 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 150
2023-12-31 21:53:36 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 175
2023-12-31 21:53:38 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 200
2023-12-31 21:53:40 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 225
2023-12-31 21:53:43 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 250
2023-12-31 21:53:45 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 275
2023-12-31 21:53:47 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 300
2023-12-31 21:53:49 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 325
2023-12-31 21:53:51 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 350
2023-12-31 21:53:53 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 375
2023-12-31 21:53:55 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 400
2023-12-31 21:53:57 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 425
2023-12-31 21:54:00 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 450
2023-12-31 21:54:02 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:54:02 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[1] increaseing the diff freq ...
2023-12-31 21:54:02 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 1 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:54:02 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:54:03 driver-btm-soc.c:6938:re_open_core_by_chain: reopen chain 1 finished, chain 1 chip temp 37 - 74
2023-12-31 21:54:03 driver-btm-soc.c:6939:re_open_core_by_chain: all chain chip temp 32 - 74
2023-12-31 21:54:03 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[1] slowly setting to voltage: 09.50 ...
2023-12-31 21:54:03 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:54:08 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:54:09 driver-btm-soc.c:6955:re_open_core_by_chain: re_open_core done!
2023-12-31 21:54:09 dspic33ep16gs202.c:213:dsPIC33EP16GS202_pic_heart_beat: ERROR! failed on Chain[1] after 3 times try!
2023-12-31 21:54:39 driver-btm-soc.c:6911:re_open_core_by_chain:

reopen chain 2, current pwm 15
2023-12-31 21:54:41 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[2] slowly setting to voltage: 09.50 ...
2023-12-31 21:54:42 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:54:47 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
2023-12-31 21:54:47 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:54:48 asic.c:1176:set_baud_by_chain: chain 2 set baud=26
2023-12-31 21:54:48 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 2
2023-12-31 21:54:48 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2023-12-31 21:54:49 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:54:51 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 2, find asic num = 60
2023-12-31 21:54:54 driver-btm-soc.c:4816:set_freq_by_chain: chain[2] set freq:100.00
2023-12-31 21:54:55 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 2
2023-12-31 21:54:55 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:54:55 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:54:55 temperature.c:801:calibration_sensor_offset: Chain[2] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:54:56 temperature.c:801:calibration_sensor_offset: Chain[2] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:54:56 asic.c:1176:set_baud_by_chain: chain 2 set baud=1
2023-12-31 21:54:56 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:54:56 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:54:58 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:54:58 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 125
2023-12-31 21:55:01 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 150
2023-12-31 21:55:03 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 175
2023-12-31 21:55:05 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 200
2023-12-31 21:55:07 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 225
2023-12-31 21:55:09 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 250
2023-12-31 21:55:11 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 275
2023-12-31 21:55:13 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 300
2023-12-31 21:55:15 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 325
2023-12-31 21:55:18 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 350
2023-12-31 21:55:20 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 375
2023-12-31 21:55:22 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 400
2023-12-31 21:55:24 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 425
2023-12-31 21:55:26 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 450
2023-12-31 21:55:28 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:55:28 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[2] increaseing the diff freq ...
2023-12-31 21:55:28 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 2 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:55:28 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:55:29 driver-btm-soc.c:6938:re_open_core_by_chain: reopen chain 2 finished, chain 2 chip temp 36 - 78
2023-12-31 21:55:29 driver-btm-soc.c:6939:re_open_core_by_chain: all chain chip temp 31 - 91
2023-12-31 21:55:29 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[2] slowly setting to voltage: 09.50 ...
2023-12-31 21:55:30 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:55:35 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
2023-12-31 21:55:35 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:55:36 driver-btm-soc.c:6955:re_open_core_by_chain: re_open_core done!
2023-12-31 21:56:06 driver-btm-soc.c:3646:check_system_work: Reboot cost 256 sec !
2023-12-31 21:56:06 driver-btm-soc.c:3657:check_system_work: re_open_core [2] times!
now setting chain[0]-volt[09.51]-data[027] chain[1]-volt[09.51]-data[027] chain[2]-volt[09.51]-data[027]
2023-12-31 21:56:08 power.c:1278:slowly_set_iic_power_voltage_t11: parallel set all chain to working voltage end!
now setting chain[0]-volt[09.50]-data[027] chain[1]-volt[09.50]-data[027] chain[2]-volt[09.50]-data[027]
2023-12-31 22:11:22 driver-btm-soc.c:3510:check_system_work: The avg rate is  10 in 30 mins, PCB temperature between 25 ~ 75
2023-12-31 22:41:50 driver-btm-soc.c:3510:check_system_work: The avg rate is  20 in 30 mins, PCB temperature between 25 ~ 66
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
December 31, 2023, 06:13:41 PM
#6
okay s9 k sucks 


but let me see the second part.

I have a good idea of what is wrong.
jr. member
Activity: 51
Merit: 16
December 31, 2023, 06:08:26 PM
#5
two parts should work

Okay.

1 of 2:
Code:
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 204140K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25236K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12196K (ccf17000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Broadcom BCM5241 e000b000.etherne:00: attached PHY driver [Broadcom BCM5241] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 11/5, WL threshold: 4096, image sequence number: 1537580400
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 14A3D278-9E8E-4C6E-8A15-6E652B4D1DA0, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 1014/239, WL threshold: 4096, image sequence number: 2477448636
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 7DFC7CE0-47AC-4703-95E0-63A3D3A02975, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab00d
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
 [2023-12-31 21:21:26.269] httpListenThread start ret=0
 [2023-12-31 21:21:56.270] start listen on 6060 ...
 [2023-12-31 21:28:00.285] setStartTimePoint total_tv_start_sys=879 total_tv_end_sys=880

2023-12-31 21:21:26 driver-btm-soc.c:6520:bitmain_soc_init: This is Antminer S9 K/SE scan user version
2023-12-31 21:21:26 driver-btm-soc.c:6526:bitmain_soc_init: special mode: disabled
2023-12-31 21:21:26 driver-btm-soc.c:6533:bitmain_soc_init: This is high performance mode
2023-12-31 21:21:26 driver-btm-soc.c:6538:bitmain_soc_init: last commit version: 99791ac commit time: 2019-09-17 19:17:44 build: 2019-09-18 16:00:29
2023-12-31 21:21:26 driver-btm-soc.c:6559:bitmain_soc_init: Detect 256MB control board of XILINX
2023-12-31 21:21:26 driver-btm-soc.c:6562:bitmain_soc_init: Miner compile time: Fri Feb 7 18:44:26 CST 2020 (Chipless S9K/SE v2.9) type: Antminer S9 K/SE
2023-12-31 21:21:26 driver-btm-soc.c:839:check_chain: get_hash_on_plug is 0x7
2023-12-31 21:21:26 driver-btm-soc.c:851:check_chain: !! chain[0]is exist
2023-12-31 21:21:26 driver-btm-soc.c:851:check_chain: !! chain[1]is exist
2023-12-31 21:21:26 driver-btm-soc.c:851:check_chain: !! chain[2]is exist
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fb 28 fc ff
00000080 ff ff ff ff ff ff ff dc   5a 5a 5a 5a 5a 5a 5a 5a
00000090 5a 5a 5a 5a 5a 5a 5a 5a   5a 5a 5a 5a 5a 5a 5a 5a
000000a0 5a 5a 5a 5a 5a 5a 5a 5a   5a 5a 5a 5a 5a 5a 5a 5a
000000b0 5a 5a 5a 5a 5a 5a 5a 5a   5a 5a 5a 5a 5a 5a 5a 5a
000000c0 5a 5a 5a 5a 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 26 12 00 00   20 ff ff ff 39 10 90 4b
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fb 28 fc ff
00000080 ff ff ff ff ff ff ff dc   5a 5a 5a 5a 5a 5a 5a 5a
00000090 5a 5a 5a 5a 5a 5a 5a 5a   5a 5a 5a 5a 5a 5a 5a 5a
000000a0 5a 5a 5a 5a 5a 5a 5a 5a   5a 5a 5a 5a 5a 5a 5a 5a
000000b0 5a 5a 5a 5a 5a 5a 5a 5a   5a 5a 5a 5a 5a 5a 5a 5a
000000c0 5a 5a 5a 5a 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 26 12 00 00   20 ff ff ff 39 10 90 4b
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fb 28 fc ff
00000080 ff ff ff ff ff ff ff dc   5a 5a 5a 5a 5a 5a 5a 5a
00000090 5a 5a 5a 5a 5a 5a 5a 5a   5a 5a 5a 5a 5a 5a 5a 5a
000000a0 5a 5a 5a 5a 5a 5a 5a 5a   5a 5a 5a 5a 5a 5a 5a 5a
000000b0 5a 5a 5a 5a 5a 5a 5a 5a   5a 5a 5a 5a 5a 5a 5a 5a
000000c0 5a 5a 5a 5a 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 26 12 00 00   20 ff ff ff 39 10 90 4b

read chain[0] hardware info:
major type: 0
minor type: 4
chip level: 0
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[1] hardware info:
major type: 0
minor type: 4
chip level: 0
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[2] hardware info:
major type: 0
minor type: 4
chip level: 0
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

sweep config for eco mode:
sweep_start_voltage: 8.60
max_aging_voltage:   8.90
sweep_min_freq:      300M
sweep_max_freq:      380M

sweep config for hpf mode:
sweep_start_voltage: 9.20
max_aging_voltage:   9.50
sweep_min_freq:      415M
sweep_max_freq:      600M
2023-12-31 21:21:38 driver-btm-soc.c:839:check_chain: get_hash_on_plug is 0x7
2023-12-31 21:21:38 driver-btm-soc.c:851:check_chain: !! chain[0]is exist
2023-12-31 21:21:38 driver-btm-soc.c:851:check_chain: !! chain[1]is exist
2023-12-31 21:21:38 driver-btm-soc.c:851:check_chain: !! chain[2]is exist
2023-12-31 21:21:38 driver-btm-soc.c:5965:get_freq_result_from_eeprom: orginal chip freq:
chain 0 freq:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450

chain 1 freq:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450

chain 2 freq:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450

2023-12-31 21:21:38 driver-btm-soc.c:6647:bitmain_soc_init: reset all...
2023-12-31 21:21:40 driver-btm-soc.c:6655:bitmain_soc_init: miner ID : 81189c0618c0885c
2023-12-31 21:21:40 driver-btm-soc.c:6359:init_miner_version: FPGA Version = 0xB00D
2023-12-31 21:21:59 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[0] PIC software version: 177
2023-12-31 21:22:00 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[1] PIC software version: 177
2023-12-31 21:22:00 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[2] PIC software version: 177
2023-12-31 21:22:00 power.c:185:power_init: power init ...
2023-12-31 21:22:00 power.c:232:set_working_voltage_by_chain: chain[0] working_voltage = 9.50
2023-12-31 21:22:00 power.c:232:set_working_voltage_by_chain: chain[1] working_voltage = 9.50
2023-12-31 21:22:00 power.c:232:set_working_voltage_by_chain: chain[2] working_voltage = 9.50
2023-12-31 21:22:00 driver-btm-soc.c:5735:init_working_voltage: set fixed voltage to 9.500000
2023-12-31 21:22:00 driver-btm-soc.c:5754:update_highest_voltage: chain 0 hpf working voltage 10.40
2023-12-31 21:22:00 driver-btm-soc.c:5754:update_highest_voltage: chain 1 hpf working voltage 10.40
2023-12-31 21:22:00 driver-btm-soc.c:5754:update_highest_voltage: chain 2 hpf working voltage 10.40
2023-12-31 21:22:00 driver-btm-soc.c:5763:update_highest_voltage: open core at max voltage 11.00
2023-12-31 21:22:00 power.c:781:set_iic_power_to_highest_voltage_by_chain: chain[0] setting to highest voltage: 11.00 ...
2023-12-31 21:22:01 power.c:707:set_iic_power_by_voltage: now setting voltage to : 11.00
2023-12-31 21:22:01 power.c:781:set_iic_power_to_highest_voltage_by_chain: chain[1] setting to highest voltage: 11.00 ...
2023-12-31 21:22:03 power.c:707:set_iic_power_by_voltage: now setting voltage to : 11.00
2023-12-31 21:22:04 power.c:781:set_iic_power_to_highest_voltage_by_chain: chain[2] setting to highest voltage: 11.00 ...
2023-12-31 21:22:04 power.c:707:set_iic_power_by_voltage: now setting voltage to : 11.00
2023-12-31 21:22:04 driver-btm-soc.c:1188:get_eeprom_total_hash_rate: chain[0] hash rate = 4646
2023-12-31 21:22:05 driver-btm-soc.c:1188:get_eeprom_total_hash_rate: chain[1] hash rate = 4646
2023-12-31 21:22:05 driver-btm-soc.c:1188:get_eeprom_total_hash_rate: chain[2] hash rate = 4646
2023-12-31 21:22:05 driver-btm-soc.c:1192:get_eeprom_total_hash_rate: total rate = 13938
2023-12-31 21:22:05 driver-btm-soc.c:1200:get_ideal_hash_rate: get ideal hash rate 13000
2023-12-31 21:22:05 eeprom.c:669:travel_eeprom_store: chain[0] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:450 IC[001]:450 IC[002]:450 IC[003]:450 IC[004]:450 IC[005]:450 IC[006]:450 IC[007]:450 IC[008]:450 IC[009]:450
IC[010]:450 IC[011]:450 IC[012]:450 IC[013]:450 IC[014]:450 IC[015]:450 IC[016]:450 IC[017]:450 IC[018]:450 IC[019]:450
IC[020]:450 IC[021]:450 IC[022]:450 IC[023]:450 IC[024]:450 IC[025]:450 IC[026]:450 IC[027]:450 IC[028]:450 IC[029]:450
IC[030]:450 IC[031]:450 IC[032]:450 IC[033]:450 IC[034]:450 IC[035]:450 IC[036]:450 IC[037]:450 IC[038]:450 IC[039]:450
IC[040]:450 IC[041]:450 IC[042]:450 IC[043]:450 IC[044]:450 IC[045]:450 IC[046]:450 IC[047]:450 IC[048]:450 IC[049]:450
IC[050]:450 IC[051]:450 IC[052]:450 IC[053]:450 IC[054]:450 IC[055]:450 IC[056]:450 IC[057]:450 IC[058]:450 IC[059]:450
voltage in mode2: 10.40 V
hash rate in mode2: 04646 GH/s

2023-12-31 21:22:05 eeprom.c:669:travel_eeprom_store: chain[1] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:450 IC[001]:450 IC[002]:450 IC[003]:450 IC[004]:450 IC[005]:450 IC[006]:450 IC[007]:450 IC[008]:450 IC[009]:450
IC[010]:450 IC[011]:450 IC[012]:450 IC[013]:450 IC[014]:450 IC[015]:450 IC[016]:450 IC[017]:450 IC[018]:450 IC[019]:450
IC[020]:450 IC[021]:450 IC[022]:450 IC[023]:450 IC[024]:450 IC[025]:450 IC[026]:450 IC[027]:450 IC[028]:450 IC[029]:450
IC[030]:450 IC[031]:450 IC[032]:450 IC[033]:450 IC[034]:450 IC[035]:450 IC[036]:450 IC[037]:450 IC[038]:450 IC[039]:450
IC[040]:450 IC[041]:450 IC[042]:450 IC[043]:450 IC[044]:450 IC[045]:450 IC[046]:450 IC[047]:450 IC[048]:450 IC[049]:450
IC[050]:450 IC[051]:450 IC[052]:450 IC[053]:450 IC[054]:450 IC[055]:450 IC[056]:450 IC[057]:450 IC[058]:450 IC[059]:450
voltage in mode2: 10.40 V
hash rate in mode2: 04646 GH/s

2023-12-31 21:22:05 eeprom.c:669:travel_eeprom_store: chain[2] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:450 IC[001]:450 IC[002]:450 IC[003]:450 IC[004]:450 IC[005]:450 IC[006]:450 IC[007]:450 IC[008]:450 IC[009]:450
IC[010]:450 IC[011]:450 IC[012]:450 IC[013]:450 IC[014]:450 IC[015]:450 IC[016]:450 IC[017]:450 IC[018]:450 IC[019]:450
IC[020]:450 IC[021]:450 IC[022]:450 IC[023]:450 IC[024]:450 IC[025]:450 IC[026]:450 IC[027]:450 IC[028]:450 IC[029]:450
IC[030]:450 IC[031]:450 IC[032]:450 IC[033]:450 IC[034]:450 IC[035]:450 IC[036]:450 IC[037]:450 IC[038]:450 IC[039]:450
IC[040]:450 IC[041]:450 IC[042]:450 IC[043]:450 IC[044]:450 IC[045]:450 IC[046]:450 IC[047]:450 IC[048]:450 IC[049]:450
IC[050]:450 IC[051]:450 IC[052]:450 IC[053]:450 IC[054]:450 IC[055]:450 IC[056]:450 IC[057]:450 IC[058]:450 IC[059]:450
voltage in mode2: 10.40 V
hash rate in mode2: 04646 GH/s

2023-12-31 21:22:05 driver-btm-soc.c:6698:bitmain_soc_init: fan_eft : 0  fan_pwm : 0
2023-12-31 21:22:05 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 0
2023-12-31 21:22:05 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2023-12-31 21:22:37 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2023-12-31 21:22:38 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 0, find asic num = 60
2023-12-31 21:22:42 driver-btm-soc.c:4816:set_freq_by_chain: chain[0] set freq:100.00
2023-12-31 21:22:43 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 0
2023-12-31 21:22:43 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:22:43 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:22:43 temperature.c:523:is_tempsensor_data_correct: Bad,temp_info.type = 0
2023-12-31 21:22:43 temperature.c:751:calibration_sensor_offset: chain[0] temp info is bad, reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0
sensor offset: -5  -4  0  0  0  0
2023-12-31 21:22:43 temperature.c:801:calibration_sensor_offset: Chain[0] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:22:44 temperature.c:801:calibration_sensor_offset: Chain[0] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:22:44 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 1
2023-12-31 21:22:44 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2023-12-31 21:23:16 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2023-12-31 21:23:17 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 1, find asic num = 60
2023-12-31 21:23:21 driver-btm-soc.c:4816:set_freq_by_chain: chain[1] set freq:100.00
2023-12-31 21:23:22 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 1
2023-12-31 21:23:22 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:23:22 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:23:22 temperature.c:523:is_tempsensor_data_correct: Bad,temp_info.type = 0
2023-12-31 21:23:22 temperature.c:751:calibration_sensor_offset: chain[1] temp info is bad, reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0
sensor offset: -5  -4  0  0  0  0
2023-12-31 21:23:22 temperature.c:801:calibration_sensor_offset: Chain[1] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:23:23 temperature.c:801:calibration_sensor_offset: Chain[1] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:23:23 driver-btm-soc.c:6388:bring_up_chain:

bring up chain 2
2023-12-31 21:23:24 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2023-12-31 21:23:55 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2023-12-31 21:23:56 driver-btm-soc.c:4003:check_asic_num: without pre_open_core chain 2, find asic num = 60
2023-12-31 21:24:00 driver-btm-soc.c:4816:set_freq_by_chain: chain[2] set freq:100.00
2023-12-31 21:24:01 driver-btm-soc.c:3929:pre_open_core_one_chain: for chain 2
2023-12-31 21:24:01 driver-btm-soc.c:4090:set_clock_delay_control: core_data = 0x06
2023-12-31 21:24:01 temperature.c:614:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2023-12-31 21:24:01 temperature.c:523:is_tempsensor_data_correct: Bad,temp_info.type = 0
2023-12-31 21:24:01 temperature.c:751:calibration_sensor_offset: chain[2] temp info is bad, reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0
sensor offset: -5  -4  0  0  0  0
2023-12-31 21:24:01 temperature.c:801:calibration_sensor_offset: Chain[2] chip[31] middle temp offset=-5, typeID=55
2023-12-31 21:24:02 temperature.c:801:calibration_sensor_offset: Chain[2] chip[40] middle temp offset=-4, typeID=55
2023-12-31 21:24:02 asic.c:1153:set_baud: set baud=1
2023-12-31 21:24:02 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2023-12-31 21:24:03 temperature.c:2064:detect_startup_environment_temperature: Environment temperature: [19]
2023-12-31 21:24:03 temperature.c:2081:detect_startup_environment_temperature: Enter 10 secs to cool down hash board, 1 times ...
2023-12-31 21:24:14 temperature.c:2064:detect_startup_environment_temperature: Environment temperature: [20]
2023-12-31 21:24:14 temperature.c:2081:detect_startup_environment_temperature: Enter 10 secs to cool down hash board, 2 times ...
2023-12-31 21:24:25 temperature.c:2064:detect_startup_environment_temperature: Environment temperature: [20]
2023-12-31 21:24:25 temperature.c:2081:detect_startup_environment_temperature: Enter 10 secs to cool down hash board, 3 times ...
2023-12-31 21:24:35 driver-btm-soc.c:4160:open_core_bm1393: Start Open Core!!
2023-12-31 21:24:42 driver-btm-soc.c:4227:open_core_bm1393: End Open Core!!
2023-12-31 21:24:43 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 125
2023-12-31 21:24:45 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 150
2023-12-31 21:24:47 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 175
2023-12-31 21:24:49 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 200
2023-12-31 21:24:51 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 225
2023-12-31 21:24:53 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 250
2023-12-31 21:24:55 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 275
2023-12-31 21:24:58 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 300
2023-12-31 21:25:00 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 325
2023-12-31 21:25:02 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 350
2023-12-31 21:25:04 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 375
2023-12-31 21:25:06 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 400
2023-12-31 21:25:08 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 425
2023-12-31 21:25:10 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 450
2023-12-31 21:25:12 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:25:12 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[0] increaseing the diff freq ...
2023-12-31 21:25:12 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 0 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:25:12 power.c:1309:slowly_set_working_power_t11: set chain 0 to working voltage:
now setting chain[0]-volt[10.63]-data[005]
now setting chain[0]-volt[10.33]-data[009]
now setting chain[0]-volt[10.09]-data[013]
now setting chain[0]-volt[09.89]-data[017]
now setting chain[0]-volt[09.72]-data[021]
now setting chain[0]-volt[09.65]-data[023]
now setting chain[0]-volt[09.58]-data[025]
2023-12-31 21:25:40 dspic33ep16gs202.c:213:dsPIC33EP16GS202_pic_heart_beat: ERROR! failed on Chain[0] after 3 times try!
now setting chain[0]-volt[09.54]-data[026]
now setting chain[0]-volt[09.51]-data[027]
2023-12-31 21:25:48 power.c:1331:slowly_set_working_power_t11: done!
2023-12-31 21:25:49 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 125
2023-12-31 21:25:51 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 150
2023-12-31 21:25:53 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 175
2023-12-31 21:25:55 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 200
2023-12-31 21:25:57 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 225
2023-12-31 21:25:59 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 250
2023-12-31 21:26:01 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 275
2023-12-31 21:26:03 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 300
2023-12-31 21:26:06 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 325
2023-12-31 21:26:08 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 350
2023-12-31 21:26:10 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 375
2023-12-31 21:26:12 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 400
2023-12-31 21:26:14 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 425
2023-12-31 21:26:16 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 450
2023-12-31 21:26:18 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:26:18 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[1] increaseing the diff freq ...
2023-12-31 21:26:18 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 1 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:26:18 power.c:1309:slowly_set_working_power_t11: set chain 1 to working voltage:
now setting chain[1]-volt[10.63]-data[005]
now setting chain[1]-volt[10.33]-data[009]
now setting chain[1]-volt[10.09]-data[013]
now setting chain[1]-volt[09.89]-data[017]
now setting chain[1]-volt[09.72]-data[021]
now setting chain[1]-volt[09.65]-data[023]
now setting chain[1]-volt[09.58]-data[025]
now setting chain[1]-volt[09.54]-data[026]
now setting chain[1]-volt[09.51]-data[027]
2023-12-31 21:26:53 power.c:1331:slowly_set_working_power_t11: done!
2023-12-31 21:26:54 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 125
2023-12-31 21:26:56 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 150
2023-12-31 21:26:58 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 175
2023-12-31 21:27:00 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 200
2023-12-31 21:27:02 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 225
2023-12-31 21:27:04 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 250
2023-12-31 21:27:06 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 275
2023-12-31 21:27:08 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 300
2023-12-31 21:27:11 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 325
2023-12-31 21:27:13 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 350
2023-12-31 21:27:15 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 375
2023-12-31 21:27:17 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 400
2023-12-31 21:27:19 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 425
2023-12-31 21:27:21 driver-btm-soc.c:5367:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 450
2023-12-31 21:27:23 driver-btm-soc.c:5383:increase_freq_by_eeprom_slowly_by_chain: max = 450 ,min = 450
2023-12-31 21:27:23 driver-btm-soc.c:5389:increase_freq_by_eeprom_slowly_by_chain: chain[2] increaseing the diff freq ...
2023-12-31 21:27:23 driver-btm-soc.c:5418:increase_freq_by_eeprom_slowly_by_chain: chain 2 final freq setting:
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
450 450 450 450 450 450 450 450 450 450
2023-12-31 21:27:23 power.c:1309:slowly_set_working_power_t11: set chain 2 to working voltage:
now setting chain[2]-volt[10.63]-data[005]
now setting chain[2]-volt[10.33]-data[009]
now setting chain[2]-volt[10.09]-data[013]
now setting chain[2]-volt[09.89]-data[017]
now setting chain[2]-volt[09.72]-data[021]
now setting 2023-12-31 21:27:45 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
chain[2]-volt[09.65]-data[023]
now setting chain[2]-volt[09.58]-data[025]
now setting chain[2]-volt[09.54]-data[026]
now setting 2023-12-31 21:27:58 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
chain[2]-volt[09.51]-data[027]
2023-12-31 21:27:59 power.c:1331:slowly_set_working_power_t11: done!
2023-12-31 21:27:59 driver-btm-soc.c:5112:set_timeout: freq 450 final timeout=291
2023-12-31 21:27:59 driver-btm-soc.c:2920:low_temp_process_parm_init: chip miner_type = [4]
2023-12-31 21:27:59 driver-btm-soc.c:2920:low_temp_process_parm_init: chip miner_type = [4]
2023-12-31 21:27:59 driver-btm-soc.c:2920:low_temp_process_parm_init: chip miner_type = [4]
2023-12-31 21:27:59 driver-btm-soc.c:3359:check_system_work: check system thread start...
2023-12-31 21:27:59 driver-btm-soc.c:3376:check_system_work: low_bringup_pcb_temp_threshhold = 0
2023-12-31 21:27:59 driver-btm-soc.c:3377:check_system_work: recovery_working_vol_low_temp = 6, recovery_working_vol_high_temp = 28
2023-12-31 21:27:59 driver-btm-soc.c:3378:check_system_work: delta_voltage = 0.10
2023-12-31 21:28:00 driver-btm-soc.c:6810:bitmain_soc_init: Init done!
2023-12-31 21:28:00 driver-btm-soc.c:7429:bitmain_soc_prepare: bitmain soc init success.
2023-12-31 21:28:00 temperature.c:1525:read_temp_func: bring_up_pcb_temp = 27
2023-12-31 21:28:00 util.c:2178:process_version_mask: Pool 0 Version num is 2
2023-12-31 21:28:01 driver-btm-soc.c:7104:send_job: Version num 2
2023-12-31 21:28:19 temperature.c:1870:get_target_chip_temp: if startup in low temp environment: YES
2023-12-31 21:28:19 temperature.c:1716:_get_target_chip_temp_t11: chip miner_type = [4]
2023-12-31 21:28:19 temperature.c:1716:_get_target_chip_temp_t11: chip miner_type = [4]
2023-12-31 21:28:19 temperature.c:1716:_get_target_chip_temp_t11: chip miner_type = [4]
2023-12-31 21:28:19 driver-btm-soc.c:3541:check_system_work: set reopen algorith parameters...
2023-12-31 21:33:03 driver-btm-soc.c:2513:is_domain_imbalance: dumping inbalance domain info...
1 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0 
2023-12-31 21:33:03 driver-btm-soc.c:3494:check_system_work: starup imbalance detected
2023-12-31 21:33:03 driver-btm-soc.c:6911:re_open_core_by_chain:

reopen chain 0, current pwm 13
2023-12-31 21:33:05 power.c:996:slowly_set_iic_power_to_working_voltage_by_chain: chain[0] slowly setting to voltage: 09.50 ...
2023-12-31 21:33:05 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.50
2023-12-31 21:33:08 power.c:728:set_iic_power_by_iic_data: now setting voltage to : 09.51
2023-12-31 21:33:09 asic.c:1176:set_baud_by_chain: chain 0 set baud=26
2023-12-31 21:33:09 driver-btm-soc.c:6388:bring_up_chain:

(continued)...
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
December 31, 2023, 05:58:55 PM
#4
Thank you.

I looked for what ever errors and failures I can find and some suggestions I've tried so far is a tear down of the miner and cleaning with a duster and brush and made sure all cables were firmly secured. I did a few resets and the miner continues to revert back to some idle state and RT GH/S continues to read 0. I haven't tried any kind of firmware update.

The log is too large and failed to post cause it exceeded the maximum, should I try to just split it in two parts?

two parts should work
jr. member
Activity: 51
Merit: 16
December 31, 2023, 05:48:54 PM
#3
Thank you.

I looked for what ever errors and failures I can find and some suggestions I've tried so far is a tear down of the miner and cleaning with a duster and brush and made sure all cables were firmly secured. I did a few resets and the miner continues to revert back to some idle state and RT GH/S continues to read 0. I haven't tried any kind of firmware update.

The log is too large and failed to post cause it exceeded the maximum, should I try to just split it in two parts?
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
December 31, 2023, 03:25:25 PM
#2
I'm getting the feeling I was sold a defective unit and can't be returned.
It may be possible it's something I'm doing wrong, or maybe can be diagnosed and repaired. Or at least find out what needs to be replaced and then decide what to do.

Here's the current status:
Enclosure outside with hatch closed:


Enclosure intake side:


Enclosure exhaust side:


Subpanel:


Miner OS miner status:


The miner has been running for almost 7 hours at the time of this post and still 0 real time hash, but the average has been slowly creeping up, but is about as much hash power as a CompacF USB miner.

In the status page all the ASIC chips are accounted for, but when I looked in the log, I have found some lines that mentioned bad temp readings and one error in there somewhere. I can't really decipher the log and trying to see if Bitman will help with diagnosing the log file.

The green signal light continues to flash like it is hashing. I have heard that ASICs take a while to start hashing, but I'm sure it's not supposed to take this long.

The enclosure, I tried my best to keep good airflow, it actually seems to be working despite not having two rooms for positive and negative pressure.
The picture showing the exhaust, there's a 6" duct there and a hole, I promise, there's just some dampening material.
The soundproofing however is garbage and should have invested in MLV and green glue, it's still sounds like a vacuum outside of the enclosure which is not working for everyone else. I tried to add more sound proofing by building a box to fit in the enclosure and the miner did not like being put in a box and I think overheated. Perhaps the design was poor and lacked proper air flow.

I read up on some things about making repairs, but I've also read posts here that repairs are not advised and will destroy the miner. Such as the thermal compound is an epoxy and not a paste and will likely tear off the chip if you try to remove a heat sink.
I would like to try to diagnose the problem and zero in on the fault.

post the logs.

set them in
Code:
 like this 

maybe i can figure out issue.
jr. member
Activity: 51
Merit: 16
December 31, 2023, 02:43:38 AM
#1
I'm getting the feeling I was sold a defective unit and can't be returned.
It may be possible it's something I'm doing wrong, or maybe can be diagnosed and repaired. Or at least find out what needs to be replaced and then decide what to do.

Here's the current status:
Enclosure outside with hatch closed:


Enclosure intake side:


Enclosure exhaust side:


Subpanel:


Miner OS miner status:


The miner has been running for almost 7 hours at the time of this post and still 0 real time hash, but the average has been slowly creeping up, but is about as much hash power as a CompacF USB miner.

In the status page all the ASIC chips are accounted for, but when I looked in the log, I have found some lines that mentioned bad temp readings and one error in there somewhere. I can't really decipher the log and trying to see if Bitman will help with diagnosing the log file.

The green signal light continues to flash like it is hashing. I have heard that ASICs take a while to start hashing, but I'm sure it's not supposed to take this long.

The enclosure, I tried my best to keep good airflow, it actually seems to be working despite not having two rooms for positive and negative pressure.
The picture showing the exhaust, there's a 6" duct there and a hole, I promise, there's just some dampening material.
The soundproofing however is garbage and should have invested in MLV and green glue, it's still sounds like a vacuum outside of the enclosure which is not working for everyone else. I tried to add more sound proofing by building a box to fit in the enclosure and the miner did not like being put in a box and I think overheated. Perhaps the design was poor and lacked proper air flow.

I read up on some things about making repairs, but I've also read posts here that repairs are not advised and will destroy the miner. Such as the thermal compound is an epoxy and not a paste and will likely tear off the chip if you try to remove a heat sink.
I would like to try to diagnose the problem and zero in on the fault.
Jump to: