Jump to content

    

Промышленный компьютер тион-про28

2 hours ago, Alex_Golubev said:

Но нужно найти причину почему рухнул init

Попробуйте полностью пересобрать отдельно rootfs в формате ext4 и указать ее как rootfs в kernel command line

Share this post


Link to post
Share on other sites

Посмотрите эта нормальная загрузка. 

Спойлер

<0>HTLLCLLC

U-Boot 2018.05 (Jun 01 2019 - 10:36:30 +0700)

CPU:   Freescale i.MX28 rev1.2 at 454 MHz
BOOT:  SSP SD/MMC #0, 3V3
SPI:   ready
DRAM:  128 MiB
No arch specific invalidate_icache_all available!
NAND:  256 MiB
MMC:   MXS MMC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Failed (-5)
Video: MXSFB: 'videomode' variable not set!
In:    serial
Out:   serial
Err:   serial
Net:   FEC0 [PRIME], FEC1
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
** Unable to read file boot.scr **
4506272 bytes read in 1334 ms (3.2 MiB/s)
Booting from mmc ...
22316 bytes read in 31 ms (702.1 KiB/s)
Kernel image @ 0x42000000 [ 0x000000 - 0x44c2a0 ]
## Flattened Device Tree blob at 41000000
   Booting using the fdt blob at 0x41000000
   Loading Device Tree to 47b17000, end 47b1f72b ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.17.8 (alexey@debian) (gcc version 7.4.0 (Buildroot 2019.02.2)) #1 Sat Jun 1 10:44:59 +07 2019
