Manually updating xilinx zynq firmware with contents of swupdate package - Page 1
Forum section: electronics / general

author: glenneaux
author_rank: Contributor
timestamp: December 17, 2024, 10:58:49 am
content: I have a Xilinx device that I'm playing with - as seen in another thread.I current have root access to the linux system onboard, and have console access to uboot environment (@19.2kbps, the port cannot currently do 115.2kbps). I have not looked into sourcing a JTAG to see I can access the device that way.This device is currently running an old/developement firmware package. I am contemplating if I have a "safe" route to (or if it is possible) to update to a "production" firmware package.I have a production firmware package, in the form of an swupdate file. The device does not currently have swupdate onboard so this route cannot currently be used.The swupdate file includes a 909kb BOOT.bin, sw-description, an ext4.gz file system image (appears to only be the linux system, no other partitions?), 2 uboot environments (text file containing the environment variables) and a lua script to deal with emmc partitioning.Within the ext4 file system it contains a fitImage and ".fpga" file - presumably a .bit file.When tinkering with the system with the original software, I have been able to set up an environment with TFTP and NFS access to another device.I have referenced the boot up commands and loaded the kernel & device tree into memory and uploaded via TFTP to my computer. I have had it booting the device as standard but loading the kernel and device tree via TFTP. I haven't yet managed to duplicate the file system and have it use that via NFS.Ideally I would1) Back up the original flash & mmc contents - even the boot loader data if possible? Perhaps I could get back to square one with a JTAG worst case?2) Boot, if possible, the new firmware/system over the network and prove I can run the new firmware verifying device tree's etc.3) Update the device to the new firmware (would need to be careful to do my best to set the uboot environment variable baudrate=19200).4) Establish swupdate on this device? I believe I'm missing this environment - If I could access a production device and dump the emmc partition would that help?Apologies for the boring post, but does anyone know given the scenario if it is possible to reach any of these goals?Happy to fill in more information... I have been having a crash course in uboot and some of the xilinx tools packages and been attempting to learn what each contains and what you can glean from it, including extracting devices trees and performing dtdiff on them.

author: Postal2
author_rank: Frequent Contributor
timestamp: December 17, 2024, 03:33:34 pm
content: You need to try the last step described to get the speed of 115200. When you adjust the variable resistor with the pull-up connected, most likely you will find a point where non-linearity will appear and then the pulse shape will be acceptable. Because it is unlikely that the defect is symmetrical.If a good pulse shape is obtained in one of the extreme positions of the variable resistor, then the pull-up from the central terminal must be switched to more accurately adjust the comparator threshold.

author: glenneaux
author_rank: Contributor
timestamp: December 17, 2024, 09:28:04 pm
content: Quote from: Postal2 on December 17, 2024, 03:33:34 pmHi again Postal2Getting that functionality definitely something to investigate.. repairing that damaged output wasn't part of the original projectgiven that I have access to uboot @19.2kbps and the system via SSH I have been on an information gathering path.Having full functionality of that uart will definitely mean it's less likely to be locked out.

author: Postal2
author_rank: Frequent Contributor
timestamp: December 18, 2024, 03:07:39 am
content: Quote from: glenneaux on December 17, 2024, 10:58:49 amI don't know the design of your board, but first of course you need to save all the images.Quote from: glenneaux on December 17, 2024, 10:58:49 amYou can similarly save images (not partitions!) from a working device, transfer them to your device, and everything will work in the same way. Since you need 19200, you can find and correct the necessary line directly in the image, so your device will immediately use 19200 after starting with a new image.

author: glenneaux
author_rank: Contributor
timestamp: December 18, 2024, 11:14:50 am
content: This device boots from flash over QSPI.Code:SF: Detected n25q256a with page size 256 Bytes, erase size 64 KiB, total 32 MiBThe device includes an EMMC for the root filesystem.Code:device> mmcinfoDevice: sdhci@ff160000Manufacturer ID: 13OEM: 14eName: R1J56Tran Speed: 25000000Rd Block Len: 512MMC version 5.0High Capacity: YesCapacity: 6.9 GiBBus Width: 8-bitErase Group Size: 512 KiBHC WP Group Size: 8 MiBUser Capacity: 6.9 GiB ENH WRRELUser Enhanced Start: 0 BytesUser Enhanced Size: 6.9 GiBBoot Capacity: 16 MiB ENHRPMB Capacity: 128 KiB ENH

author: Postal2
author_rank: Frequent Contributor
timestamp: December 18, 2024, 08:04:04 pm
content: Quote from: glenneaux on December 18, 2024, 11:14:50 amIf you have the ability to connect a USB flash drive, you can easily create images using the "dd" command. To do this via TFTP, you most likely need another program. That is, you need to transfer the images to the drive and then restore from the drive. This is the easiest and fastest way, allowing you not to delve into the details.

author: glenneaux
author_rank: Contributor
timestamp: December 18, 2024, 10:14:48 pm
content: Quote from: Postal2 on December 18, 2024, 08:04:04 pmYep we have USB access on this device so that's definitely possible.Was thinking might be challenging to dd the image while the device is live and may have to do via uboot?This particular build of uboot crashes when enabling the USB system so not currently an option to use usb there.

author: Postal2
author_rank: Frequent Contributor
timestamp: December 18, 2024, 10:39:02 pm
content: As far as I know, dd is used under Linux, booting into u-boot is not required if Linux is running. However, I assume that you will need 2 flash drives. Because on FAT32 you will not load 7 GB. I think that it is more convenient to write to a flash drive in the same manner as reading. That is, linearly and sector by sector.First, practice on your device. After taking an image of your device, save the flash drive images to your computer and save them to files to use these flash drives again.

author: glenneaux
author_rank: Contributor
timestamp: December 21, 2024, 11:42:34 am
content: Quote from: Postal2 on December 18, 2024, 10:39:02 pmi have dumped the qspi flash contentscat /dev/mtd0 > mtd0.bincat /dev/mtd1 > mtd1.bincat /dev/mtd2 > mtd2.bincat /dev/mtd3 > mtd3.bincat /dev/mtd4 > mtd4.bincombined into one bincat mtd0.bin mtd1.bin mtd2.bin mtd3.bin mtd4.bin > mtd.binmtd0.bin is the xilinx first stage boot/ubootmtd1.bin is the first uboot envmtd2.bin is the second uboot envmtd3.bin is the kernelmtd4.bin is the device treeI have tested booting with the kernel and device tree over tftp, using the emmc as system root as per existing config and all works correctly.looking at the firmware update package Boot .bin file, it appears to be the first stage boot loader only. I would love to flash this into the qspi but scared of getting locked out!when running "strings BOOT.bin | grep 115200" shows where the default environment parameter is set (baudrate=115200)-2-production.bin | grep 115200baudrate=115200bootargs=console=ttyPS0,115200n8 consoleblank=0 clk_ignore_unusedserial0:115200n8serial0:115200n8is it possible to hexedit this file, replacing 115200 to 019200 ? Will it fail crc and not boot? Not sure how this will behave...

author: Postal2
author_rank: Frequent Contributor
timestamp: December 21, 2024, 12:04:13 pm
content: Quote from: glenneaux on December 21, 2024, 11:42:34 amFirst, it's not 019200, it's just 19200 with a 00 byte added at the end. It's a C string. In the cases where I edited, no environment variable checks occurred.

author: glenneaux
author_rank: Contributor
timestamp: December 21, 2024, 12:10:59 pm
content: Quote from: Postal2 on December 21, 2024, 12:04:13 pmok i wasn't sure if it would get away with a leading zero and keeping the binary size the same..in theory i could hexedit my combined binary and reflash it back into the device... and it would either work or we'd need to progress to trying to flash the spi via jtagThe existing environment already has a parameter that i believe was being used for this purpose:Code:boot_upd=tftpboot 0x30000000 BOOT.bin && sf probe 0 80000000 0 && sf update 0x30000000 $boot_offset $filesizetftp works, running this would be a few clicks away...then next step could be doing the same to the new boot.bin and seeing how that one goes ! very unsure and nervous about that.I have already attempted to boot the device with the new kernel from the update package - it crashes out with a kernel panic due to some firmware being the wrong versionCode:Kernel panic - not syncing: zynqmp_plat_init Platform Management API version error. Expected: v1.0 - Found: v0.3

author: Postal2
author_rank: Frequent Contributor
timestamp: December 21, 2024, 12:23:16 pm
content: Quote from: glenneaux on December 21, 2024, 12:10:59 pmYou can easily edit strings to be shorter by adding an extra null byte to the end of the string.

author: glenneaux
author_rank: Contributor
timestamp: December 21, 2024, 12:50:56 pm
content: Quote from: Postal2 on December 21, 2024, 12:23:16 pmIt is tempting to flash this in.. with the new bootloader. need to do some more reading to have any confidence.. jtag scares me.

author: Postal2
author_rank: Frequent Contributor
timestamp: December 21, 2024, 01:04:43 pm
content: Quote from: glenneaux on December 21, 2024, 12:50:56 pmYou have a bootloader in an external flash chip. You can always unsolder it and flash it separately. JTAG performs the same functions, unless its pins are damaged.

author: glenneaux
author_rank: Contributor
timestamp: December 22, 2024, 06:06:15 am
content: Quote from: Postal2 on December 21, 2024, 01:04:43 pmAttached some photos of the device - not sure which one is emmc or the flash chip... either way they're epoxied/sealed in and appear to be BGA and not real keen to learn on this...

author: Postal2
author_rank: Frequent Contributor
timestamp: December 22, 2024, 09:49:41 am
content: Quote from: glenneaux on December 22, 2024, 06:06:15 am"7EC77"=EMMC"7JA15"=NOR FLASH BOOT24128C=I2C EEPROM, SERIAL NUMBER, KEYS, SETTINGS FOR UBOOT.I meant nor flash boot, but I didn't expect such a case. Usually such chips have 8 pins and are easy to solder.

author: glenneaux
author_rank: Contributor
timestamp: December 22, 2024, 09:52:21 am
content: Quote from: Postal2 on December 22, 2024, 09:49:41 amfairly sure the uboot data lives in the flash on this device. it is a shame because an 8pin device soic i'd pop off with hot air no problems.I have posted a question in the fpga forum - I have (i believe) identified the jtag pins on the service connector, not sure what hardware (can i get away with a flashed stlink?) or software i would need or how to go about flashing via jtag.There is 2 24128C IC's, not sure what they hold.

