LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > slarm64
User Name
Password
slarm64 This forum is for the discussion of slarm64.

Notices


Reply
  Search this Thread
Old 03-17-2022, 05:03 AM   #16
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,866

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by shelldweller View Post
Hmmm... alright. Now I am getting a different error in roughly the same spot:

Code:
  MKIMAGE tpl/u-boot-tpl-rockchip.bin
  CAT     idbloader.img
  CAT     u-boot-rockchip.bin
  UPD     include/generated/timestamp_autogenerated.h
  CC      cmd/version.o
  AR      cmd/built-in.o
  LD      u-boot
  OBJCOPY u-boot-nodtb.bin
./"arch/arm/mach-rockchip/make_fit_atf.py" \
arch/arm/dts/rk3328-rock64.dtb > u-boot.its
  RELOC   u-boot-nodtb.bin
  MKIMAGE u-boot.itb
/hdd/slarm64/images_build_kit/build/source/u-boot /hdd/slarm64/images_build_kit/build/source/u-boot
Error: SPL image is too large (size 0x7800 than 0x7000)
Error: Bad parameters for image type
Usage: tools/mkimage -l image
          -l ==> list image header information
       tools/mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] image
          -A ==> set architecture to 'arch'
          -O ==> set operating system to 'os'
          -T ==> set image type to 'type'
          -C ==> set compression type 'comp'
          -a ==> set load address to 'addr' (hex)
          -e ==> set entry point to 'ep' (hex)
          -n ==> set image name to 'name'
          -d ==> use image data from 'datafile'
          -x ==> set XIP (execute in place)
       tools/mkimage [-D dtc_options] [-f fit-image.its|-f auto|-F] [-b <dtb> [-b <dtb>]] [-E] [-B size] [-i <ramdisk.cpio.gz>] fit-image
           <dtb> file is used with -f auto, it may occur multiple times.
          -D => set all options for device tree compiler
          -f => input filename for FIT source
          -i => input filename for ramdisk file
          -E => place data outside of the FIT structure
          -B => align size in hex for FIT structure and header
Signing / verified boot options: [-k keydir] [-K dtb] [ -c <comment>] [-p addr] [-r] [-N engine]
          -k => set directory containing private keys
          -K => write public keys to this .dtb file
          -G => use this signing key (in lieu of -k)
          -c => add comment in signature node
          -F => re-sign existing FIT image
          -p => place external data at a static position
          -r => mark keys used as 'required' in dtb
          -N => openssl engine to use for signing
       tools/mkimage -V ==> print version information and exit
Use '-T list' to see a list of available image types

I have tried switching between the two sources for rkbin as well as u-boot-tools in config/sources/rockchip.inc, but nothing lets me get past the u-boot compilation stage above.

FWIW, I am getting something similar when I try to build images for Quartz64 also. So, maybe something is going on with the rockchip boot sources and I just need to be more patient.

Just for your info, nothing critical. Thanks much.
Fixed, this is due to rk3328_ddr_333MHz_v1.19.bin, the size is larger than version 1.17.
 
1 members found this post helpful.
Old 03-18-2022, 10:22 PM   #17
shelldweller
Member
 
Registered: Mar 2019
Distribution: Slackware
Posts: 300

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
Fixed, this is due to rk3328_ddr_333MHz_v1.19.bin, the size is larger than version 1.17.
Excellent, thank you. After a few tries, I was able to build a fresh legacy image. That is all I was after. Much appreciated.
 
Old 11-05-2022, 12:35 AM   #21
downhomechunk
LQ Newbie
 
Registered: Dec 2007
Location: chicago
Distribution: slackware
Posts: 25

Rep: Reputation: 7
first of all, thank you sndwvs for maintaining this. i'm a total n00b to SBCs. i bought one of these on a whim and am hoping to get some form of slackware ARM up and running on it. i thought this thread was the answer since it's the same chipset but i'm not having any luck so far. any tips?

