Hi,

It is very strange to hear that. I deployed this image to couple of Rock64-s week ago. So, could you please be more specific? What are you trying to do exactly?

You are supposed to download openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz uncompress it with `xz -d openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz` and write .raw file to microsd card as the following `dd_rescue openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw /dev/your_sd_card_here`. That's what i did, but i'll try it again. I didn't get any errors when writing the image. This time, i'll wipe the sd card and create one fat

On 2/12/20 1:49 AM, Matwey V. Kornilov wrote: partition, just to be on the safe side.

Do you have usb rs232 ttl converter to attach the Rock64 console? What does it say?

i did, but i don't remember. It didn't get very far. If it fails this time, i'll copy and paste the output. Thanks

ср, 12 февр. 2020 г. в 10:17, Guillaume Gardet :

...

Hi,

...

-----Original Message----- From: ITwrx Sent: 12 February 2020 03:49 To: opensuse-arm@opensuse.org Subject: [opensuse-arm] Rock64

Thorston/All,

i just wanted to report that there are not Rock64 microOS images, only images for the older pine64.

Also, the instructions on the Rock64 openSUSE wiki don't work (exactly as they are), using the below linked image file. I don't know what the corresponding "packages" file is for or how to use it, so it was not used in any way. The Rock64 The "packages" file is just the list of installed packages in this *.raw.xz image.

...

openSUSE wiki page didn't mention anything about it. Probably why the board won't boot... :)

http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Roc kchip/images/openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30- Build5.29.raw.xz

Any tips appreciated. Added Matwey in Cc who may help.

Cheers, Guillaume

...

Thanks,

ITwrx

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- ---- --- Information Technology Works on the net: https://ITwrx.org on the fediverse: @ITwrx@blurts.net -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

12.02.2020 18:37, ITwrx пишет:

On 2/12/20 8:59 AM, ITwrx wrote:

...

...

Hi,

It is very strange to hear that. I deployed this image to couple of Rock64-s week ago. So, could you please be more specific? What are you trying to do exactly?

You are supposed to download openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz uncompress it with `xz -d openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz` and write .raw file to microsd card as the following `dd_rescue openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw /dev/your_sd_card_here`. That's what i did, but i'll try it again. I didn't get any errors when writing the image. This time, i'll wipe the sd card and create one fat

On 2/12/20 1:49 AM, Matwey V. Kornilov wrote: partition, just to be on the safe side.

...

Do you have usb rs232 ttl converter to attach the Rock64 console? What does it say? i did, but i don't remember. It didn't get very far. If it fails this time, i'll copy and paste the output.

Thanks

...

ср, 12 февр. 2020 г. в 10:17, Guillaume Gardet :

...

Hi,

...

-----Original Message----- From: ITwrx Sent: 12 February 2020 03:49 To: opensuse-arm@opensuse.org Subject: [opensuse-arm] Rock64

Thorston/All,

i just wanted to report that there are not Rock64 microOS images, only images for the older pine64.

Also, the instructions on the Rock64 openSUSE wiki don't work (exactly as they are), using the below linked image file. I don't know what the corresponding "packages" file is for or how to use it, so it was not used in any way. The Rock64 The "packages" file is just the list of installed packages in this *.raw.xz image.

...

openSUSE wiki page didn't mention anything about it. Probably why the board won't boot... :)

http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Roc kchip/images/openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30- Build5.29.raw.xz

Any tips appreciated. Added Matwey in Cc who may help.

Cheers, Guillaume

...

Thanks,

ITwrx

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Ok, i misspoke earlier. The first time i didn't extract, then run dd_rescue per your instructions. i ran "xzcat [image].raw.xz | dd bs=4M of=/dev/sdX iflag=fullblock oflag=direct; sync" (substituting relevant info) per the wiki. This time i did use your commands. I got the same result and output in the serial console as before.

...

U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) data training error col error data training error LPDDR3, 800MHz BW=16 Col=12 Bk=8 CS0 Row=16 CS=1 Die BW=8 Size=4096MB I don't know much about Arm, so i don't know what that output means. :)

It is very first stage of bootloader. Do you see anything else next?

Thanks

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

12.02.2020 20:58, ITwrx пишет:

On 2/12/20 11:56 AM, Matwey V. Kornilov wrote:

...

12.02.2020 18:37, ITwrx пишет:

...

...

...

Hi,

It is very strange to hear that. I deployed this image to couple of Rock64-s week ago. So, could you please be more specific? What are you trying to do exactly?

You are supposed to download openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz uncompress it with `xz -d openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz` and write .raw file to microsd card as the following `dd_rescue openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw /dev/your_sd_card_here`. That's what i did, but i'll try it again. I didn't get any errors when writing the image. This time, i'll wipe the sd card and create one fat