author: Postal2
author_rank: Frequent Contributor
timestamp: December 22, 2024, 10:16:02 am
content: Quote from: glenneaux on December 22, 2024, 09:52:21 amI don't see JTAG in your pictures. A regular Xilinx adapter is connected, if the programming environment supports this board, then all memory chips will be visible.One 24C128 should contain some "hardware chain" for uboot, I forgot what it's called. And the second (I don't see it) - some user parameters, serial number, software version in text form are usually there.

author: glenneaux
author_rank: Contributor
timestamp: December 22, 2024, 11:05:21 am
content: Quote from: Postal2 on December 22, 2024, 10:16:02 amFrom overlaying the pin out I traced the JTAG pins to the service connector on the reverse where the uart is alsoI know two copies of the uboot environment live in the spi flash, and also the device tree - is that what you mean by hardware chain ?

author: Postal2
author_rank: Frequent Contributor
timestamp: December 22, 2024, 11:20:14 am
content: Quote from: glenneaux on December 22, 2024, 11:05:21 amExactly. U-boot requires this thing to be in i2c-eeprom. That's why it's so "universal".

author: langwadt
author_rank: Super Contributor
timestamp: December 22, 2024, 11:37:27 am
content: Quote from: Postal2 on December 22, 2024, 11:20:14 amon Zynq it is all in the qspi flash

author: Postal2
author_rank: Frequent Contributor
timestamp: December 22, 2024, 11:41:21 am
content: Quote from: langwadt on December 22, 2024, 11:37:27 amMaybe. Then i2c-eeprom, intended for this, will be empty, i.e. filled with FF. But eeprom is always designed for u-boot.

author: glenneaux
author_rank: Contributor
timestamp: December 22, 2024, 11:41:45 am
content: Quote from: langwadt on December 22, 2024, 11:37:27 amThat makes sense.. see below for flash info on bootup.[ 2.442209] m25p80 spi0.0: n25q256a (32768 Kbytes)[ 2.446939] 5 ofpart partitions found on MTD device spi0.0[ 2.452387] Creating 5 MTD partitions on "spi0.0":[ 2.457165] 0x000000000000-0x000000800000 : "qspi-fsbl-uboot"[ 2.463386] 0x000000800000-0x000000840000 : "qspi-uboot-env1"[ 2.469522] 0x000000840000-0x000000880000 : "qspi-uboot-env2"[ 2.475649] 0x000000880000-0x000001880000 : "qspi-linux"[ 2.481338] 0x000001880000-0x0000018a0000 : "qspi-device-tree"

author: glenneaux
author_rank: Contributor
timestamp: December 22, 2024, 11:43:20 am
content: complete boot from cold @ 115.2kbps (before me damaging the uart)Code:Xilinx Zynq MP First Stage Boot LoaderRelease 2017.3 Dec 12 2017 - 18:26:20PMU Firmware 2017.3Dec 12 2017 18:22:12NOTICE: ATF running on XCZU2EG/silicon v4/RTL5.1 at 0xfffea000, with PMU firmwareNOTICE: BL31: Secure code at 0x0NOTICE: BL31: Non secure code at 0x8000000NOTICE: BL31: v1.3(release):f9b244bNOTICE: BL31: Built : 18:17:09, Dec 12 2017PMUFW:v0.3U-Boot 2017.01 (Dec 12 2017 - 18:17:25 +0100) Xilinx ZynqMP pdm3-large-revBI2C: readyDRAM: 1 GiBEL Level:EL2Chip ID:xczu3egMMC: sdhci@ff160000: 0 (eMMC)SF: Detected n25q256a with page size 256 Bytes, erase size 64 KiB, total 32 MiBIn: serial@ff000000Out: serial@ff000000Err: serial@ff000000Net: ZYNQ GEM: ff0b0000, phyaddr 0, interface rgmii-ideth0: ethernet@ff0b0000Hit any key to stop autoboot: 2 1 0SF: Detected n25q256a with page size 256 Bytes, erase size 64 KiB, total 32 MiBdevice 0 offset 0x1880000, size 0x20000SF: 131072 bytes @ 0x1880000 Read: OKdevice 0 offset 0x880000, size 0x1000000SF: 16777216 bytes @ 0x880000 Read: OK## Flattened Device Tree blob at 04000000Booting using the fdt blob at 0x4000000Loading Device Tree to 000000003de55000, end 000000003de63b04 ... OKStarting kernel ...[ 0.000000] Booting Linux on physical CPU 0x0[ 0.000000] Linux version 4.9.0-xilinx-v2017.2 (derossfe@deeclu54) (gcc version 6.2.0 (GCC) ) #1 SMP Tue Jan 16 12:08:50 CET 2018[ 0.000000] Boot CPU: AArch64 Processor [ 0.000000] efi: Getting EFI parameters from FDT:[ 0.000000] efi: UEFI not found.[ 0.000000] cma: Reserved 192 MiB at 0x0000000031c00000[ 0.000000] psci: probing for conduit method from DT.[ 0.000000] psci: PSCIv1.0 detected in firmware.[ 0.000000] psci: Using standard PSCI v0.2 function IDs[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.[ 0.000000] percpu: Embedded 21 pages/cpu @ffffffc03ff68000 s47384 r8192 d30440 u86016[ 0.000000] Detected VIPT I-cache on CPU0[ 0.000000] CPU features: enabling workaround for ARM erratum 845719[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 258560[ 0.000000] Kernel command line: $bootargs console=ttyPS0,115200n8 consoleblank=0 clk_ignore_unused root=/dev/mmcblk0p1 rw rootwait[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)[ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)[ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)[ 0.000000] Memory: 822076K/1048576K available (8892K kernel code, 578K rwdata, 2892K rodata, 512K init, 387K bss, 29892K reserved, 196608K cma-reserved)[ 0.000000] Virtual kernel memory layout:[ 0.000000] modules : 0xffffff8000000000 - 0xffffff8008000000 ( 128 MB)[ 0.000000] vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000 ( 250 GB)[ 0.000000] .text : 0xffffff8008080000 - 0xffffff8008930000 ( 8896 KB)[ 0.000000] .rodata : 0xffffff8008930000 - 0xffffff8008c10000 ( 2944 KB)[ 0.000000] .init : 0xffffff8008c10000 - 0xffffff8008c90000 ( 512 KB)[ 0.000000] .data : 0xffffff8008c90000 - 0xffffff8008d20a00 ( 579 KB)[ 0.000000] .bss : 0xffffff8008d20a00 - 0xffffff8008d817ac ( 388 KB)[ 0.000000] fixed : 0xffffffbefe7fd000 - 0xffffffbefec00000 ( 4108 KB)[ 0.000000] PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000 ( 16 MB)[ 0.000000] vmemmap : 0xffffffbf00000000 - 0xffffffc000000000 ( 4 GB maximum)[ 0.000000] 0xffffffbf00000000 - 0xffffffbf00e00000 ( 14 MB actual)[ 0.000000] memory : 0xffffffc000000000 - 0xffffffc040000000 ( 1024 MB)[ 0.000000] Hierarchical RCU implementation.[ 0.000000] Build-time adjustment of leaf fanout to 64.[ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4[ 0.000000] NR_IRQS:64 nr_irqs:64 0[ 0.000000] GIC: Adjusting CPU interface base to 0x00000000f902f000[ 0.000000] GIC: Using split EOI/Deactivate mode[ 0.000000] arm_arch_timer: Architected cp15 timer(s) running at 99.99MHz (phys).[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171015c90f, max_idle_ns: 440795203080 ns[ 0.000003] sched_clock: 56 bits at 99MHz, resolution 10ns, wraps every 4398046511101ns[ 0.000261] Console: colour dummy device 80x25[ 0.000278] Calibrating delay loop (skipped), value calculated using timer frequency.. 199.99 BogoMIPS (lpj=399996)[ 0.000285] pid_max: default: 32768 minimum: 301[ 0.000383] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)[ 0.000389] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)[ 0.000886] ASID allocator initialised with 65536 entries[ 0.001372] zynqmp_plat_init Power management API v0.3[ 0.001448] EFI services will not be available.[ 0.001774] Detected VIPT I-cache on CPU1[ 0.001802] CPU1: Booted secondary processor [ 0.002062] Detected VIPT I-cache on CPU2[ 0.002080] CPU2: Booted secondary processor [ 0.002333] Detected VIPT I-cache on CPU3[ 0.002350] CPU3: Booted secondary processor [ 0.002385] Brought up 4 CPUs[ 0.002399] SMP: Total of 4 processors activated.[ 0.002404] CPU features: detected feature: 32-bit EL0 Support[ 0.002410] CPU: All CPU(s) started at EL2[ 0.002423] alternatives: patching kernel code[ 0.002939] devtmpfs: initialized[ 0.009316] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns[ 0.013206] xor: measuring software checksum speed[ 0.052019] 8regs : 2303.000 MB/sec[ 0.092046] 8regs_prefetch: 2053.000 MB/sec[ 0.132073] 32regs : 2727.000 MB/sec[ 0.172102] 32regs_prefetch: 2379.000 MB/sec[ 0.172106] xor: using function: 32regs (2727.000 MB/sec)[ 0.172252] pinctrl core: initialized pinctrl subsystem[ 0.172938] NET: Registered protocol family 16[ 0.188123] cpuidle: using governor menu[ 0.188321] Failed to initialise IOMMU /amba/smmu@fd800000[ 0.188582] vdso: 2 pages (1 code @ ffffff8008937000, 1 data @ ffffff8008c94000)[ 0.188614] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.[ 0.189133] DMA: preallocated 256 KiB pool for atomic allocations[ 0.205581] reset_zynqmp reset-controller: Xilinx zynqmp reset driver probed[ 0.206321] ARM CCI_400_r1 PMU driver probed[ 0.209948] zynqmp-pinctrl ff180000.pinctrl: zynqmp pinctrl initialized[ 0.234477] HugeTLB registered 2 MB page size, pre-allocated 0 pages[ 0.300324] raid6: int64x1 gen() 406 MB/s[ 0.368372] raid6: int64x1 xor() 435 MB/s[ 0.436435] raid6: int64x2 gen() 671 MB/s[ 0.504419] raid6: int64x2 xor() 593 MB/s[ 0.572450] raid6: int64x4 gen() 982 MB/s[ 0.640489] raid6: int64x4 xor() 755 MB/s[ 0.708568] raid6: int64x8 gen() 1099 MB/s[ 0.776609] raid6: int64x8 xor() 729 MB/s[ 0.844652] raid6: neonx1 gen() 728 MB/s[ 0.912668] raid6: neonx1 xor() 732 MB/s[ 0.980751] raid6: neonx2 gen() 1169 MB/s[ 1.048756] raid6: neonx2 xor() 1033 MB/s[ 1.116819] raid6: neonx4 gen() 1509 MB/s[ 1.184853] raid6: neonx4 xor() 1181 MB/s[ 1.252904] raid6: neonx8 gen() 1586 MB/s[ 1.320944] raid6: neonx8 xor() 1221 MB/s[ 1.320948] raid6: using algorithm neonx8 gen() 1586 MB/s[ 1.320951] raid6: .... xor() 1221 MB/s, rmw enabled[ 1.320955] raid6: using intx1 recovery algorithm[ 1.321737] SCSI subsystem initialized[ 1.321929] usbcore: registered new interface driver usbfs[ 1.321965] usbcore: registered new interface driver hub[ 1.322009] usbcore: registered new device driver usb[ 1.322076] media: Linux media interface: v0.10[ 1.322102] Linux video capture interface: v2.00[ 1.322130] pps_core: LinuxPPS API ver. 1 registered[ 1.322134] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>[ 1.322149] PTP clock support registered[ 1.322176] EDAC MC: Ver: 3.0.0[ 1.322445] FPGA manager framework[ 1.322489] Advanced Linux Sound Architecture Driver Initialized.[ 1.322790] Bluetooth: Core ver 2.22[ 1.322810] NET: Registered protocol family 31[ 1.322814] Bluetooth: HCI device and connection manager initialized[ 1.322822] Bluetooth: HCI socket layer initialized[ 1.322828] Bluetooth: L2CAP socket layer initialized[ 1.322844] Bluetooth: SCO socket layer initialized[ 1.323413] clocksource: Switched to clocksource arch_sys_counter[ 1.323482] VFS: Disk quotas dquot_6.6.0[ 1.323525] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)[ 1.328129] NET: Registered protocol family 2[ 1.328503] TCP established hash table entries: 8192 (order: 4, 65536 bytes)[ 1.328561] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)[ 1.328688] TCP: Hash tables configured (established 8192 bind 8192)[ 1.328732] UDP hash table entries: 512 (order: 2, 16384 bytes)[ 1.328755] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)[ 1.328859] NET: Registered protocol family 1[ 1.329055] RPC: Registered named UNIX socket transport module.[ 1.329059] RPC: Registered udp transport module.[ 1.329062] RPC: Registered tcp transport module.[ 1.329066] RPC: Registered tcp NFSv4.1 backchannel transport module.[ 1.329460] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available[ 1.330183] futex hash table entries: 1024 (order: 5, 131072 bytes)[ 1.330251] audit: initializing netlink subsys (disabled)[ 1.330278] audit: type=2000 audit(1.320:1): initialized[ 1.330739] workingset: timestamp_bits=62 max_order=18 bucket_order=0[ 1.331347] NFS: Registering the id_resolver key type[ 1.331364] Key type id_resolver registered[ 1.331367] Key type id_legacy registered[ 1.331377] nfs4filelayout_init: NFSv4 File Layout Driver Registering...[ 1.331395] jffs2: version 2.2. (NAND) (SUMMARY) 2001-2006 Red Hat, Inc.[ 1.335721] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)[ 1.335730] io scheduler noop registered[ 1.335734] io scheduler deadline registered[ 1.335743] io scheduler cfq registered (default)[ 1.337148] xilinx-vdma a00a0000.dma: Xilinx AXI VDMA Engine Driver Probed!![ 1.337332] xilinx-vdma a00b0000.dma: Xilinx AXI VDMA Engine Driver Probed!![ 1.337517] xilinx-vdma a00c0000.dma: Xilinx AXI VDMA Engine Driver Probed!![ 1.337696] xilinx-vdma a00d0000.dma: Xilinx AXI VDMA Engine Driver Probed!![ 1.337988] xilinx-vdma a0100000.dma: Xilinx AXI VDMA Engine Driver Probed!![ 1.338272] xilinx-vdma a0110000.dma: Xilinx AXI VDMA Engine Driver Probed!![ 1.338502] Write failed gate address:1000f02[ 1.338596] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success[ 1.338743] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success[ 1.338885] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success[ 1.339021] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success[ 1.339162] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success[ 1.339300] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success[ 1.339462] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success[ 1.339602] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success[ 1.339820] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success[ 1.339959] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success[ 1.340101] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success[ 1.340240] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success[ 1.340383] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success[ 1.340520] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success[ 1.340668] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success[ 1.340810] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success[ 1.340937] zynqmp_pm firmware: Power management API v0.3[ 1.368791] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled[ 1.369702] a0020000.serial: ttyUL2 at MMIO 0xa0020000 (irq = 44, base_baud = 0) is a uartlite[ 1.370106] ff000000.serial: ttyPS0 at MMIO 0xff000000 (irq = 40, base_baud = 6249999) is a xuartps[ 1.449882] PLL: shutdown[ 2.371401] console  enabled[ 2.375272] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 41, base_baud = 6249999) is a xuartps[ 2.384478]  Initialized[ 2.388533]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.395065]  No driver support for vblank timestamp query.[ 2.401015] ifm_dc a00e0000.ifm_displaycontroller: Failed to create outputs[ 2.408051] Unable to detect cache hierarchy from DT for CPU 0[ 2.418449] brd: module loaded[ 2.424328] loop: module loaded[ 2.427895] ifm-fpga-version a0000000.ver: IFM FPGA version: 20170919[ 2.434653] mtdoops: mtd device (mtddev=name/number) must be supplied[ 2.442209] m25p80 spi0.0: n25q256a (32768 Kbytes)[ 2.446939] 5 ofpart partitions found on MTD device spi0.0[ 2.452387] Creating 5 MTD partitions on "spi0.0":[ 2.457165] 0x000000000000-0x000000800000 : "qspi-fsbl-uboot"[ 2.463386] 0x000000800000-0x000000840000 : "qspi-uboot-env1"[ 2.469522] 0x000000840000-0x000000880000 : "qspi-uboot-env2"[ 2.475649] 0x000000880000-0x000001880000 : "qspi-linux"[ 2.481338] 0x000001880000-0x0000018a0000 : "qspi-device-tree"[ 2.488400] libphy: Fixed MDIO Bus: probed[ 2.493443] tun: Universal TUN/TAP device driver, 1.6[ 2.498413] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>[ 2.504676] CAN device driver interface[ 2.511496] usbcore: registered new interface driver asix[ 2.516859] usbcore: registered new interface driver ax88179_178a[ 2.522917] usbcore: registered new interface driver cdc_ether[ 2.528726] usbcore: registered new interface driver net1080[ 2.534367] usbcore: registered new interface driver cdc_subset[ 2.540270] usbcore: registered new interface driver zaurus[ 2.545836] usbcore: registered new interface driver cdc_ncm[ 2.552125] usbcore: registered new interface driver uas[ 2.557395] usbcore: registered new interface driver usb-storage[ 2.563414] usbcore: registered new interface driver usbserial[ 2.569183] usbcore: registered new interface driver usbserial_generic[ 2.575691] usbserial: USB Serial support registered for generic[ 2.581681] usbcore: registered new interface driver ftdi_sio[ 2.587413] usbserial: USB Serial support registered for FTDI USB Serial Device[ 2.594967] mousedev: PS/2 mouse device common for all mice[ 2.600759] i2c /dev entries driver[ 2.604396] cdns-i2c ff020000.i2c: 400 kHz mmio ff020000 irq 35[ 2.610575] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 36[ 2.616925] at24 1-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write[ 2.623755] at24 1-0051: 16384 byte 24c128 EEPROM, writable, 1 bytes/write[ 2.630995] rtc-abx80x 1-0069: model 1805, revision 2.3, lot 2c, wafer 8, uid 42d4[ 2.639518] rtc-abx80x 1-0069: rtc core: registered abx8xx as rtc0[ 2.646183] tw9984 2-0028: chip found @ 0x50 (xiic-i2c)[ 2.652508] ifm_bt656_demux a0090000.bt656_demux: IFM BT656 demuxer v2017-09-19.13 loaded.[ 2.661057] Bluetooth: HCI UART driver ver 2.3[ 2.665417] Bluetooth: HCI UART protocol H4 registered[ 2.670533] Bluetooth: HCI UART protocol BCSP registered[ 2.675828] Bluetooth: HCI UART protocol LL registered[ 2.680948] Bluetooth: HCI UART protocol ATH3K registered[ 2.686330] Bluetooth: HCI UART protocol Three-wire (H5) registered[ 2.692618] Bluetooth: HCI UART protocol Intel registered[ 2.698000] Bluetooth: HCI UART protocol Broadcom registered[ 2.703605] Bluetooth: HCI UART protocol QCA registered[ 2.708850] usbcore: registered new interface driver bcm203x[ 2.714487] usbcore: registered new interface driver bpa10x[ 2.720042] usbcore: registered new interface driver bfusb[ 2.725508] usbcore: registered new interface driver btusb[ 2.730947] Bluetooth: Generic Bluetooth SDIO driver ver 0.1[ 2.736638] usbcore: registered new interface driver ath3k[ 2.742205] EDAC MC: ECC not enabled[ 2.745832] EDAC DEVICE0: Giving out device to module edac controller cache_err: DEV edac (POLLED)[ 2.754869] EDAC DEVICE1: Giving out device to module zynqmp-ocm-edac controller zynqmp_ocm: DEV ff960000.memory-controller (INTERRUPT)[ 2.767855] sdhci: Secure Digital Host Controller Interface driver[ 2.773951] sdhci: Copyright(c) Pierre Ossman[ 2.778287] sdhci-pltfm: SDHCI platform and OF driver helper[ 2.831486] mmc0: SDHCI controller on ff160000.sdhci [ff160000.sdhci] using ADMA 64-bit[ 2.841858] ledtrig-cpu: registered to indicate activity on CPUs[ 2.847853] hidraw: raw HID events driver (C) Jiri Kosina[ 2.853285] usbcore: registered new interface driver usbhid[ 2.858772] usbhid: USB HID core driver[ 2.865650] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered[ 2.879195] ifm-i2s a00f0000.ifm_i2s_master: IFM I2S v2017-08-25.14 loaded.[ 2.886442] pktgen: Packet Generator for packet performance testing. Version: 2.75[ 2.894103] Netfilter messages via NETLINK v0.30.[ 2.898831] ip_tables: (C) 2000-2006 Netfilter Core Team[ 2.904101] Initializing XFRM netlink socket[ 2.908356] NET: Registered protocol family 10[ 2.913138] ip6_tables: (C) 2000-2006 Netfilter Core Team[ 2.918489] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver[ 2.924769] NET: Registered protocol family 17[ 2.929136] NET: Registered protocol family 15[ 2.933561] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.[ 2.946483] Ebtables v2.0 registered[ 2.950066] can: controller area network core (rev 20120528 abi 9)[ 2.956230] NET: Registered protocol family 29[ 2.960655] can: raw protocol (rev 20120528)[ 2.964884] can: broadcast manager protocol (rev 20161123 t)[ 2.970528] can: netlink gateway (rev 20130117) max_hops=1[ 2.976054] Bluetooth: RFCOMM TTY layer initialized[ 2.980861] Bluetooth: RFCOMM socket layer initialized[ 2.985984] Bluetooth: RFCOMM ver 1.11[ 2.989712] Bluetooth: BNEP (Ethernet Emulation) ver 1.3[ 2.995004] Bluetooth: BNEP filters: protocol multicast[ 3.000223] Bluetooth: BNEP socket layer initialized[ 3.005166] Bluetooth: HIDP (Human Interface Emulation) ver 1.2[ 3.011065] Bluetooth: HIDP socket layer initialized[ 3.016197] 9pnet: Installing 9P2000 support[ 3.020403] Key type dns_resolver registered[ 3.025067] registered taskstats version 1[ 3.029490] Btrfs loaded, crc32c=crc32c-generic[ 3.049708] ifm-pdm3ng-panel a00e0400.panel: Valid panel found: sn=0000007f vid:pid=0001:010c[ 3.058363]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 3.064891]  No driver support for vblank timestamp query.[ 3.080018] Console: switching to colour frame buffer device 160x30[ 3.093458] ifm_dc a00e0000.ifm_displaycontroller: fb0: frame buffer device[ 3.108897] mmc0: new HS200 MMC card at address 0001[ 3.114034] mmcblk0: mmc0:0001 R1J56L 6.88 GiB[ 3.118512] ifm_dc a00e0000.ifm_displaycontroller: IFM DisplayController v2017-09-21.24 loaded.[ 3.127333] mmcblk0boot0: mmc0:0001 R1J56L partition 1 16.0 MiB[ 3.133758] mmcblk0boot1: mmc0:0001 R1J56L partition 2 16.0 MiB[ 3.139700] mmcblk0rpmb: mmc0:0001 R1J56L partition 3 128 KiB[ 3.145873] mmcblk0: p1[ 3.151975] libphy: MACB_mii_bus: probed[ 3.227643] macb ff0b0000.ethernet eth0: Cadence GEM rev 0x50070106 at 0xff0b0000 irq 32 (00:02:01:06:63:3d)[ 3.237385] SMSC LAN8710/LAN8720 ff0b0000.etherne:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=ff0b0000.etherne:00, irq=-1)[ 3.267879] libphy: MACB_mii_bus: probed[ 3.343638] macb ff0c0000.ethernet eth1: Cadence GEM rev 0x50070106 at 0xff0c0000 irq 33 (00:02:01:06:63:3e)[ 3.353384] SMSC LAN8710/LAN8720 ff0c0000.etherne:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=ff0c0000.etherne:00, irq=-1)[ 3.367187] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller[ 3.372604] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1[ 3.380585] xhci-hcd xhci-hcd.0.auto: hcc params 0x0238f625 hci version 0x100 quirks 0x00010810[ 3.389223] xhci-hcd xhci-hcd.0.auto: irq 235, io mem 0xfe200000[ 3.395276] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002[ 3.401985] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 3.409186] usb usb1: Product: xHCI Host Controller[ 3.414047] usb usb1: Manufacturer: Linux 4.9.0-xilinx-v2017.2 xhci-hcd[ 3.420642] usb usb1: SerialNumber: xhci-hcd.0.auto[ 3.425815] hub 1-0:1.0: USB hub found[ 3.429497] hub 1-0:1.0: 1 port detected[ 3.433536] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller[ 3.438946] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2[ 3.446658] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003[ 3.453362] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 3.460563] usb usb2: Product: xHCI Host Controller[ 3.465423] usb usb2: Manufacturer: Linux 4.9.0-xilinx-v2017.2 xhci-hcd[ 3.472020] usb usb2: SerialNumber: xhci-hcd.0.auto[ 3.477132] hub 2-0:1.0: USB hub found[ 3.480812] hub 2-0:1.0: 1 port detected[ 3.485562] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller[ 3.490976] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3[ 3.498873] xhci-hcd xhci-hcd.1.auto: hcc params 0x0238f625 hci version 0x100 quirks 0x00010810[ 3.507509] xhci-hcd xhci-hcd.1.auto: irq 237, io mem 0xfe300000[ 3.513540] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002[ 3.520251] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 3.527454] usb usb3: Product: xHCI Host Controller[ 3.532313] usb usb3: Manufacturer: Linux 4.9.0-xilinx-v2017.2 xhci-hcd[ 3.538909] usb usb3: SerialNumber: xhci-hcd.1.auto[ 3.544025] hub 3-0:1.0: USB hub found[ 3.547707] hub 3-0:1.0: 1 port detected[ 3.551739] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller[ 3.557143] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4[ 3.564852] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003[ 3.571558] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 3.578760] usb usb4: Product: xHCI Host Controller[ 3.583620] usb usb4: Manufacturer: Linux 4.9.0-xilinx-v2017.2 xhci-hcd[ 3.590217] usb usb4: SerialNumber: xhci-hcd.1.auto[ 3.595327] hub 4-0:1.0: USB hub found[ 3.599009] hub 4-0:1.0: 1 port detected[ 3.603116] tw9984 2-0028: chip found @ 0x50 (xiic-i2c)[ 3.692650] random: fast init done[ 3.703249] input: hid-over-i2c 0EEF:C000 as /devices/platform/amba/ff030000.i2c/i2c-1/1-002a/0018:0EEF:C000.0001/input/input0[ 3.714818] input: hid-over-i2c 0EEF:C000 Pen as /devices/platform/amba/ff030000.i2c/i2c-1/1-002a/0018:0EEF:C000.0001/input/input1[ 3.726682] hid-multitouch 0018:0EEF:C000.0001: input,hidraw0: I2C HID v1.00 Pointer [hid-over-i2c 0EEF:C000] on 1-002a[ 3.738690] ifm-i2s a00f0000.ifm_i2s_master: Failed to get DMA channel capabilities, falling back to period counting: -6[ 3.749761] ifm-i2s a00f0000.ifm_i2s_master: Failed to get DMA channel capabilities, falling back to period counting: -6[ 3.760550] asoc-simple-card sound: wm8960-hifi <-> a00f0000.ifm_i2s_master mapping ok[ 3.877091] rtc-abx80x 1-0069: setting system clock to 2024-05-16 21:33:00 UTC (1715895180)[ 3.885493] clk: Not disabling unused clocks[ 3.889716] ALSA device list:[ 3.892629] #0: a00f0000.ifm_i2s_master-wm8960-hifi[ 3.898483] EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature incompatibilities[ 3.923568] EXT4-fs (mmcblk0p1): recovery complete[ 3.929241] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)[ 3.937262] VFS: Mounted root (ext4 filesystem) on device 179:1.[ 3.944525] devtmpfs: mounted[ 3.947536] Freeing unused kernel memory: 512K (ffffffc000c10000 - ffffffc000c90000)INIT: version 2.88 bootingStarting udevstat: can't stat 'lib/udev/rules.d/*': No such file or directory[ 4.189573] udevd: starting version 3.2[ 4.211947] udevd: starting eudev-3.2[ 4.249643] mali: loading out-of-tree module taints kernel.[ 4.260790] PLL: enable[ 4.288900] EXT4-fs (mmcblk0p1): re-mounted. Opts: data=orderedALSA: Restoring mixer settings...INIT: Entering runlevel: 5Configuring network interfaces... [ 4.667037] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not readydone.resize2fs 1.43 (17-May-2016)The filesystem is already 1048576 (1k) blocks long. Nothing to do!Starting XserverStarting system message bus: dbus.Starting dev-serviceStarting Dropbear SSH server: dropbear.Starting keyboard-serviceStarting can-serviceStarting net-serviceStarting syscall-serviceStarting syscfg-serviceStarting io-serviceStarting camera-serviceStarting syslogd/klogd: doneStarting Lighttpd Web Server: lighttpd.pdm3-linux V3.2.2.0 pdm3 /dev/ttyPS0pdm3 login: [ 5.549400] input: pdm3 Keyboard as /devices/virtual/input/input3[ 6.691726] macb ff0b0000.ethernet eth0: link up (100/Full)[ 6.697257] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes readyLooking at the update files uboot environment, this is the mtdparts variable it passes to the kernel:Code:mtdparts=spi0.0:2048k(production-boot-bin)${mtd_readonly},1536k(recovery-boot-bin)ro,256k(env1),256k(env2),-(recovery)roagain looking at the boot parameters, the device always loads the kernel/device tree fitimage from the MMC, this other unit I have stores kernel/device tree seperately in qspi.Everything is looking like I could in theory load the bootloader, and load the fitimage over tftp and access the file system via NFS moutned on another machine. The question is if i modify the boot.bin to have uboot in 19200bps will it corrupt it and not work.. that is the question i guess

author: glenneaux
author_rank: Contributor
timestamp: December 22, 2024, 11:52:52 am
content: This is a boot up sequence from a device closer to a production unitThe production units incorporate swupdate, and i can see from this log that their flash memory arrangement is differentCode:[ 2.340055] m25p80 spi0.0: found n25q256a, expected m25p80[ 2.345998] m25p80 spi0.0: n25q256a (32768 Kbytes)[ 2.350718] 4 cmdlinepart partitions found on MTD device spi0.0[ 2.356608] Creating 4 MTD partitions on "spi0.0":[ 2.361385] 0x000000000000-0x000000380000 : "u-boot"[ 2.366874] 0x000000380000-0x0000003c0000 : "env1"[ 2.372059] 0x0000003c0000-0x000000400000 : "env2"[ 2.377263] 0x000000400000-0x000002000000 : "recovery"Code:Xilinx Zynq MP First Stage Boot LoaderRelease 2018.2 Jul 26 2018 - 17:46:19PMU Firmware 2018.2 Jul 26 2018 17:51:15PMU_ROM Version: xpbr-v8.1.0-0NOTICE: ATF running on XCZU2EG/silicon v4/RTL5.1 at 0xfffea000NOTICE: BL31: Secure code at 0x0NOTICE: BL31: Non secure code at 0x8000000NOTICE: BL31: v1.4(release):xilinx-v2018.2NOTICE: BL31: Built : 17:43:05, Jul 26 2018U-Boot 2018.07 (Jul 26 2018 - 16:39:55 +0000) IFM PDM3I2C: readyDRAM: 1 GiBEL Level: EL2Chip ID: zu2egMMC: sdhci@ff160000: 0Loading Environment from SPI Flash... SF: Detected n25q256a with page size 256 Bytes, erase size 64 KiB, total 32 MiBOKFPGA: Using normal mode image.sha1+ design filename = "b_v0_11_wrapper;UserID=0XFFFFFFFF;Version=2017.2"part number = "xczu2eg-sfva625-1-i"date = "2017/09/22"time = "14:11:52"bytes in bitstream = 5568668zynqmp_align_dma_buffer: Align buffer at 0000000010000077 to 000000000fffff80(swap 1)In: serial@ff000000Out: serial@ff000000Err: serial@ff000000Net: ZYNQ GEM: ff0b0000, phyaddr 0, interface rgmii-ideth0: ethernet@ff0b0000## Copying 'logo@1' subimage from FIT image at 3dd72bc0 ...sha1+ Uncompressing part 0 ... OKHit any key to stop autoboot: 0switch to partitions #0, OKmmc0(part 0) is current device13995756 bytes read in 2205 ms (6.1 MiB/s)## Loading kernel from FIT Image at 01000000 ...Using 'conf@xilinx_zynqmp-pdm3-medium-revB.dtb' configurationTrying 'kernel@1' kernel subimageDescription: Linux kernelType: Kernel ImageCompression: uncompressedData Start: 0x01000100Data Size: 13920768 Bytes = 13.3 MiBArchitecture: AArch64OS: LinuxLoad Address: 0x00080000Entry Point: 0x00080000Hash algo: sha1Hash value: 1cf787a578e8890cc48d194da34599018e308d02Verifying Hash Integrity ... sha1+ OK## Loading fdt from FIT Image at 01000000 ...Using 'conf@xilinx_zynqmp-pdm3-medium-revB.dtb' configurationTrying 'fdt@xilinx_zynqmp-pdm3-medium-revB.dtb' fdt subimageDescription: Flattened Device Tree blobType: Flat Device TreeCompression: uncompressedData Start: 0x01d4fbacData Size: 36069 Bytes = 35.2 KiBArchitecture: AArch64Hash algo: sha1Hash value: 33614d073755d5e82425128b5ec4377a4e84a33dVerifying Hash Integrity ... sha1+ OKBooting using the fdt blob at 0x1d4fbacLoading Kernel Image ... OKLoading Device Tree to 000000003dc9c000, end 000000003dca7ce4 ... OKWARNING: reserved memory node not in DT!Starting kernel ...[ 0.000000] Booting Linux on physical CPU 0x0[ 0.000000] Linux version 4.14.79-yocto-standard (oe-user@oe-host) (gcc version 7.3.0 (GCC)) #4 SMP Tue Jan 22 15:32:03 UTC 2019[ 0.000000] Boot CPU: AArch64 Processor [ 0.000000] Machine model: IFM PDM3 Medium rev. B[ 0.000000] efi: Getting EFI parameters from FDT:[ 0.000000] efi: UEFI not found.[ 0.000000] cma: Reserved 192 MiB at 0x0000000031c00000[ 0.000000] psci: probing for conduit method from DT.[ 0.000000] psci: PSCIv1.1 detected in firmware.[ 0.000000] psci: Using standard PSCI v0.2 function IDs[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.[ 0.000000] psci: SMC Calling Convention v1.1[ 0.000000] percpu: Embedded 21 pages/cpu @ffffffc03ff93000 s45080 r8192 d32744 u86016[ 0.000000] Detected VIPT I-cache on CPU0[ 0.000000] CPU features: enabling workaround for ARM erratum 845719[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 254464[ 0.000000] Kernel command line: console=ttyPS0,115200n8 consoleblank=0 clk_ignore_unused mtdparts=spi0.0:3584k(u-boot),256k(env1),256k(env2),-(recovery) root=/dev/mmcblk0p1 rw rootwait[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)[ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)[ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)[ 0.000000] Memory: 803480K/1032192K available (9596K kernel code, 602K rwdata, 2844K rodata, 512K init, 2113K bss, 32104K reserved, 196608K cma-reserved)[ 0.000000] Virtual kernel memory layout:[ 0.000000] modules : 0xffffff8000000000 - 0xffffff8008000000 ( 128 MB)[ 0.000000] vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000 ( 250 GB)[ 0.000000] .text : 0xffffff8008080000 - 0xffffff80089e0000 ( 9600 KB)[ 0.000000] .rodata : 0xffffff80089e0000 - 0xffffff8008cb0000 ( 2880 KB)[ 0.000000] .init : 0xffffff8008cb0000 - 0xffffff8008d30000 ( 512 KB)[ 0.000000] .data : 0xffffff8008d30000 - 0xffffff8008dc6a00 ( 603 KB)[ 0.000000] .bss : 0xffffff8008dc6a00 - 0xffffff8008fd6f88 ( 2114 KB)[ 0.000000] fixed : 0xffffffbefe7fb000 - 0xffffffbefec00000 ( 4116 KB)[ 0.000000] PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000 ( 16 MB)[ 0.000000] vmemmap : 0xffffffbf00000000 - 0xffffffc000000000 ( 4 GB maximum)[ 0.000000] 0xffffffbf00000000 - 0xffffffbf00e00000 ( 14 MB actual)[ 0.000000] memory : 0xffffffc000000000 - 0xffffffc040000000 ( 1024 MB)[ 0.000000] Hierarchical RCU implementation.[ 0.000000] RCU event tracing is enabled.[ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0[ 0.000000] GIC: Adjusting CPU interface base to 0x00000000f902f000[ 0.000000] GIC: Using split EOI/Deactivate mode[ 0.000000] arch_timer: cp15 timer(s) running at 99.99MHz (phys).[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171015c90f, max_idle_ns: 440795203080 ns[ 0.000003] sched_clock: 56 bits at 99MHz, resolution 10ns, wraps every 4398046511101ns[ 0.000312] Console: colour dummy device 80x25[ 0.000332] Calibrating delay loop (skipped), value calculated using timer frequency.. 199.99 BogoMIPS (lpj=399996)[ 0.000340] pid_max: default: 32768 minimum: 301[ 0.000433] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)[ 0.000441] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)[ 0.001078] ASID allocator initialised with 32768 entries[ 0.001128] Hierarchical SRCU implementation.[ 0.001307] EFI services will not be available.[ 0.001331] zynqmp_plat_init Platform Management API v1.0[ 0.001336] zynqmp_plat_init Trustzone version v1.0[ 0.001411] smp: Bringing up secondary CPUs ...[ 0.001690] Detected VIPT I-cache on CPU1[ 0.001722] CPU1: Booted secondary processor [ 0.001780] smp: Brought up 1 node, 2 CPUs[ 0.001788] SMP: Total of 2 processors activated.[ 0.001794] CPU features: detected feature: 32-bit EL0 Support[ 0.001799] CPU features: detected feature: Kernel page table isolation (KPTI)[ 0.003536] CPU: All CPU(s) started at EL2[ 0.003546] alternatives: patching kernel code[ 0.004186] devtmpfs: initialized[ 0.008647] random: get_random_u32 called from bucket_table_alloc+0x108/0x260 with crng_init=0[ 0.008962] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns[ 0.008973] futex hash table entries: 512 (order: 4, 65536 bytes)[ 0.013295] xor: measuring software checksum speed[ 0.052034] 8regs : 2303.000 MB/sec[ 0.092061] 8regs_prefetch: 2053.000 MB/sec[ 0.132090] 32regs : 2830.000 MB/sec[ 0.172119] 32regs_prefetch: 2379.000 MB/sec[ 0.172123] xor: using function: 32regs (2830.000 MB/sec)[ 0.172134] pinctrl core: initialized pinctrl subsystem[ 0.173056] NET: Registered protocol family 16[ 0.173984] cpuidle: using governor menu[ 0.174286] vdso: 2 pages (1 code @ ffffff80089e6000, 1 data @ ffffff8008d34000)[ 0.174297] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.[ 0.175027] DMA: preallocated 256 KiB pool for atomic allocations[ 0.212470] reset_zynqmp reset-controller: Xilinx zynqmp reset driver probed[ 0.234013] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages[ 0.300389] raid6: int64x1 gen() 398 MB/s[ 0.368462] raid6: int64x1 xor() 444 MB/s[ 0.436549] raid6: int64x2 gen() 686 MB/s[ 0.504538] raid6: int64x2 xor() 602 MB/s[ 0.572643] raid6: int64x4 gen() 1040 MB/s[ 0.640709] raid6: int64x4 xor() 742 MB/s[ 0.708749] raid6: int64x8 gen() 979 MB/s[ 0.776806] raid6: int64x8 xor() 746 MB/s[ 0.844882] raid6: neonx1 gen() 724 MB/s[ 0.912951] raid6: neonx1 xor() 850 MB/s[ 0.981038] raid6: neonx2 gen() 1162 MB/s[ 1.049074] raid6: neonx2 xor() 1204 MB/s[ 1.117152] raid6: neonx4 gen() 1503 MB/s[ 1.185193] raid6: neonx4 xor() 1438 MB/s[ 1.253276] raid6: neonx8 gen() 1647 MB/s[ 1.321326] raid6: neonx8 xor() 1527 MB/s[ 1.321330] raid6: using algorithm neonx8 gen() 1647 MB/s[ 1.321334] raid6: .... xor() 1527 MB/s, rmw enabled[ 1.321338] raid6: using neon recovery algorithm[ 1.323139] SCSI subsystem initialized[ 1.323355] usbcore: registered new interface driver usbfs[ 1.323388] usbcore: registered new interface driver hub[ 1.323439] usbcore: registered new device driver usb[ 1.323498] media: Linux media interface: v0.10[ 1.323522] Linux video capture interface: v2.00[ 1.323560] pps_core: LinuxPPS API ver. 1 registered[ 1.323564] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>[ 1.323578] PTP clock support registered[ 1.323840] zynqmp-ipi ff9905c0.mailbox: Probed ZynqMP IPI Mailbox driver.[ 1.324090] ff000000.serial: ttyPS0 at MMIO 0xff000000 (irq = 26, base_baud = 6249999) is a xuartps[ 1.328621] FPGA manager framework[ 1.328725] fpga-region fpga-full: FPGA Region probed[ 1.328817] Advanced Linux Sound Architecture Driver Initialized.[ 1.329084] Bluetooth: Core ver 2.22[ 1.329109] NET: Registered protocol family 31[ 1.329111] Bluetooth: HCI device and connection manager initialized[ 1.329118] Bluetooth: HCI socket layer initialized[ 1.329122] Bluetooth: L2CAP socket layer initialized[ 1.329135] Bluetooth: SCO socket layer initialized[ 1.345694] clocksource: Switched to clocksource arch_sys_counter[ 1.345771] VFS: Disk quotas dquot_6.6.0[ 1.345808] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)[ 1.388486] NET: Registered protocol family 2[ 1.388803] TCP established hash table entries: 8192 (order: 4, 65536 bytes)[ 1.388858] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)[ 1.388980] TCP: Hash tables configured (established 8192 bind 8192)[ 1.389043] UDP hash table entries: 512 (order: 2, 16384 bytes)[ 1.389064] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)[ 1.389191] NET: Registered protocol family 1[ 1.390516] RPC: Registered named UNIX socket transport module.[ 1.390518] RPC: Registered udp transport module.[ 1.390520] RPC: Registered tcp transport module.[ 1.390521] RPC: Registered tcp NFSv4.1 backchannel transport module.[ 1.396031] hw perfevents: no interrupt-affinity property for /pmu, guessing.[ 1.399885] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available[ 1.400500] audit: initializing netlink subsys (disabled)[ 1.401245] audit: type=2000 audit(1.396:1): state=initialized audit_enabled=0 res=1[ 1.401305] workingset: timestamp_bits=62 max_order=18 bucket_order=0[ 1.406814] NFS: Registering the id_resolver key type[ 1.406828] Key type id_resolver registered[ 1.406830] Key type id_legacy registered[ 1.406837] nfs4filelayout_init: NFSv4 File Layout Driver Registering...[ 1.406851] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.[ 1.468182] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)[ 1.468187] io scheduler noop registered[ 1.468189] io scheduler deadline registered[ 1.468206] io scheduler cfq registered (default)[ 1.468208] io scheduler mq-deadline registered[ 1.468210] io scheduler kyber registered[ 1.476163] xilinx-vdma a00a0000.axivdma: Xilinx AXI VDMA Engine Driver Probed!![ 1.476629] xilinx-vdma a00b0000.axivdma: Xilinx AXI VDMA Engine Driver Probed!![ 1.476887] xilinx-vdma a00c0000.axivdma: Xilinx AXI VDMA Engine Driver Probed!![ 1.477165] xilinx-vdma a00d0000.axivdma: Xilinx AXI VDMA Engine Driver Probed!![ 1.477443] xilinx-vdma a0100000.axidma: Xilinx AXI DMA Engine Driver Probed!![ 1.477735] xilinx-vdma a0110000.axidma: Xilinx AXI DMA Engine Driver Probed!![ 1.525052] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled[ 2.240327] console  enabled[ 2.244462] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 27, base_baud = 6249999) is a xuartps[ 2.254638] a0020000.uart: ttyUL0 at MMIO 0xa0020000 (irq = 31, base_baud = 0) is a uartlite[ 2.264861]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.271391]  No driver support for vblank timestamp query.[ 2.277339] ifm_dc a00e0000.displaycontroller: Failed to create outputs[ 2.284048] cacheinfo: Unable to detect cache hierarchy for CPU 0[ 2.295585] brd: module loaded[ 2.302542] loop: module loaded[ 2.305979] ifm-fpga-version a0000000.ver: IFM FPGA version: 20170919[ 2.312959]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.319495]  No driver support for vblank timestamp query.[ 2.326121] mtdoops: mtd device (mtddev=name/number) must be supplied[ 2.333230] ifm_dc a00e0000.displaycontroller: Failed to create outputs[ 2.340055] m25p80 spi0.0: found n25q256a, expected m25p80[ 2.345998] m25p80 spi0.0: n25q256a (32768 Kbytes)[ 2.350718] 4 cmdlinepart partitions found on MTD device spi0.0[ 2.356608] Creating 4 MTD partitions on "spi0.0":[ 2.361385] 0x000000000000-0x000000380000 : "u-boot"[ 2.366874] 0x000000380000-0x0000003c0000 : "env1"[ 2.372059] 0x0000003c0000-0x000000400000 : "env2"[ 2.377263] 0x000000400000-0x000002000000 : "recovery"[ 2.383255]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.389786]  No driver support for vblank timestamp query.[ 2.394450] libphy: Fixed MDIO Bus: probed[ 2.395400] tun: Universal TUN/TAP device driver, 1.6[ 2.404011] CAN device driver interface[ 2.406141] macb ff0b0000.ethernet: Not enabling partial store and forward[ 2.415557] ifm_dc a00e0000.displaycontroller: Failed to create outputs[ 2.422797]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.426125] libphy: MACB_mii_bus: probed[ 2.433235]  No driver support for vblank timestamp query.[ 2.439181] ifm_dc a00e0000.displaycontroller: Failed to create outputs[ 2.446104]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.452636]  No driver support for vblank timestamp query.[ 2.458575] ifm_dc a00e0000.displaycontroller: Failed to create outputs[ 2.493816] macb ff0b0000.ethernet eth0: Cadence GEM rev 0x50070106 at 0xff0b0000 irq 15 (00:02:01:05:34:71)[ 2.503561] SMSC LAN8710/LAN8720 ff0b0000.ethernet-ffffffff:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=ff0b0000.ethernet-ffffffff:00, irq=POLL)[ 2.518698]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.525229]  No driver support for vblank timestamp query.[ 2.531711] usbcore: registered new interface driver asix[ 2.537102] usbcore: registered new interface driver ax88179_178a[ 2.543156] ifm_dc a00e0000.displaycontroller: Failed to create outputs[ 2.549763] usbcore: registered new interface driver cdc_ether[ 2.555621] usbcore: registered new interface driver cdc_eem[ 2.561252] usbcore: registered new interface driver net1080[ 2.566895] usbcore: registered new interface driver rndis_host[ 2.572794] usbcore: registered new interface driver cdc_subset[ 2.578698] usbcore: registered new interface driver zaurus[ 2.584278] usbcore: registered new interface driver cdc_ncm[ 2.591368]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.594022] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller[ 2.594035] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1[ 2.611003]  No driver support for vblank timestamp query.[ 2.616950] ifm_dc a00e0000.displaycontroller: Failed to create outputs[ 2.623866]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.630397]  No driver support for vblank timestamp query.[ 2.636337] ifm_dc a00e0000.displaycontroller: Failed to create outputs[ 2.643223] xhci-hcd xhci-hcd.0.auto: hcc params 0x0238f625 hci version 0x100 quirks 0x02010010[ 2.651899] xhci-hcd xhci-hcd.0.auto: irq 40, io mem 0xfe200000[ 2.657827] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002[ 2.664530] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 2.671731] usb usb1: Product: xHCI Host Controller[ 2.676592] usb usb1: Manufacturer: Linux 4.14.79-yocto-standard xhci-hcd[ 2.683362] usb usb1: SerialNumber: xhci-hcd.0.auto[ 2.688573] hub 1-0:1.0: USB hub found[ 2.692261] hub 1-0:1.0: 1 port detected[ 2.696606]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 2.703138]  No driver support for vblank timestamp query.[ 2.703258] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller[ 2.703266] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2[ 2.703274] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed[ 2.703309] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.[ 2.703361] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003[ 2.703365] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 2.703369] usb usb2: Product: xHCI Host Controller[ 2.703372] usb usb2: Manufacturer: Linux 4.14.79-yocto-standard xhci-hcd[ 2.703375] usb usb2: SerialNumber: xhci-hcd.0.auto[ 2.703602] hub 2-0:1.0: USB hub found[ 2.703616] hub 2-0:1.0: 1 port detected[ 2.703843] usbcore: registered new interface driver uas[ 2.703897] usbcore: registered new interface driver usb-storage[ 2.703950] usbcore: registered new interface driver usbserial[ 2.703971] usbcore: registered new interface driver usbserial_generic[ 2.703989] usbserial: USB Serial support registered for generic[ 2.704010] usbcore: registered new interface driver ftdi_sio[ 2.704028] usbserial: USB Serial support registered for FTDI USB Serial Device[ 2.704501] i2c /dev entries driver[ 2.704902] cdns-i2c ff020000.i2c: 400 kHz mmio ff020000 irq 17[ 2.722162] atmel_mxt_ts 1-004a: __mxt_read_reg: i2c transfer failed (-6)[ 2.728751] atmel_mxt_ts 1-004a: mxt_bootloader_read: i2c recv failed (-6)[ 2.728754] atmel_mxt_ts 1-004a: Trying alternate bootloader address[ 2.736822] atmel_mxt_ts 1-004a: mxt_bootloader_read: i2c recv failed (-6)[ 2.750843] at24 1-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write[ 2.762472] at24 1-0051: 16384 byte 24c128 EEPROM, writable, 1 bytes/write[ 2.771030] rtc-abx80x 1-0069: model 1805, revision 2.3, lot c, wafer 6, uid 2a47[ 2.827016] rtc-abx80x 1-0069: rtc core: registered abx8xx as rtc0[ 2.827049] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 18[ 2.827974] tw9984 2-0028: chip found @ 0x50 (xiic-i2c)[ 2.860431] IR NEC protocol handler initialized[ 2.860433] IR RC5(x/sz) protocol handler initialized[ 2.860435] IR RC6 protocol handler initialized[ 2.860436] IR JVC protocol handler initialized[ 2.860438] IR Sony protocol handler initialized[ 2.860440] IR SANYO protocol handler initialized[ 2.860441] IR Sharp protocol handler initialized[ 2.860443] IR MCE Keyboard/mouse protocol handler initialized[ 2.860444] IR XMP protocol handler initialized[ 2.861440] ifm_bt656_demux a0090000.bt656demux: IFM BT656 demuxer v2017-09-19.13 loaded.[ 2.861549] usbcore: registered new interface driver uvcvideo[ 2.861550] USB Video Class driver (1.1.1)[ 2.862267] Bluetooth: HCI UART driver ver 2.3[ 2.862271] Bluetooth: HCI UART protocol H4 registered[ 2.862273] Bluetooth: HCI UART protocol BCSP registered[ 2.862275] Bluetooth: HCI UART protocol ATH3K registered[ 2.862314] Bluetooth: HCI UART protocol Intel registered[ 2.862315] Bluetooth: HCI UART protocol QCA registered[ 2.862351] usbcore: registered new interface driver bcm203x[ 2.862381] usbcore: registered new interface driver bpa10x[ 2.862409] usbcore: registered new interface driver bfusb[ 2.862438] usbcore: registered new interface driver btusb[ 2.862440] Bluetooth: Generic Bluetooth SDIO driver ver 0.1[ 2.862490] usbcore: registered new interface driver ath3k[ 2.862822] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 1199999 KHz[ 2.862836] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 1199999988 (-34)[ 2.862878] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 799999 KHz[ 2.862898] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 1199999988 (-34)[ 2.863084] sdhci: Secure Digital Host Controller Interface driver[ 2.863085] sdhci: Copyright(c) Pierre Ossman[ 2.863086] sdhci-pltfm: SDHCI platform and OF driver helper[ 3.066164] ledtrig-cpu: registered to indicate activity on CPUs[ 3.066211] ifm_dc a00e0000.displaycontroller: Failed to create outputs[ 3.073459] ifm-panel a00e0400.panel: Valid panel found: sn=00000015 vid:pid=0001:0501[ 3.074024]  Supports vblank timestamp caching Rev 2 (21.10.2013).[ 3.074025]  No driver support for vblank timestamp query.[ 3.099329] hidraw: raw HID events driver (C) Jiri Kosina[ 3.104783] usbcore: registered new interface driver usbhid[ 3.104785] usbhid: USB HID core driver[ 3.105412] zynqmp_r5_remoteproc ff9a0100.zynqmp_r5_rproc: RPU core_conf: split0[ 3.105426] zynqmp_r5_remoteproc ff9a0100.zynqmp_r5_rproc: IPI resource is not specified.[ 3.105593] remoteproc remoteproc0: ff9a0100.zynqmp_r5_rproc is available[ 3.105658] zynqmp_r5_remoteproc ff9a0200.zynqmp_r5_rproc: RPU core_conf: split1[ 3.105666] zynqmp_r5_remoteproc ff9a0200.zynqmp_r5_rproc: IPI resource is not specified.[ 3.105831] remoteproc remoteproc1: ff9a0200.zynqmp_r5_rproc is available[ 3.109668] Console: switching to colour frame buffer device 100x30[ 3.174598] ifm_dc a00e0000.displaycontroller: fb0: frame buffer device[ 3.181332] ifm_dc a00e0000.displaycontroller: IFM DisplayController v2017-09-21.24 loaded.[ 3.182029] ifm-i2s a00f0000.ifm_i2s_master: IFM I2S v2017-08-25.14 loaded.[ 3.182117] pktgen: Packet Generator for packet performance testing. Version: 2.75[ 3.204167] Netfilter messages via NETLINK v0.30.[ 3.208949]  Initialized ifm_dc 1.0.0 20170127 for a00e0000.displaycontroller on minor 0[ 3.209053] ip_tables: (C) 2000-2006 Netfilter Core Team[ 3.222868] Initializing XFRM netlink socket[ 3.227196] NET: Registered protocol family 10[ 3.232161] Segment Routing with IPv6[ 3.235780] ip6_tables: (C) 2000-2006 Netfilter Core Team[ 3.241224] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver[ 3.247375] NET: Registered protocol family 17[ 3.251744] NET: Registered protocol family 15[ 3.256176] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.[ 3.269093] Ebtables v2.0 registered[ 3.272718] can: controller area network core (rev 20170425 abi 9)[ 3.273628] mmc0: SDHCI controller on ff160000.sdhci [ff160000.sdhci] using ADMA 64-bit[ 3.273686] PLL: shutdown[ 3.273775] PLL: enable[ 3.292109] NET: Registered protocol family 29[ 3.292395] ifm-i2s a00f0000.ifm_i2s_master: Failed to get DMA channel capabilities, falling back to period counting: -6[ 3.293041] ifm-i2s a00f0000.ifm_i2s_master: Failed to get DMA channel capabilities, falling back to period counting: -6[ 3.293045] asoc-simple-card sound: wm8960-hifi <-> a00f0000.ifm_i2s_master mapping ok[ 3.326102] can: raw protocol (rev 20170425)[ 3.330333] can: broadcast manager protocol (rev 20170425 t)[ 3.335972] can: netlink gateway (rev 20170425) max_hops=1[ 3.336668] mmc0: new HS200 MMC card at address 0001[ 3.341652] mmcblk0: mmc0:0001 Q2J55L 3.55 GiB[ 3.341724] mmcblk0boot0: mmc0:0001 Q2J55L partition 1 16.0 MiB[ 3.341879] mmcblk0boot1: mmc0:0001 Q2J55L partition 2 16.0 MiB[ 3.341951] mmcblk0rpmb: mmc0:0001 Q2J55L partition 3 4.00 MiB[ 3.350310] mmcblk0: p1 p2 p3[ 3.371618] Bluetooth: RFCOMM TTY layer initialized[ 3.376423] Bluetooth: RFCOMM socket layer initialized[ 3.381541] Bluetooth: RFCOMM ver 1.11[ 3.385270] Bluetooth: BNEP (Ethernet Emulation) ver 1.3[ 3.390561] Bluetooth: BNEP filters: protocol multicast[ 3.395771] Bluetooth: BNEP socket layer initialized[ 3.400717] Bluetooth: HIDP (Human Interface Emulation) ver 1.2[ 3.406621] Bluetooth: HIDP socket layer initialized[ 3.411727] 9pnet: Installing 9P2000 support[ 3.415925] Key type dns_resolver registered[ 3.420563] registered taskstats version 1[ 3.424874] Btrfs loaded, crc32c=crc32c-generic[ 3.440206] rtc-abx80x 1-0069: setting system clock to 2019-01-22 21:03:30 UTC (1548191010)[ 3.448598] clk: Not disabling unused clocks[ 3.452817] ALSA device list:[ 3.455732] #0: a00f0000.ifm_i2s_master-wm8960-hifi[ 3.559691] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)[ 3.567720] VFS: Mounted root (ext4 filesystem) on device 179:1.[ 3.575214] devtmpfs: mounted[ 3.578214] Freeing unused kernel memory: 512K[ 3.585497] random: fast init doneINIT: version 2.88 bootingStarting udev[ 3.769351] udevd: starting version 3.2.2[ 3.779833] random: udevd: uninitialized urandom read (16 bytes read)[ 3.786464] random: udevd: uninitialized urandom read (16 bytes read)[ 3.793114] random: udevd: uninitialized urandom read (16 bytes read)[ 3.817273] udevd: starting eudev-3.2.2[ 3.907479] mali: loading out-of-tree module taints kernel.[ 3.921737] i2c_hid 1-002a: 1-002a supply vdd not found, using dummy regulator[ 4.531234] input: hid-over-i2c 0EEF:C000 as /devices/platform/amba/ff030000.i2c/i2c-1/1-002a/0018:0EEF:C000.0001/input/input0[ 4.542815] input: hid-over-i2c 0EEF:C000 Pen as /devices/platform/amba/ff030000.i2c/i2c-1/1-002a/0018:0EEF:C000.0001/input/input3[ 4.554624] hid-multitouch 0018:0EEF:C000.0001: input,hidraw0: I2C HID v1.00 Pointer [hid-over-i2c 0EEF:C000] on 1-002a[ 4.634309] EXT4-fs (mmcblk0p1): re-mounted. Opts: data=ordered[ 4.949780] PLL: shutdown[ 5.051581] urandom_read: 6 callbacks suppressed[ 5.051585] random: dd: uninitialized urandom read (512 bytes read)ALSA: Restoring mixer settings...INIT: Entering runlevel: 5Configuring network interfaces... [ 5.162238] pps pps0: new PPS source ptp0[ 5.166889] macb ff0b0000.ethernet: gem-ptp-timer ptp clock registered.[ 5.173640] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not readyCannot find device "eth1"Cannot find device "eth1"Cannot find device "eth1"Cannot find device "usb0"resize2fs 1.43.5 (04-Aug-2017)Filesystem at /dev/mmcblk0p1 is mounted on /; o[ 5.256906] EXT4-fs (mmcblk0p1): resizing filesystem from 487272 to 2097152 blocksn-line resizing requiredold_desc_blocks = 2, new_desc_blocks = 8[ 5.290713] EXT4-fs (mmcblk0p1): resized filesystem to 2097152The filesystem on /dev/mmcblk0p1 is now 2097152 (1k) blocks long.resize2fs 1.43.5 (04-Aug-2017)The filesystem is already 262144 (4k) blocks long. Nothing to do!Starting system message bus: dbus./etc/rc5.d/S03disable_splash_screen.sh: line 12: /sys/devices/platform/amba_pl/a00e0000.displaycontroller/splash_state: Permission deniedStarting OpenBSD Secure Shell server: sshdgenerating ssh RSA key...generating ssh ECDSA key...generating ssh DSA key...[ 6.177853] macb ff0b0000.ethernet eth0: link up (100/Full)[ 6.183372] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes readygenerating ssh ED25519 key...done.

author: Postal2
author_rank: Frequent Contributor
timestamp: December 22, 2024, 12:58:25 pm
content: I can also pile on a lot.Code:ECC Data Bytepos=32a Bitpos=40 correctedC.ifr_newnewx.so.ifr_new:583 CRC errorECC Data Bytepos=1c Bitpos=4 corrected 5 10005 14 vmAC.ifr_newcrc32 forDDR DPLL in Lock mode:ifr_05 14 ModJan 01DDR clock 266 Mhz [266/1]4 touchdriver.ifr_new5 5Disp DPLL in Lock mode:fr_Jan 01 00:00:00.339Disp clock 192 Mhz [192/1]0005 14 spidriver.ifr_newMPU DPLL in Lock mode:ver.ifr_new00.338 5MPU clock 800 Mhz [800/1] 5 10005 14 resources.ifPER DPLL in Lock mode:14 Progress 100n 01 00:PER clock 192 Mhz [960/5]336 5 10005 14 md4_timCORE DPLL in Lock mode:ROR: Ifr file md4_qnx_dM4 CORE clock 200 Mhz [2000/10]7 5 10005 14 md4_qt.ifr_newM5 CORE clock 250 Mhz [2000/8]2 errorJan 01ECJan 01 00:00:M6 CORE clock 500 Mhz [2000/4]fr_new 14 touchdriver.ifr_EJumping to QNXs=be2 BitpoJaMD4 QNX startup7 5 10005nanddriver: devio_readtrans:583 CRC errorpos=80 correctedewogress 100Jan 0Time Sev Major 32a BitJan 01 00:00:00.337 5 10005 14 vmGC.ifr_newnewio_readtrans:583 CRC error.R DPLL in Lock modJan 01 00:00:00.337 5 10005 14 vmAC.ifr_newcrc32 for module md4_qnx_display.ifr_05 14 ModJan 01 00:00:00.337 5 10005 14 touchdriver.ifr_new# ECC Datanew started0:00.335Jan 01 00:00:00.340Jan 01 00:00:00.337 5 10005 14 spidriver.ifr_new invorrected14 libmd4Jan 01 00:00:00.335 5 10005Jan 01 00:00:00.338 5 10005 14 resources.ifr_new.429 5 10005 14 Progress 100n 01 00:00:00.335Jan 01 00:00:00.338 5 10005 14 md4_time.ifr_new 10005 14 ERROR: Ifr file md4_qnx_display.ifr_newJan 01 00:00:00.338 5 10005 14 md4_qt.ifr_newwcorrectedr_new4].ifr_new[2000/32 errorles to uECJan 01 00:00:00.338 5 10005 14 md4_qnx.ifr_newfr_new66 Mhz [266/1]uleECC Data Bytepos=1a9 Bitpos=Jan 01 00:00:00.338 5 10005 14 md4_install.ifr_newData Bytepos=be2 Bitpos=1 correctednewJanMPU DPLL inJan 01 00:00:00.338 5 10005 =5d5 Bitpock 800Jan 01 00:00:00.338 5 10005 14 libmd4.a.ifr_newcorrected0TimMPU clock 800 Mhz [800/1] 5 1000Jan 01 00:00:00.339 5 10005 14 images.ifr_news/startup.sh: NPER clock 192 Mhz [960/5]336Jan 01 00:00:00.339 5 10005 14 i2cdriver.ifr_new86f Bitpos=2M4 CORE clock 200 Mhz [2000/10]6 5Jan 01 00:00:00.339 5 10005 14 fonts.ifr_new[2000/8]ectedorMPUJan 01 00:00:M6 COREJan 01 00:00:00.339 5 10005 14 devnp-am335x.so.ifr_newng to QNXCC Data BytJaMD4 QNX startup6 5 10005nandJan 01 00:00:00.339 5 10005 14 camserver.ifr_news=40 correctedlock

author: glenneaux
author_rank: Contributor
timestamp: December 22, 2024, 01:07:56 pm
content: Quote from: Postal2 on December 22, 2024, 12:58:25 pmWhat is this ?

author: Postal2
author_rank: Frequent Contributor
timestamp: December 22, 2024, 01:15:47 pm
content: Quote from: glenneaux on December 22, 2024, 01:07:56 pmThis is the QNX startup, stupidly copied from HyperTerminal.

author: glenneaux
author_rank: Contributor
timestamp: December 22, 2024, 01:42:59 pm
content: Quote from: Postal2 on December 22, 2024, 01:15:47 pmoh ok.I guess, if I try and get console working at 115.2kbps per your suggestion, I could probably just flash this new bootloader in and see what happens - I probably wont lose the console (maybe).I believe uboot has a default environment hardcoded into the bootloader as a fallback. Looking at my device, i can see the baudrate=115200 command from the bootloader image - and can see baudrate=19200 in both of my environment partitions, and i know these contain a crc check. Apparently the bootloader itself does not?If so, inspecting the new bootloader, i can see its baudrate=115200 variable... if uboot does not perform crc check in theory it would be possible to alter this default variable - once in uboot i can manually set the actual environment variables and continue to attempt loading the kernel/device tree image by tftp.

author: Postal2
author_rank: Frequent Contributor
timestamp: December 22, 2024, 02:14:22 pm
content: Quote from: glenneaux on December 22, 2024, 01:42:59 pmI've changed environment variables by directly editing the image and never had problems. This applies to the bootloader, you can set baudrate, change the timeout, and I don't remember what, and it always worked for me.I don't understand at all what you are doing. You can write everything directly from Linux, using dd with maximum rights. You know how to set 19200. If it doesn't work, then you can figure it out. But first you need to copy the image. Then, before writing a new one, compare visually, usually this is enough. If it stops starting at all, then I would unsolder the nor flash and conduct temporary experiments with the flash in a familiar case. Perhaps I would use JTAG if I had everything configured. Perhaps the chip has a bootrom and it is easier to use.

author: langwadt
author_rank: Super Contributor
timestamp: December 22, 2024, 02:50:49 pm
content: Quote from: glenneaux on December 22, 2024, 01:42:59 pmif crc fails you get a warning that the default is used

author: glenneaux
author_rank: Contributor
timestamp: December 23, 2024, 01:58:05 am
content: Quote from: Postal2 on December 22, 2024, 02:14:22 pmWell I can confirm that editing the parameters through editing the binary worked no worries.I was able to change the default environment baudrate to 19200 and flash it back in.My goal here was to get the device onto a production firmware, or at least operating system, so that I would be able to program the device (HMI) with Codesys. Having the production firmware would mean I would have the accompanying codesys library to allow programming.Since doing that, I built up courage and modified the binary of the production v2.2.2.1, chaning baudrate to be 19200, and flashed it.Device now has some messages come up on the console at 115.2kbps and uboot doesn't appear.Next steps - play around with the opamp circuit to get back to 115.2kbps, and then work on rectifying the problem with the new bootloader (unlikely), or, work on getting the old binary reloaded (jtag?)

author: Postal2
author_rank: Frequent Contributor
timestamp: December 23, 2024, 03:52:09 am
content: Quote from: glenneaux on December 23, 2024, 01:58:05 amI changed environment variables only for the bootloader. I would have tried system variables, but I had no reason.I assume that restoring 115200 will show an unrecoverable error and will not be useful. At this point, I would try JTAG, because Xilinx loves it. I have a cable bought on Aliexpress for $25, which supports all chips, like DLC9LP (with the right stuffing). I connected it to ISE 13, ISE 14 under Windows XP, it works absolutely without problems. I don't know anything about your chip. I can only say that the situation with JTAG adapters is the same as with TI, i.e. you can buy an expensive adapter and suddenly find out that it only supports MSP430.

author: glenenglish
author_rank: Frequent Contributor
timestamp: December 26, 2024, 04:46:30 am
content: Buy a Xilinx Platform Cable II JTAG pod. There are a few inexpensive options. Maybe just - the USB pod. USD270.https://www.xilinx.com/products/boards-and-kits/hw-usb-ii-g.htmlMost of the ALiexpress pods are DLC10 - old Platform cable - 1there might be limited Vivado support for NON XILINX pods.This aliexpress one might work, worth the USD25 gamble... Not sure it supports 1.8V VCCIO....https://www.aliexpress.com/item/1005003712446430.html?src=google&albch=search&acnt=479-062-3723&isdl=y&aff_short_key=UneMJZVf&albcp=21520181001&albag=168529894787&slnk=&trgt=dsa-1642801257570&plac=&crea=707748366228&albad=707748366228&netw=g&device=c&mtctp=&memo1=&albbt=Google_7_search&aff_platform=google&albagn=888888&isSmbActive=false&isSmbAutoCall=false&needSmbHouyi=false&gad_source=1&gclid=Cj0KCQiA9667BhDoARIsANnamQa5aOpJKF8IaDPfs3cSx3Wu8pw16owlGeho80B2s0hocRcnKDDTeJAaAj6BEALw_wcB

author: langwadt
author_rank: Super Contributor
timestamp: December 26, 2024, 05:36:59 pm
content: Quote from: glenenglish on December 26, 2024, 04:46:30 aman FTDI shoudl do,https://www.eevblog.com/forum/fpga/custom-jtag-debugger-for-xilinx-fpgas-based-on-ft22x-chips/