https://www.libre.computer/products/roc-rk3328-cc/
 
Old 11-05-2022, 09:57 AM   #22
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,866

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by downhomechunk View Post
first of all, thank you sndwvs for maintaining this. i'm a total n00b to SBCs. i bought one of these on a whim and am hoping to get some form of slackware ARM up and running on it. i thought this thread was the answer since it's the same chipset but i'm not having any luck so far. any tips?

https://www.libre.computer/products/roc-rk3328-cc/
the easiest way is to install a working image of any system (if there is no bootloader that can be written separately) and then just rewrite everything from the rock64 image and change the DTB name in the /boot/uEnv.txt file to rk3328-roc-cc.dtb
or try the image of the station m1, it is the closest.
 
1 members found this post helpful.
Old 06-22-2023, 09:19 AM   #26
shelldweller
Member
 
Registered: Mar 2019
Distribution: Slackware
Posts: 300

Rep: Reputation: Disabled
Hi sndwvs, I hope you're well.

I was trying to build a fresh set of kernel packages for the Rock64 (my only board left after a fire), and I ran into this error while downloading the sources:

Code:
|----------- delimiter ----------- "download" "linux-next" -----------|
HEAD is now at 6ab3eda15 Linux 6.2.2
error: pathspec 'linux-6.3.y' did not match any file(s) known to git
Seems like it's on the wrong branch now. What branch should this board be on for the next kernel, and where do I change that line? I checked in config/sources/rk3328.conf and config/sources/rockchip.inc, but the 6.3.y url must be coming from somewhere else. Any ideas?

thanks so much, keep up the great work!
 
Old 06-22-2023, 02:08 PM   #27
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,866

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by shelldweller View Post
Hi sndwvs, I hope you're well.

I was trying to build a fresh set of kernel packages for the Rock64 (my only board left after a fire), and I ran into this error while downloading the sources:

Code:
|----------- delimiter ----------- "download" "linux-next" -----------|
HEAD is now at 6ab3eda15 Linux 6.2.2
error: pathspec 'linux-6.3.y' did not match any file(s) known to git
Seems like it's on the wrong branch now. What branch should this board be on for the next kernel, and where do I change that line? I checked in config/sources/rk3328.conf and config/sources/rockchip.inc, but the 6.3.y url must be coming from somewhere else. Any ideas?

thanks so much, keep up the great work!
Hi shelldweller,

It's very unfortunate that this happened to you.
So far so good thank you.

Very similar to the fact that in the images_build_kit/build/source kernel-next folder contains the old downloaded kernel, you need to delete the kernel-next folder
 
1 members found this post helpful.
Old 06-23-2023, 08:41 AM   #28
shelldweller
Member
 
Registered: Mar 2019
Distribution: Slackware
Posts: 300

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
Hi shelldweller,

It's very unfortunate that this happened to you.
So far so good thank you.

Very similar to the fact that in the images_build_kit/build/source kernel-next folder contains the old downloaded kernel, you need to delete the kernel-next folder
Hi sndwvs. Perfect, that fixed the problem. I should have remembered to clean out the build directory, I've run into that before. It's been a while since I've messed around with the script though. Thanks for the tip, keep up the good work!
 
  


Reply

Tags
pine64 team, rk3328, rockchip, slackware, slarm64


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware for Rock64 RK3328 sndwvs Slackware - ARM 83 01-25-2022 03:49 PM
[SOLVED] Station M1(RK3328)/P1(RK3399) (slarm64, aarch64) sndwvs Slackware - ARM 10 12-07-2021 10:34 AM
[SOLVED] Rock Pi E RK3328 (aarch64) sndwvs Slackware - ARM 10 12-07-2021 10:23 AM
LXer: Meet ROCK64, a 4K-Capable Single-Board Computer That Can Run Android 7.1, Debian LXer Syndicated Linux News 0 07-07-2017 09:30 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > slarm64

All times are GMT -5. The time now is 06:06 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration