Keyboard issue - j0rs - 01-01-2025
Keyboard issue
https://forum.armbian.com/topic/47099-keyboard-is-it-software-issue/
Is there any chance to check if the keyboard failure is hardware or software related?
The keyboard stopped working correctly when computer was in the drawer. There was no possibility for any physical damage to the keyboard.
Can I solve the issue by myself or do I need to buy the new keyboard or use my Pinebook pro as a coaster only.
Thanks.
*UPDATE*
On top of keyboard issue - I solved it by buying external usb keyboard.
*I cannot power up my trashy laptop i.e. PBP.*
1a. battery disconnected, I used bypass cables.
eMMC with Armbian
Code: U-Boot TPL 2020.10-armbian (Aug 08 2021 - 16:26:56)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
Trying to boot from MMC2
NOTICE: BL31: v2.5(release):c158878-dirty
NOTICE: BL31: Built : 16:26:51, Aug 8 2021
U-Boot 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 Pinebook Pro
Net: No ethernet found.
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3:
All led are dead.
1b. - eMMC is disabled, Armbian on sd card
Code: U-Boot TPL 2020.10-armbian (Aug 08 2021 - 16:26:56)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
Trying to boot from MMC1
NOTICE: BL31: v2.5(release):c158878-dirty
NOTICE: BL31: Built : 16:26:51, Aug 8 2021
U-Boot 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 Pinebook Pro
2. Battery is connected (with reset), eMMC disabled.
Code: U-Boot TPL 2020.10-armbian (Aug 08 2021 - 16:26:56)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
Trying to boot from MMC1
NOTICE: BL31: v2.5(release):c158878-dirty
NOTICE: BL31: Built : 16:26:51, Aug 8 2021
U-Boot 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 Pinebook Pro
All led are dead.
RE: Keyboard issue - ingcontrib - 01-15-2025
Do you think that it’s a sign of a software issue rather than hardware?
[/url]
[url=https://forum.armbian.com/topic/47099-keyboard-is-it-software-issue/]https://forum.armbian.com/topic/47099-keyboard-Geometry Dash Lite-is-it-software-issue/
RE: Keyboard issue - j0rs - 01-20-2025
I'm confused because PBP was stored in a drawer after update&&upgrade.
What could happen to the keyboard in the drawer? I have no idea. That's why I thought that maybe this is somehow firmware related?
I have had a lot hardware and software related issues with PBP. To be honest with this device everything is possible.
The thing is, how can I exclude software or hardware defect without investing money in the new keyboard? I don't want to invest >$1 in this product anymore.
RE: Keyboard issue - KC9UDX - 01-20-2025
Put a different OS on a micro-SD card. Boot that and see what happens.
On these devices there is certainly the possibility of hardware damage if stored in a drawer. The battery can puff up and cause mechanical damage. I've had it happen. I haven't had damage to the keyboard but I can see how it could happen. I don't suspect this is your issue though.
In any case if you get to a point where you give up on it please don't "recycle" it. There are many of us here who would jump at the opportunity to try to fix it.
|