Obviously you need to get the polarity right, otherwise you're going to really hope you used thin wires so you can feel them heat up or smoke if you get it back to front!īy rights, you can cheat if you didn't have a charger or variable power supply handy, and hook up a pair of AA batteries (i.e. 3v) to the lithium battery for 5-10 seconds, and that would have given it the (gentle) kick it needed to dis-arm the low-voltage cuttoff. it needs power before it works, but when you first connect it stays off, so you need to bypass that protection to 'arm' it (hence why all the 'buy-your-own-battery' powerbanks all have a reset pinhole/switch in order to power them on when you first insert the batteries).īy rights, you can cheat if you didn't have a charger or variable power supply handy, and hook up a pair of AA batteries (i.e. Same stupid situation as the TP5100 lipo charge boards with protection circuitry. you get a chicken-egg situation happening. It looks like there may also be an issue with the fact that the battery has a dedicated battery protection circuit, which will isolate itself from the outside world until the undervoltage lockout has been lifted. Sunxi bmp: unable to open file \boot\bootlogo.bmpĪutoboot in 3 seconds, Press s or to abort ** Unable to use mmc 0:1 for loading the env ** PLL6=600 Mhz,AHB1=200 Mhz, APB1=100Mhz AHB2=300Mhz MBus=400Mhzįetch script data boot_to_hpd fail :arisc_dvfs_cfg_vf_table: support only one vf_table INFO: B元-1: Preparing for E元 exit to normal world INFO: B元-1: Initializing runtime services Loading file 2 at address 0x00040000,size 0x00019a00 success Loading file 0 at address 0x40000000,size 0x0000a200 success Succeed in loading uboot from sdmmc flash. : read block failed, mmc_read_blocks 271īoot log: sopine legacy image with this patchīoot0 commit : 43e77041d17badbf8be959b8db97232c5e3a0a75ĭRAM Type = 7 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3) + if(!axp_i2c_read(AXP81X_ADDR, BOOT_POWER81X_OFF_CTL, ®_value)) + /* Force enable battery detection - reg 0x32 bit 6 */ a/u-boot-pine64/board/sunxi/common/power_check.c but even after that it came back fine and just charged the battery.ĭiff -git a/u-boot-pine64/board/sunxi/common/power_check.c b/u-boot-pine64/board/sunxi/common/power_check.c I even disabled upower once and let it run until the kernel crashed, that was around 3.4V at 2A load and well past 2% capacity left. just a wild guess, I tried to discharge my PB a couple times now and couldn't get it into that state so far. Question, how did it run dry? Was that with system active or did it run dry in suspend? Maybe the ARISC does weird things and leaves the AXP in some faulty state. : start mmc_calibrate_delay_unit, don't access device. Screen_id =0, screen_width =1366, screen_height =768 drivers/mmc/mmc.c 2733 mmc_initīmp file buffer: 0x41000000, bmp_info.buffer: 47400000įetch script data boot_disp.output_full fail PowerBus = 2(0: not exist 1:vBus 2:acBus 3:vBus&acBus)īattery low power and vol with dc or ac, should charge longer Get Pine64 model from DRAM size and used storage
0 kommentar(er)