[    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=0005317f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] OF: fdt: Machine model: Freescale i.MX28 Evaluation Kit
[    0.000000] Memory policy: Data cache writeback
[    0.000000] random: get_random_bytes called from start_kernel+0x84/0x474 with crng_init=0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyAMA0,115200 root=/dev/mmcblk0p3 rw rootwait
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 113240K/131072K available (6064K kernel code, 555K rwdata, 2004K rodata, 304K init, 7442K bss, 17832K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff800000   ( 880 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0x(ptrval) - 0x(ptrval)   (6066 kB)
[    0.000000]       .init : 0x(ptrval) - 0x(ptrval)   ( 304 kB)
[    0.000000]       .data : 0x(ptrval) - 0x(ptrval)   ( 556 kB)
[    0.000000]        .bss : 0x(ptrval) - 0x(ptrval)   (7443 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Running RCU self tests
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] clocksource: mxs_timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000033] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.002273] Console: colour dummy device 80x30
[    0.002438] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
[    0.002504] ... MAX_LOCKDEP_SUBCLASSES:  8
[    0.002558] ... MAX_LOCK_DEPTH:          48
[    0.002609] ... MAX_LOCKDEP_KEYS:        8191
[    0.002658] ... CLASSHASH_SIZE:          4096
[    0.002709] ... MAX_LOCKDEP_ENTRIES:     32768
[    0.002759] ... MAX_LOCKDEP_CHAINS:      65536
[    0.002808] ... CHAINHASH_SIZE:          32768
[    0.002859]  memory used by lock dependency info: 4655 kB
[    0.002909]  per task-struct memory footprint: 1536 bytes
[    0.003109] Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)
[    0.071451] pid_max: default: 32768 minimum: 301
[    0.072584] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.072694] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.081161] CPU: Testing write buffer coherency: ok
[    0.090262] Setting up static identity map for 0x40008400 - 0x40008458
[    0.103284] devtmpfs: initialized
[    0.164999] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.165245] futex hash table entries: 256 (order: 1, 11264 bytes)
[    0.166897] pinctrl core: initialized pinctrl subsystem
[    0.181166] NET: Registered protocol family 16
[    0.184165] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.389304] Serial: AMBA PL011 UART driver
[    0.392929] 80074000.serial: ttyAMA0 at MMIO 0x80074000 (irq = 236, base_baud = 0) is a PL011 rev2
[    0.712803] console [ttyAMA0] enabled
[    0.799819] mxs-dma 80004000.dma-apbh: initialized
[    0.817835] mxs-dma 80024000.dma-apbx: initialized
[    0.844870] SCSI subsystem initialized
[    0.851838] usbcore: registered new interface driver usbfs
[    0.858108] usbcore: registered new interface driver hub
[    0.864422] usbcore: registered new device driver usb
[    0.879292] pps_core: LinuxPPS API ver. 1 registered
[    0.884560] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.893972] PTP clock support registered
[    0.900931] Advanced Linux Sound Architecture Driver Initialized.
[    0.915445] clocksource: Switched to clocksource mxs_timer
[    1.572353] NET: Registered protocol family 2
[    1.582003] tcp_listen_portaddr_hash hash table entries: 128 (order: 0, 5120 bytes)
[    1.590191] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    1.597550] TCP bind hash table entries: 1024 (order: 3, 36864 bytes)
[    1.604964] TCP: Hash tables configured (established 1024 bind 1024)
[    1.612694] UDP hash table entries: 256 (order: 2, 20480 bytes)
[    1.619482] UDP-Lite hash table entries: 256 (order: 2, 20480 bytes)
[    1.627695] NET: Registered protocol family 1
[    1.638596] RPC: Registered named UNIX socket transport module.
[    1.644857] RPC: Registered udp transport module.
[    1.649890] RPC: Registered tcp transport module.
[    1.654683] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.676129] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[    1.766063] NFS: Registering the id_resolver key type
[    1.772308] Key type id_resolver registered
[    1.777065] Key type id_legacy registered
[    1.781660] jffs2: version 2.2. (NAND) В© 2001-2006 Red Hat, Inc.
[    1.813279] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[    1.821294] io scheduler noop registered (default)
[    1.826424] io scheduler mq-deadline registered
[    1.831054] io scheduler kyber registered
[    1.844829] pwm-backlight backlight: backlight supply power not found, using dummy regulator
[    1.903644] Console: switching to colour frame buffer device 100x30
[    1.930779] mxsfb 80030000.lcdif: initialized
[    1.942538] 8006a000.serial: ttyAPP0 at MMIO 0x8006a000 (irq = 234, base_baud = 1500000) is a 8006a000.serial
[    1.954797] mxs-auart 8006a000.serial: Found APPUART 3.1.0
[    1.963078] 80070000.serial: ttyAPP3 at MMIO 0x80070000 (irq = 235, base_baud = 1500000) is a 80070000.serial
[    1.975749] mxs-auart 80070000.serial: Found APPUART 3.1.0
[    2.028851] random: fast init done
[    2.069620] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    2.076285] nand: Micron MT29F2G08ABAEAWP
[    2.080390] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    2.096629] Scanning device for bad blocks
[    3.363286] gpmi-nand 8000c000.gpmi-nand: driver registered.
[    3.396177] m25p80 spi1.0: unrecognized JEDEC id bytes: ff, ff, ff
[    3.407919] libphy: Fixed MDIO Bus: probed
[    3.564483] libphy: fec_enet_mii_bus: probed
[    3.575000] fec 800f4000.ethernet: 800f4000.ethernet supply phy not found, using dummy regulator
[    3.592310] usbcore: registered new interface driver asix
[    3.598445] usbcore: registered new interface driver ax88179_178a
[    3.604991] usbcore: registered new interface driver cdc_ether
[    3.611656] usbcore: registered new interface driver smsc95xx
[    3.618132] usbcore: registered new interface driver net1080
[    3.624287] usbcore: registered new interface driver cdc_subset
[    3.630892] usbcore: registered new interface driver zaurus
[    3.637338] usbcore: registered new interface driver cdc_ncm
[    3.643094] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.650455] usbcore: registered new interface driver usb-storage
[    3.688003] ci_hdrc ci_hdrc.1: EHCI Host Controller
[    3.693983] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1
[    3.725757] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
[    3.746362] hub 1-0:1.0: USB hub found
[    3.751292] hub 1-0:1.0: 1 port detected
[    3.771453] input: mxs-lradc-ts as /devices/soc0/80000000.apb/80040000.apbx/80050000.lradc/mxs-lradc-ts/input/input0
[    3.792297] stmp3xxx-rtc 80056000.rtc: rtc core: registered 80056000.rtc as rtc0
[    3.801868] i2c /dev entries driver
[    3.816214] stmp3xxx_rtc_wdt stmp3xxx_rtc_wdt: initialized watchdog with heartbeat 19s
[    3.861166] mxs-mmc 80010000.ssp: initialized
[    3.890329] mxs-dcp 80028000.dcp: Failed to register sha1 hash!
[    3.899962] mxs-dcp: probe of 80028000.dcp failed with error -22
[    3.913606] usbcore: registered new interface driver usbhid
[    3.919521] usbhid: USB HID core driver
[    3.936086] mmc0: host does not support reading read-only switch, assuming write-enable
[    3.956651] mmc0: new high speed SDHC card at address aaaa
[    3.980865] mmcblk0: mmc0:aaaa SL16G 14.8 GiB 
[    4.011557] mxs-sgtl5000 sound: ASoC: CODEC DAI sgtl5000 not registered
[    4.027447]  mmcblk0: p1 p2 p3
[    4.034483] NET: Registered protocol family 17
[    4.044373] Key type dns_resolver registered
[    4.067916] registered taskstats version 1
[    4.155152] sgtl5000 0-000a: Error reading chip id -6
[    4.166761] mxs-sgtl5000 sound: ASoC: CODEC DAI sgtl5000 not registered
[    4.177234] stmp3xxx-rtc 80056000.rtc: setting system clock to 1970-01-01 00:00:09 UTC (9)
[    4.187384] usb0_vbus: disabling
[    4.191076] can-3v3: disabling
[    4.194224] ALSA device list:
[    4.197505]   No soundcards found.
[    4.206220] uart-pl011 80074000.serial: no DMA platform data
[    4.228730] EXT4-fs (mmcblk0p3): mounting ext2 file system using the ext4 subsystem
[    4.281995] EXT4-fs (mmcblk0p3): mounted filesystem without journal. Opts: (null)
[    4.290409] VFS: Mounted root (ext2 filesystem) on device 179:3.
[    4.314535] devtmpfs: mounted
[    4.320364] Freeing unused kernel memory: 304K
[    4.324905] This architecture does not have kernel memory protection.
[    4.593170] EXT4-fs (mmcblk0p3): re-mounted. Opts: block_validity,barrier,user_xattr
Starting syslogd: OK
Starting klogd: OK
Initializing random number generator... [    5.224032] random: dd: uninitialized urandom read (512 bytes read)
done.
Starting network: OK