On 2/12/20 1:49 AM, Matwey V. Kornilov wrote: partition, just to be on the safe side.

...

Do you have usb rs232 ttl converter to attach the Rock64 console? What does it say? i did, but i don't remember. It didn't get very far. If it fails this time, i'll copy and paste the output.

Thanks

...

ср, 12 февр. 2020 г. в 10:17, Guillaume Gardet :

...

Hi,

> -----Original Message----- > From: ITwrx > Sent: 12 February 2020 03:49 > To: opensuse-arm@opensuse.org > Subject: [opensuse-arm] Rock64 > > Thorston/All, > > i just wanted to report that there are not Rock64 microOS images, only images for > the older pine64. > > Also, the instructions on the Rock64 openSUSE wiki don't work (exactly as they > are), using the below linked image file. I don't know what the corresponding > "packages" file is for or how to use it, so it was not used in any way. The Rock64 The "packages" file is just the list of installed packages in this *.raw.xz image.

> openSUSE wiki page didn't mention anything about it. Probably why the board > won't boot... :) > > http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Roc > kchip/images/openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30- > Build5.29.raw.xz > > Any tips appreciated. Added Matwey in Cc who may help.

Cheers, Guillaume

> Thanks, > > ITwrx > > > -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org > To contact the owner, e-mail: opensuse-arm+owner@opensuse.org Ok, i misspoke earlier. The first time i didn't extract, then run

On 2/12/20 8:59 AM, ITwrx wrote: dd_rescue per your instructions. i ran "xzcat [image].raw.xz | dd bs=4M of=/dev/sdX iflag=fullblock oflag=direct; sync" (substituting relevant info) per the wiki. This time i did use your commands. I got the same result and output in the serial console as before.

...

U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) data training error col error data training error LPDDR3, 800MHz BW=16 Col=12 Bk=8 CS0 Row=16 CS=1 Die BW=8 Size=4096MB I don't know much about Arm, so i don't know what that output means. :) It is very first stage of bootloader. Do you see anything else next? no. That's where it stops, unfortunately. I guess i could try the ALARM install process and see if it stops at the same point, in which case maybe it's an hardware issue.

For me, the output looks like. (My testing board is 2GB, but I successfully use 4GB also) U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) LPDDR3, 800MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2020.01 (Jan 30 2020 - 10:43:44 +0000) Trying to boot from MMC1 NOTICE: BL31: v2.1(debug): NOTICE: BL31: Built : 22:19:57, Sep 4 2019 ERROR: over or zero region, nr=4187432, max=10 NOTICE: BL31:Rockchip release version: v1.2 INFO: ARM GICv2 driver initialized INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services WARNING: BL31: cortex_a53: CPU workaround for 819472 was missing! WARNING: BL31: cortex_a53: CPU workaround for 824069 was missing! WARNING: BL31: cortex_a53: CPU workaround for 827319 was missing! WARNING: BL31: cortex_a53: CPU workaround for 855873 was missing! INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 Well, maybe something is still wrong with U-boot (It is known to be not quite stable for Rock64 at the time of 2019.10 release). Could you try this section? https://en.opensuse.org/HCL:Rock64#Using_proprietary_TPL_bootloader If the proprietary boot-loader works, then the issue should be reported to u-boot maillist.

...

...

Thanks

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 2/12/20 12:07 PM, Matwey V. Kornilov wrote:

12.02.2020 20:58, ITwrx пишет:

...

On 2/12/20 11:56 AM, Matwey V. Kornilov wrote:

...

12.02.2020 18:37, ITwrx пишет:

...

...

...

Hi,

It is very strange to hear that. I deployed this image to couple of Rock64-s week ago. So, could you please be more specific? What are you trying to do exactly?

You are supposed to download openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz uncompress it with `xz -d openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz` and write .raw file to microsd card as the following `dd_rescue openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw /dev/your_sd_card_here`. That's what i did, but i'll try it again. I didn't get any errors when writing the image. This time, i'll wipe the sd card and create one fat

On 2/12/20 1:49 AM, Matwey V. Kornilov wrote: partition, just to be on the safe side.

...

Do you have usb rs232 ttl converter to attach the Rock64 console? What does it say? i did, but i don't remember. It didn't get very far. If it fails this time, i'll copy and paste the output.

Thanks

...

