two days in and it's already bricked! D:
after flashing a custom-built manjaro image to emmc, the pbp won't boot any more. not from emmc, but also not from sdcards (tried multiple) or usb sticks (tried multiple), neither with the default debian image nor with a stock manjaro image, regardless of whether emmc is enabled or disabled via the hardware switch (or even present). power led stays off, whether a uart cable is connected or not (or the uart is even enabled via switch).
looking at uart logs it seems that the chip doesn't even reach uboot. when booting with emmc disabled it comes out of DDR init just fine, but the boot stage isn't happy:
Code: Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 249
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=59640MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
mmc0:cmd7,10
mmc0:cmd5,20
mmc0:cmd7,10
mmc0:cmd5,20
mmc0:cmd7,10
SdmmcInit=0 1
StorageInit ok = 329828
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT part: 0, name: IDBLoader, start:0x40, size:0x3fc0
GPT part: 1, name: U-Boot, start:0x4000, size:0x2000
GPT part: 2, name: TrustedFirmware-A, start:0x6000, size:0x2000
GPT part: 3, name: EFI, start:0x8000, size:0x64000
GPT part: 4, name: Boot, start:0x6c000, size:0xfa000
GPT part: 5, name: RootFS, start:0x166000, size:0x7315fdf
no find partition:uboot.
LoadTrust Addr:0x4000
LoadTrust Addr:0x4400
LoadTrust Addr:0x4800
LoadTrust Addr:0x4c00
LoadTrust Addr:0x5000
LoadTrust Addr:0x5400
LoadTrust Addr:0x5800
LoadTrust Addr:0x5c00
Addr:0x4000 No find trust.img!
LoadTrustBL error:-3
emmc enabled stops even earlier:
Code: Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 251
mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
mmc: ERROR: Card did not respond to voltage select!
emmc reinit
mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
mmc: ERROR: Card did not respond to voltage select!
emmc reinit
mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
mmc: ERROR: Card did not respond to voltage select!
SdmmcInit=2 1
mmc0:cmd5,20
mmc0:cmd7,10
mmc0:cmd5,20
mmc0:cmd7,10
mmc0:cmd5,20
mmc0:cmd7,10
SdmmcInit=0 1
powerOn 68753
is this recoverable? 
01-01-2020, 09:52 PM
(This post was last modified: 01-01-2020, 09:57 PM by bcnaz.)
(01-01-2020, 07:51 PM)dhivael Wrote: two days in and it's already bricked! D:
after flashing a custom-built manjaro image to emmc, the pbp won't boot any more. not from emmc, but also not from sdcards (tried multiple) or usb sticks (tried multiple), neither with the default debian image nor with a stock manjaro image, regardless of whether emmc is enabled or disabled via the hardware switch (or even present). power led stays off, whether a uart cable is connected or not (or the uart is even enabled via switch).
looking at uart logs it seems that the chip doesn't even reach uboot. when booting with emmc disabled it comes out of DDR init just fine, but the boot stage isn't happy:
Code: Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 249
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=59640MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
mmc0:cmd7,10
mmc0:cmd5,20
mmc0:cmd7,10
mmc0:cmd5,20
mmc0:cmd7,10
SdmmcInit=0 1
StorageInit ok = 329828
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT part: 0, name: IDBLoader, start:0x40, size:0x3fc0
GPT part: 1, name: U-Boot, start:0x4000, size:0x2000
GPT part: 2, name: TrustedFirmware-A, start:0x6000, size:0x2000
GPT part: 3, name: EFI, start:0x8000, size:0x64000
GPT part: 4, name: Boot, start:0x6c000, size:0xfa000
GPT part: 5, name: RootFS, start:0x166000, size:0x7315fdf
no find partition:uboot.
LoadTrust Addr:0x4000
LoadTrust Addr:0x4400
LoadTrust Addr:0x4800
LoadTrust Addr:0x4c00
LoadTrust Addr:0x5000
LoadTrust Addr:0x5400
LoadTrust Addr:0x5800
LoadTrust Addr:0x5c00
Addr:0x4000 No find trust.img!
LoadTrustBL error:-3
emmc enabled stops even earlier:
Code: Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 251
mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
mmc: ERROR: Card did not respond to voltage select!
emmc reinit
mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
mmc: ERROR: Card did not respond to voltage select!
emmc reinit
mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
mmc: ERROR: Card did not respond to voltage select!
SdmmcInit=2 1
mmc0:cmd5,20
mmc0:cmd7,10
mmc0:cmd5,20
mmc0:cmd7,10
mmc0:cmd5,20
mmc0:cmd7,10
SdmmcInit=0 1
powerOn 68753
is this recoverable?
Yes, There are several Threads/Posts that can help you recover.
Same and similar problems
Though if this a brand new PBP, ? You may also want to check some of the other items :
If the eMMC is seated all the way, is the ribbon cable to the sd card slot secure.....
I opened my PBP before turning it on the first time, I found the eMMC was not all the way pushed into the socket.
LINUX = CHOICES
**BCnAZ**
Donate to $upport
your favorite OS Team
none of the threads i've found so far have helped, as similar or different as they looked. the gist seems to be "boot from sd and reflash emmc", but the thing just won't boot from anything at this point.
01-01-2020, 11:30 PM
(This post was last modified: 01-01-2020, 11:43 PM by bcnaz.)
(01-01-2020, 09:56 PM)dhivael Wrote: none of the threads i've found so far have helped, as similar or different as they looked. the gist seems to be "boot from sd and reflash emmc", but the thing just won't boot from anything at this point.
Have you tried turning off your eMMC ?
if the boot on it is messed up, it will not allow the sd card to boot.
The boot procedure to start from sd first is on the eMMC, so if that is corrupt you will not boot from the sd card.
I see where another forum member was able to boot from sd after turning off the eMMC
( See wiki for the switch location in the board )
IF you succeed, with being able to boot in this fashion... (after this, proceed to next step)
Next you need to turn the eMMC switch back on at the correct time during the boot sequence.
This person did state he had to try several times before he got the switch turned on at the correct time.
When you are able to get booted and have the eMMC turned back on, you should be able to re-install your OS.
I am looking into being able to use a usb to eMMC adapter to load the OS onto the eMMC.
(using another computer to download and install to the eMMC via the usb adapter)
I have a 128gb eMMC I would like to swap out with my original 64gb drive.
I hope this is helpful
BC
Have you looked at the thread ' Restore default Debian system ' ?
The usb to eMMC adapter is available from the Pine store, but that can take 3-4 weeks for delivery.
LINUX = CHOICES
**BCnAZ**
Donate to $upport
your favorite OS Team
01-02-2020, 02:17 AM
(This post was last modified: 01-02-2020, 02:27 AM by pfeerick.)
(01-01-2020, 07:51 PM)dhivael Wrote: Code: GPT part: 0, name: IDBLoader, start:0x40, size:0x3fc0
GPT part: 1, name: U-Boot, start:0x4000, size:0x2000
GPT part: 2, name: TrustedFirmware-A, start:0x6000, size:0x2000
GPT part: 3, name: EFI, start:0x8000, size:0x64000
GPT part: 4, name: Boot, start:0x6c000, size:0xfa000
GPT part: 5, name: RootFS, start:0x166000, size:0x7315fdf
no find partition:uboot.
I note the end of this there is the error saying it can't find partition 'uboot'... where there is a partition called 'U-Boot' in the GPT table... wrong name?
And I have to ask... you've double and triple checked you're using a PinebookPro image, not a Pinebook image?
emmc has been turned off, whether it's on or off only changes *how* the thing fails, not *that* it fails. that's likely because i trashed the uboot on emmc by accident. and yes, they are pinebook pro images.
(01-02-2020, 02:17 AM)pfeerick Wrote: (01-01-2020, 07:51 PM)dhivael Wrote: Code: GPT part: 0, name: IDBLoader, start:0x40, size:0x3fc0
GPT part: 1, name: U-Boot, start:0x4000, size:0x2000
GPT part: 2, name: TrustedFirmware-A, start:0x6000, size:0x2000
GPT part: 3, name: EFI, start:0x8000, size:0x64000
GPT part: 4, name: Boot, start:0x6c000, size:0xfa000
GPT part: 5, name: RootFS, start:0x166000, size:0x7315fdf
no find partition:uboot.
I note the end of this there is the error saying it can't find partition 'uboot'... where there is a partition called 'U-Boot' in the GPT table... wrong name?
And I have to ask... you've double and triple checked you're using a PinebookPro image, not a Pinebook image? Ameridroid sells both usb emmc adapters as well as sdcard emmc adapters (I have on of those--and it works very well). I believe anywhere in the US you would receive the item in a few days max. Check out their web site .
I find the adapter very helpful--I have a couple of other pine devices that use EMMC, too, But especially in this case with the laptop, if one messes things up through software, it makes it easier to start over again with a fresh emmc install.
Can you, however:
use the switch to turn off the EMMC, remove the EMMC and boot from a fresh manjaro sdcard build? If so, you haven't bricked anything.
Also note that when reinstalling and reenabling the EMMC, you may need to press the reset button for the EMMC to begin working again.
It's also possible to write the EMMC with the rkdeveloptool device in maskrom mode. see http://opensource.rock-chips.com/wiki_Rockusb#Maskrom_mode
i don't live in the us, so getting one of these adapters won't be that easy. should have ordered one with the pbp itself to be honest. the rockchip tools also don't work at all, they try to talk to the chip in the pbp but run into usb timeouts and fail
the problem did go away now though, at least. it seems this was a combination of bad luck, bad sd cards, some images not having a complete uboot that can boot without the emmc and the pbp not having enough power at some stage of the boot process. i was finally able to boot into ubuntu lxde and use that to flash emmc with a usable image again, using the technique bcnaz described.
Hi Belfastraven,
Currently I have ChomeOS on the EMMC which freezes as soon as i try to play any video in the browser deemed unusable.
so I've tried to load Debian back on to the EMMC via SDcard but it boots past the SD and straight into Chrome again. thinking i might have a faulty card or flashed corrupted image (I don't have a EMMC usb adapter or the uart cable).
So i followed your instructions but i'm not sure if what i'm doing is correct, as i don't get any life from the laptop (no LED) when i try to power on with only the SD card in and the EMMC switch (24) is in the OFF position.
I know the follwoing was mentioned from another post by Tophneal....
"... If you have a USB c cable you can use rkflashtool to flash to your emmc. Refer to the wiki for the internal button that puts the PBP in mask tomorrow mode..."
https://forum.pine64.org/showthread.php?tid=8214
so is mask mode when the (24) switch is in the off position?
Cheers
PreMis
(01-02-2020, 02:05 PM)dhivael Wrote: i don't live in the us, so getting one of these adapters won't be that easy. should have ordered one with the pbp itself to be honest. the rockchip tools also don't work at all, they try to talk to the chip in the pbp but run into usb timeouts and fail
the problem did go away now though, at least. it seems this was a combination of bad luck, bad sd cards, some images not having a complete uboot that can boot without the emmc and the pbp not having enough power at some stage of the boot process. i was finally able to boot into ubuntu lxde and use that to flash emmc with a usable image again, using the technique bcnaz described.
Glad you got it sorted. If it makes you feel better I have had a similar issue and ended up having to switch off the emmc...(undo the back etc) then boot to sd whilst immediately switching the emmc on....took a few turns but it worked in the end.
Booted SD, reflashed EMMC - bobs your uncle
|
bricked it?