Welcome to Buildroot

buildroot login: [  103.896738] random: crng init done

не понравилось random: crng init done. Но ядро отвечает. 

 

Share this post


Link to post
Share on other sites

Да, нормальная. "random: crng init done" - это просто сообщение ядра о завершении инициализации источника случайных чисел.

Смотрю, откатились на старый конфиг. По-видимому, что-то не так с тулчейном. Я его раньше не использовал, но та же версия для

ядер с hard float (-gnueabihf) точно работает нормально. Предлагаю оставить пока встроенный тулчейн buildroot, а ядро собрать

из внешнего источника.

Share this post


Link to post
Share on other sites
Цитата

По-видимому, что-то не так с тулчейном

А если использовать gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabi ?

Share this post


Link to post
Share on other sites
4 minutes ago, Alex_Golubev said:

А если использовать gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabi ?

Можно попробовать, хотя я бы двинулся в обратном направлении, в сторону более старых версий.

Share this post


Link to post
Share on other sites
Цитата

двинулся в обратном направлении

Порекомендуйте какой можно использовать тулчайн?

А то я уже боюсь что-то брать. 

Edited by Alex_Golubev

Share this post


Link to post
Share on other sites
Цитата

Предлагаю оставить пока встроенный тулчейн buildroot, а ядро собрать

из внешнего источника.

Попробовал сделать и получил ошибку.

Спойлер

rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_rsynced
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_staging_installed
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_target_installed
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_images_installed
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_host_installed
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_built
/usr/bin/make -j1 O=/home/alexey/work/buildroot/output HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" syncconfig
make[1]: вход в каталог «/home/alexey/work/buildroot»
make[1]: выход из каталога «/home/alexey/work/buildroot»
>>> linux-headers 4.19 Downloading
--2019-06-01 19:15:22--  https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.19.tar.xz
Распознаётся cdn.kernel.org (cdn.kernel.org)… 151.101.1.176, 151.101.65.176, 151.101.129.176, ...
Подключение к cdn.kernel.org (cdn.kernel.org)|151.101.1.176|:443... соединение установлено.
HTTP-запрос отправлен. Ожидание ответа… 200 OK
Длина: 103117552 (98M) [application/x-xz]
Сохранение в: «/home/alexey/work/buildroot/output/build/.linux-4.19.tar.xz.UHLq8e/output»

/home/alexey/work/b 100%[===================>]  98,34M   341KB/s    in 5m 24s  

2019-06-01 19:21:09 (311 KB/s) - «/home/alexey/work/buildroot/output/build/.linux-4.19.tar.xz.UHLq8e/output» сохранён [103117552/103117552]

ERROR: No hash found for linux-4.19.tar.xz
package/pkg-generic.mk:143: ошибка выполнения рецепта для цели «/home/alexey/work/buildroot/output/build/linux-headers-4.19/.stamp_downloaded»
make: *** [/home/alexey/work/buildroot/output/build/linux-headers-4.19/.stamp_downloaded] Ошибка 1

 

 