ср, 12 февр. 2020 г. в 10:17, Guillaume Gardet : > Hi, > >> -----Original Message----- >> From: ITwrx >> Sent: 12 February 2020 03:49 >> To: opensuse-arm@opensuse.org >> Subject: [opensuse-arm] Rock64 >> >> Thorston/All, >> >> i just wanted to report that there are not Rock64 microOS images, only images for >> the older pine64. >> >> Also, the instructions on the Rock64 openSUSE wiki don't work (exactly as they >> are), using the below linked image file. I don't know what the corresponding >> "packages" file is for or how to use it, so it was not used in any way. The Rock64 > The "packages" file is just the list of installed packages in this *.raw.xz image. > >> openSUSE wiki page didn't mention anything about it. Probably why the board >> won't boot... :) >> >> http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Roc >> kchip/images/openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30- >> Build5.29.raw.xz >> >> Any tips appreciated. > Added Matwey in Cc who may help. > > Cheers, > Guillaume > >> Thanks, >> >> ITwrx >> >> >> -- >> To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org >> To contact the owner, e-mail: opensuse-arm+owner@opensuse.org Ok, i misspoke earlier. The first time i didn't extract, then run

On 2/12/20 8:59 AM, ITwrx wrote: dd_rescue per your instructions. i ran "xzcat [image].raw.xz | dd bs=4M of=/dev/sdX iflag=fullblock oflag=direct; sync" (substituting relevant info) per the wiki. This time i did use your commands. I got the same result and output in the serial console as before.

...

U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) data training error col error data training error LPDDR3, 800MHz BW=16 Col=12 Bk=8 CS0 Row=16 CS=1 Die BW=8 Size=4096MB I don't know much about Arm, so i don't know what that output means. :) It is very first stage of bootloader. Do you see anything else next? no. That's where it stops, unfortunately. I guess i could try the ALARM install process and see if it stops at the same point, in which case maybe it's an hardware issue. For me, the output looks like. (My testing board is 2GB, but I successfully use 4GB also)

U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) LPDDR3, 800MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Trying to boot from BOOTROM Returning to boot ROM...

U-Boot SPL 2020.01 (Jan 30 2020 - 10:43:44 +0000) Trying to boot from MMC1 NOTICE: BL31: v2.1(debug): NOTICE: BL31: Built : 22:19:57, Sep 4 2019 ERROR: over or zero region, nr=4187432, max=10 NOTICE: BL31:Rockchip release version: v1.2 INFO: ARM GICv2 driver initialized INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services WARNING: BL31: cortex_a53: CPU workaround for 819472 was missing! WARNING: BL31: cortex_a53: CPU workaround for 824069 was missing! WARNING: BL31: cortex_a53: CPU workaround for 827319 was missing! WARNING: BL31: cortex_a53: CPU workaround for 855873 was missing! INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9

Well, maybe something is still wrong with U-boot (It is known to be not quite stable for Rock64 at the time of 2019.10 release).

Could you try this section? https://en.opensuse.org/HCL:Rock64#Using_proprietary_TPL_bootloader

If the proprietary boot-loader works, then the issue should be reported to u-boot maillist.

It booted the first time after installing the proprietary bootloader, and got all the way to the login prompt, but at that point showed some btrfs filesystem error, and i was unable to login or connect via ssh. I rewrote the files to the sd card (and another card) and now it boots but keeps failing to get to the login prompt with different sd card/filesystem related errors, with the latest round of errors (these have been the same the last few times i've tried it) pasted here: https://pastebin.com/QBrR3KsL I have not had any problems with these sd cards otherwise. Is there any specific preparation i should do before rewriting the files to the sd card to try again? btw, my board says "Rock64 v2.0 2017-0713". thanks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 2/13/20 7:40 AM, Matwey V. Kornilov wrote:

13.02.2020 06:49, ITwrx пишет:

...

On 2/12/20 12:07 PM, Matwey V. Kornilov wrote:

...

12.02.2020 20:58, ITwrx пишет:

...

On 2/12/20 11:56 AM, Matwey V. Kornilov wrote:

...

12.02.2020 18:37, ITwrx пишет:

...

On 2/12/20 8:59 AM, ITwrx wrote: > On 2/12/20 1:49 AM, Matwey V. Kornilov wrote: >> Hi, >> >> It is very strange to hear that. I deployed this image to couple of >> Rock64-s week ago. >> So, could you please be more specific? What are you trying to do exactly? >> >> You are supposed to download >> openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz >> uncompress it with `xz -d >> openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz` >> and write .raw file to microsd card as the following `dd_rescue >> openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw >> /dev/your_sd_card_here`. > That's what i did, but i'll try it again. I didn't get any errors when > writing the image. This time, i'll wipe the sd card and create one fat > partition, just to be on the safe side. >> Do you have usb rs232 ttl converter to attach the Rock64 console? What >> does it say? > i did, but i don't remember. It didn't get very far. If it fails this > time, i'll copy and paste the output. > > Thanks > >> ср, 12 февр. 2020 г. в 10:17, Guillaume Gardet : >>> Hi, >>> >>>> -----Original Message----- >>>> From: ITwrx >>>> Sent: 12 February 2020 03:49 >>>> To: opensuse-arm@opensuse.org >>>> Subject: [opensuse-arm] Rock64 >>>> >>>> Thorston/All, >>>> >>>> i just wanted to report that there are not Rock64 microOS images, only images for >>>> the older pine64. >>>> >>>> Also, the instructions on the Rock64 openSUSE wiki don't work (exactly as they >>>> are), using the below linked image file. I don't know what the corresponding >>>> "packages" file is for or how to use it, so it was not used in any way. The Rock64 >>> The "packages" file is just the list of installed packages in this *.raw.xz image. >>> >>>> openSUSE wiki page didn't mention anything about it. Probably why the board >>>> won't boot... :) >>>> >>>> http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Roc >>>> kchip/images/openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30- >>>> Build5.29.raw.xz >>>> >>>> Any tips appreciated. >>> Added Matwey in Cc who may help. >>> >>> Cheers, >>> Guillaume >>> >>>> Thanks, >>>> >>>> ITwrx >>>> >>>> >>>> -- >>>> To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org >>>> To contact the owner, e-mail: opensuse-arm+owner@opensuse.org Ok, i misspoke earlier. The first time i didn't extract, then run dd_rescue per your instructions. i ran "xzcat [image].raw.xz | dd bs=4M of=/dev/sdX iflag=fullblock oflag=direct; sync" (substituting relevant info) per the wiki. This time i did use your commands. I got the same result and output in the serial console as before.

> U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) > data training error > col error > data training error > LPDDR3, 800MHz > BW=16 Col=12 Bk=8 CS0 Row=16 CS=1 Die BW=8 Size=4096MB I don't know much about Arm, so i don't know what that output means. :) It is very first stage of bootloader. Do you see anything else next? no. That's where it stops, unfortunately. I guess i could try the ALARM install process and see if it stops at the same point, in which case maybe it's an hardware issue. For me, the output looks like. (My testing board is 2GB, but I successfully use 4GB also)

U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) LPDDR3, 800MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Trying to boot from BOOTROM Returning to boot ROM...

U-Boot SPL 2020.01 (Jan 30 2020 - 10:43:44 +0000) Trying to boot from MMC1 NOTICE: BL31: v2.1(debug): NOTICE: BL31: Built : 22:19:57, Sep 4 2019 ERROR: over or zero region, nr=4187432, max=10 NOTICE: BL31:Rockchip release version: v1.2 INFO: ARM GICv2 driver initialized INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services WARNING: BL31: cortex_a53: CPU workaround for 819472 was missing! WARNING: BL31: cortex_a53: CPU workaround for 824069 was missing! WARNING: BL31: cortex_a53: CPU workaround for 827319 was missing! WARNING: BL31: cortex_a53: CPU workaround for 855873 was missing! INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9

Well, maybe something is still wrong with U-boot (It is known to be not quite stable for Rock64 at the time of 2019.10 release).

Could you try this section? https://en.opensuse.org/HCL:Rock64#Using_proprietary_TPL_bootloader

If the proprietary boot-loader works, then the issue should be reported to u-boot maillist. It booted the first time after installing the proprietary bootloader, and got all the way to the login prompt, but at that point showed some btrfs filesystem error, and i was unable to login or connect via ssh. I Could you please try another microsd card? There should be no any btrfs errors on brand new JeOS image.

I already tried the only two spare cards i have. I just ordered some Sandisk Industrial micro sd cards. If that doesn't work out, i'll get an eMMC module and usb adapter and try that. Once i can verify with working storage, i'll report the u-boot issue, as i didn't buy this *more open* board to run a proprietary anything... I'll also look into adding a note to the wiki about the Rock64 version 2, depending on what happens. Thanks for all the help! -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 2/12/20 12:18 PM, Brüns, Stefan wrote:

On Mittwoch, 12. Februar 2020 16:37:28 CET ITwrx wrote:

...

...

On 2/12/20 1:49 AM, Matwey V. Kornilov wrote: Ok, i misspoke earlier. The first time i didn't extract, then run

On 2/12/20 8:59 AM, ITwrx wrote: dd_rescue per your instructions. i ran "xzcat [image].raw.xz | dd bs=4M of=/dev/sdX iflag=fullblock oflag=direct; sync" (substituting relevant info) per the wiki. This time i did use your commands. I got the same result and output in the serial console as before.

...

U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) data training error col error data training error LPDDR3, 800MHz BW=16 Col=12 Bk=8 CS0 Row=16 CS=1 Die BW=8 Size=4096MB I don't know much about Arm, so i don't know what that output means. :) This is the automatic delay adjustments to balance the trace lengths.

Three possible reasons it fails:

1. bad board 2. initial timing settings too much off for the training to lock 3. unknown/new/different RAM chips which require a different setting

Obviously, your RAM configuration is different from Matweys:

...

U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) LPDDR3, 800MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Kind regards,

Stefan

Interesting. Thanks for your input. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org