Share this post


Link to post
Share on other sites

Есть local.mk. 

Хочу уточнить.

Теперь этап "Перейти на внешний тулчейн" не нужен?

Внешнем тулчейном собираем ядро 4.19. Использую gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi

 

Прицепляем внешнее ядро.

1. В ~/work/buildroot создаем файл local.mk со следующим содержимым:

LINUX_OVERRIDE_SRCDIR = ../linux

2. Правим конфигурацию:

  │ │    [*] Linux Kernel                                                 │ │  
  │ │          *** Linux kernel in thumb mode may be broken with binutils │ │  
  │ │          Kernel version (Custom version)  --->                      │ │  
  │ │    (4.19) Kernel version                                            │ │  
  │ │    ()    Custom kernel patches                                      │ │  
  │ │          Kernel configuration (Using a custom (def)config file)  ---│ │  
  │ │    (kernel.config) Configuration file path                          │ │  
  │ │    ()    Additional configuration fragment files                    │ │  
  │ │    ()    Custom boot logo file path                                 │ │  
  │ │          Kernel binary format (zImage)  --->                        │ │  
  │ │          Kernel compression format (gzip compression)  --->         │ │  
  │ │    [*]   Build a Device Tree Blob (DTB)                             │ │  
  │ │    (imx28-evk) In-tree Device Tree Source file names                │ │  
  │ │    ()      Out-of-tree Device Tree Source file paths                │ │  
  │ │    [ ]   Install kernel image to /boot in target                    │ │  
  │ │    [ ]   Needs host OpenSSL                                         │ │  
  │ │    [ ]   Needs host libelf                                          │ │  
  │ │          Linux Kernel Extensions  --->                              │ │  
  │ │          Linux Kernel Tools  --->                                   │ │  
	

3. Копируем linux/.config в buildroot/kernel.config

Пробуем собрать:

.../buildroot$ make linux-rebuild

 

Все правильно?

Edited by Alex_Golubev

Share this post


Link to post
Share on other sites

Да, все тоже самое, но на встроенном тулчейне.

Share this post


Link to post
Share on other sites

А внешней тулчейн подключать не будем? Может есть какой рабочий ?

 

Edited by Alex_Golubev

Share this post


Link to post
Share on other sites

Посмотрите пожалуйста все сделал правильно?

Спойлер

alexey@debian:~/work/buildroot$ ls -a
.        Config.in         DEVELOPERS  .gitlab-ci.yml     output
..       Config.in.legacy  dl          .gitlab-ci.yml.in  package
arch     .config.old       docs        kernel.config      README
board    configs           .flake8     linux              support
boot     ..config.tmp      fs          local.mk           system
CHANGES  COPYING           .git        Makefile           toolchain
.config  .defconfig        .gitignore  Makefile.legacy    utils
alexey@debian:~/work/buildroot$ md5sum /home/alexey/work/buildroot/kernel.config9851c01b06ce65bb0246c660ee40fe1b  /home/alexey/work/buildroot/kernel.config
alexey@debian:~/work/buildroot$ md5sum /home/alexey/work/linux/.config9851c01b06ce65bb0246c660ee40fe1b  /home/alexey/work/linux/.config
alexey@debian:~/work/buildroot$ ls -a

 

Спойлер

  [*] Linux Kernel                                                       │ │  
  │ │          Kernel version (Custom version)  --->                            │ │  
  │ │    (4.19) Kernel version                                                  │ │  
  │ │    ()    Custom kernel patches                                            │ │  
  │ │          Kernel configuration (Using a custom (def)config file)  --->     │ │  
  │ │    (/home/alexey/work/buildroot/kernel.config) Configuration file path    │ │  
  │ │    ()    Additional configuration fragment files                          │ │  
  │ │    ()    Custom boot logo file path                                       │ │  
  │ │          Kernel binary format (zImage)  --->                              │ │  
  │ │          Kernel compression format (gzip compression)  --->               │ │  
  │ │    [*]   Build a Device Tree Blob (DTB)                                   │ │  
  │ │    (imx28-evk) In-tree Device Tree Source file names                      │ │  
  │ │    ()      Out-of-tree Device Tree Source file paths                      │ │  
  │ │    [ ]     Build Device Tree with overlay support                         │ │  
  │ │    [ ]   Install kernel image to /boot in target                          │ │  
  │ │    [ ]   Needs host OpenSSL                                               │ │  
  │ │    [ ]   Needs host libelf                                                │ │  
  │ │          Linux Kernel Extensions  --->                                    │ │  
  │ │          Linux Kernel Tools  --->  

 

Спойлер

    Toolchain type (Buildroot toolchain)  --->                             │ │  
  │ │        *** Toolchain Buildroot Options ***                                    │ │  
  │ │    (buildroot) custom toolchain vendor name                                   │ │  
  │ │        C library (uClibc-ng)  --->                                            │ │  
  │ │        *** Kernel Header Options ***                                          │ │  
  │ │        Kernel Headers (Same as kernel being built)  --->                      │ │  
  │ │        Custom kernel headers series (4.17.x)  --->                            │ │  
  │ │        *** uClibc Options ***                                                 │ │  
  │ │    (package/uclibc/uClibc-ng.config) uClibc configuration file to use?        │ │  
  │ │    ()  Additional uClibc configuration fragment files                         │ │  
  │ │    [ ] Enable WCHAR support                                                   │ │  
  │ │    [ ] Enable toolchain locale/i18n support                                   │ │  
  │ │        Thread library implementation (Native POSIX Threading (NPTL))  --->    │ │  
  │ │    [ ] Thread library debugging                                               │ │  
  │ │    [ ] Enable stack protection support                                        │ │  
  │ │    [*] Compile and install uClibc utilities                                   │ │  
  │ │        *** Binutils Options ***                                               │ │  
  │ │        Binutils Version (binutils 2.31.1)  --->                               │ │  
  │ │    ()  Additional binutils options                                            │ │  
  │ │        *** GCC Options ***                                                    │ │  
  │ │        GCC compiler Version (gcc 7.x)  --->                                   │ │  
  │ │    ()  Additional gcc options                                                 │ │  
  │ │    [ ] Enable C++ support                                                     │ │  
  │ │    [ ] Enable Fortran support                                                 │ │  
  │ │    [ ] Enable compiler link-time-optimization support                         │ │  
  │ │    [ ] Enable compiler OpenMP support                                         │ │  
  │ │    [ ] Enable graphite support                                                │ │  
  │ │        *** Host GDB Options *** 

 

 

Share this post


Link to post
Share on other sites

Ошибка 

Спойлер

rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_rsynced
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_staging_installed
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_target_installed
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_images_installed
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_host_installed
rm -f /home/alexey/work/buildroot/output/build/linux-custom/.stamp_built
/usr/bin/make -j1 O=/home/alexey/work/buildroot/output HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" syncconfig
make[1]: вход в каталог «/home/alexey/work/buildroot»
make[1]: выход из каталога «/home/alexey/work/buildroot»
>>> linux-headers 4.19 Downloading
--2019-06-01 19:15:22--  https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.19.tar.xz
Распознаётся cdn.kernel.org (cdn.kernel.org)… 151.101.1.176, 151.101.65.176, 151.101.129.176, ...
Подключение к cdn.kernel.org (cdn.kernel.org)|151.101.1.176|:443... соединение установлено.
HTTP-запрос отправлен. Ожидание ответа… 200 OK
Длина: 103117552 (98M) [application/x-xz]
Сохранение в: «/home/alexey/work/buildroot/output/build/.linux-4.19.tar.xz.UHLq8e/output»

/home/alexey/work/b 100%[===================>]  98,34M   341KB/s    in 5m 24s  

2019-06-01 19:21:09 (311 KB/s) - «/home/alexey/work/buildroot/output/build/.linux-4.19.tar.xz.UHLq8e/output» сохранён [103117552/103117552]

ERROR: No hash found for linux-4.19.tar.xz
package/pkg-generic.mk:143: ошибка выполнения рецепта для цели «/home/alexey/work/buildroot/output/build/linux-headers-4.19/.stamp_downloaded»
make: *** [/home/alexey/work/buildroot/output/build/linux-headers-4.19/.stamp_downloaded] Ошибка 1

 

 Все настройки перепроверил все верно.  А что за ошибка ERROR: No hash found for linux-4.19.tar.xz ? Как ее исправить?

Edited by Alex_Golubev

Share this post


Link to post
Share on other sites

Не знаю даже может подтолкнет на какие мысли. 

В опциях меняем тулчейн на кастомный gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabi . C library -> glibc. Версии выставил. Kernel->Kernel version->Latest version (4.19). В local.mk  LINUX_OVERRIDE_SRCDIR = ../linux (где лежит ванильное ядро 4.19). 

https://buildroot.org/downloads/buildroot-2019.02.2.tar.gz

Edited by Alex_Golubev

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now