ChrisArena52

I see this problem WITH the CONFIG_OABI_COMPAT=y. Is this still a problem anyone else is seeing? Thanks!

New twist to the story: I'm getting a real complaint right after the nuisance message about a buggy DT, but I can't decipher the problem. The spidev module is loaded. My new CB1 system: cubie@cubieboard:~/Projects/spidev_test$ uname -a Linux cubieboard 4.7.0-sunxi #4 SMP Mon Jun 20 13:16:19 EDT 2016 armv7l armv7l armv7l GNU/Linux cubie@cubieboard:~/Projects/spidev_test$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial The SPI complaint: [ 6.941247] spidev spi32766.0: buggy DT: spidev listed directly in DT [ 6.941267] ------------[ cut here ]------------ [ 6.941291] WARNING: CPU: 0 PID: 200 at drivers/spi/spidev.c:719 spidev_probe+0x1a8/0x1c4 [spidev] [ 6.941297] Modules linked in: spidev(+) bonding [ 6.941318] CPU: 0 PID: 200 Comm: systemd-modules Not tainted 4.7.0-sunxi #4 [ 6.941324] Hardware name: Allwinner sun4i/sun5i Families [ 6.941354] [<c010e750>] (unwind_backtrace) from [<c010b0c8>] (show_stack+0x10/0x14) [ 6.941370] [<c010b0c8>] (show_stack) from [<c052b12c>] (dump_stack+0x90/0xa4) [ 6.941386] [<c052b12c>] (dump_stack) from [<c0120794>] (__warn+0xe8/0x100) [ 6.941399] [<c0120794>] (__warn) from [<c0120854>] (warn_slowpath_null+0x20/0x28) [ 6.941415] [<c0120854>] (warn_slowpath_null) from [<bf0262fc>] (spidev_probe+0x1a8/0x1c4 [spidev]) [ 6.941438] [<bf0262fc>] (spidev_probe [spidev]) from [<c0619e6c>] (spi_drv_probe+0x7c/0xa8) [ 6.941455] [<c0619e6c>] (spi_drv_probe) from [<c05bf4ac>] (driver_probe_device+0x218/0x2c8) [ 6.941468] [<c05bf4ac>] (driver_probe_device) from [<c05bf608>] (__driver_attach+0xac/0xb0) [ 6.941479] [<c05bf608>] (__driver_attach) from [<c05bd890>] (bus_for_each_dev+0x60/0x94) [ 6.941491] [<c05bd890>] (bus_for_each_dev) from [<c05bea98>] (bus_add_driver+0x1a0/0x218) [ 6.941504] [<c05bea98>] (bus_add_driver) from [<c05bfe2c>] (driver_register+0x78/0xf8) [ 6.941520] [<c05bfe2c>] (driver_register) from [<bf029090>] (spidev_init+0x90/0xc8 [spidev]) [ 6.941537] [<bf029090>] (spidev_init [spidev]) from [<c0101820>] (do_one_initcall+0x40/0x170) [ 6.941555] [<c0101820>] (do_one_initcall) from [<c01b8814>] (do_init_module+0x60/0x1c4) [ 6.941575] [<c01b8814>] (do_init_module) from [<c0192dc8>] (load_module+0x1b30/0x1d78) [ 6.941589] [<c0192dc8>] (load_module) from [<c01931e0>] (SyS_finit_module+0x8c/0x9c) [ 6.941605] [<c01931e0>] (SyS_finit_module) from [<c0107480>] (ret_fast_syscall+0x0/0x3c) [ 6.941614] ---[ end trace 194268e1a0e2160e ]--- My SPI section in the DTB: spi@01c05000 { compatible = "allwinner,sun4i-a10-spi"; reg = <0x1c05000 0x1000>; interrupts = <0xa>; clocks = <0x3 0x14 0x18>; clock-names = "ahb", "mod"; dmas = <0x19 0x1 0x1b 0x19 0x1 0x1a>; dma-names = "rx", "tx"; status = "okay"; #address-cells = <0x1>; #size-cells = <0x0>; pinctrl-names = "default"; pinctrl-0 = <0x1a 0x1b>; spidev@0x00 { compatible = "spidev"; spi-max-frequency = <0x2faf080>; reg = <0x0>; }; }; The spidev_test exits with "invalid argument", but the interface does something as the CS is activated: I'm triggering on CS. Clock goes low but doesn't "clock". ???? Thanks!! Chris

So did the limit removal patch fix it? Is that patch incorporated into anything?

My link line: g++ build/CCircularBuffer.o build/CGuiWindow.o build/CMessageHandler.o build/CSpiMaster.o build/CHoldInterrupts.o \ build/CSpiMessage.o build/CSetPoint.o build/guiMain.o build/MsgQueueType.o build/CVentilatorTestMsg.o build/CVentilatorParmMessages.o \ build/CGpioInputBit.o build/CGpioBit.o build/CPeriodic.o build/COnDemand.o build/CTrigger.o build/FlowDataPointType.o build/crcpy.o \ -L/usr/lib/arm-linux-gnueabihf -lm -lc `fltk-config --ldflags` -lpthread -o guiMain

An actual compile line is: g++ -c -std=c++11 -fno-rtti -D__packed="__attribute__((__packed__))" -Iinc -I `fltk-config --includedir` -g -Wall -g -MD -MP -MF .dep/CGuiWindow.o.d src/CGuiWindow.cpp -o build/CGuiWindow.o I do have -std=c++11 set which might be unusual. Nothing else out of the norm. But I didn't have that set for the "hello world" program that failed.

The only thing that debsums -cs complained about was the sun4i-a10-cubieboard.dtb I modified to enable SPI. I'm surprised that the check covered that file. Is there a link option that makes the image "modern" so that the deprecated OABI_COMPAT isn't needed? I'm compiling like: g++ main.cpp -g -o main It's more elaborate with multiple .o files when I link, but essentially like that.

Do you have CONFIG_OABI_COMPAT set in that kernel?

OK, that file is there. But it is behaving as though the target should be a remote ... "run" gives me a "Don't know how to run. Try help target". But it's not SIGSEGV-ing at least. This is weird ... why does THIS gdb behave differently from any other native gdb? I can't get it the program to start. Is this a proxy program or something? I'm not connected via a serial line. I'm trying to run a native program on the CB1 under the debugger. Thanks Chris

I have: cubie@cubieboard:/sys/class/gpio/gpio139$ gdb --version GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-linux-gnueabihf". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". This gdb crashes with: Program received signal SIGSEGV, Segmentation fault. 0xb6fd9822 in ?? () from /lib/ld-linux-armhf.so.3 A "hello world" program crashes exactly the same way -- AFAICS. Doing "apt-get install gdb-arm-none-eabi" does not install a binary executable by that name on my CB1. Thanks Chris

OK, this is really killing me now. My gdb is new enough: cubie@cubieboard:~/$ apt-cache show gdb gdb-arm-none-eabi Package: gdb Priority: optional Section: devel Installed-Size: 5051 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Héctor Orón Martínez <zumbi@debian.org> Architecture: armhf Version: 7.11-0ubuntu1 Replaces: gdb, gdb-doc (<< 7.8-1~) Depends: libbabeltrace-ctf1 (>= 1.2.1), libbabeltrace1 (>= 1.2.1), libc6 (>= 2.15), libexpat1 (>= 2.0.1), liblzma5 (>= 5.1.1alpha+20110809), libncurses5 (>= 6), libpython3.5 (>= 3.5.0~b1), libreadline6 (>= 6.0), libtinfo5 (>= 6), zlib1g (>= 1:1.2.0) Recommends: libc-dbg, libcc1-0, gdbserver Suggests: gdb-doc Conflicts: gdb Filename: pool/main/g/gdb/gdb_7.11-0ubuntu1_armhf.deb Size: 2229164 MD5sum: a9d02baef1a64fc61b1689a9fed59b0f SHA1: a8581e2ed7ebba9f17eec24cee180d6017d54365 SHA256: c3dc84d8115d41b742189d95aff8168e3cacaa25ee877846990fd16cfaafd947 Description-en: GNU Debugger GDB is a source-level debugger, capable of breaking programs at any specific line, displaying variable values, and determining where errors occurred. Currently, gdb supports C, C++, D, Objective-C, Fortran, Java, OpenCL C, Pascal, assembly, Modula-2, Go, and Ada. A must-have for any serious programmer. Description-md5: 4f2b8eb95df2ba7a5b11e0301c48b8e4 Multi-Arch: allowed Homepage: http://www.gnu.org/s/gdb/ Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Supported: 9m Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, kubuntu-full, edubuntu-desktop, edubuntu-usb, xubuntu-desktop, mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, mythbuntu-backend-master, mythbuntu-backend-master, ubuntustudio-desktop, ubuntu-gnome-desktop, ubuntu-touch-core, ubuntu-touch, ubuntu-sdk, ubuntukylin-desktop, ubuntu-mate-desktop Package: gdb-arm-none-eabi Priority: extra Section: universe/devel Installed-Size: 5326 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Agustin Henze <tin@debian.org> Architecture: armhf Source: gdb-arm-none-eabi (9) Version: 7.10-1ubuntu3+9 Depends: libc6 (>= 2.15), libexpat1 (>= 2.0.1), libncurses5 (>= 6), libpython2.7 (>= 2.7), libreadline6 (>= 6.0), libtinfo5 (>= 6), zlib1g (>= 1:1.2.0) Recommends: gcc-arm-none-eabi Filename: pool/universe/g/gdb-arm-none-eabi/gdb-arm-none-eabi_7.10-1ubuntu3+9_armhf.deb Size: 2406174 MD5sum: 4b3656ea81660478e0ed5f27fda67f86 SHA1: 738f1f4016c03108fd74d68f1ce4bd398f17c526 SHA256: 07442d48b1c27953087d8639b90316c2fc8c1044fbee8fe5ded4be09557775f4 Description-en: GNU debugger for ARM Cortex-A/R/M processors Bare metal GNU debugger for embedded ARM chips using Cortex-M0/M0+/M3/M4, Cortex-R4/R5/R7 and Cortex-A* processors. GDB is a source-level debugger, capable of breaking programs at any specific line, displaying variable values, and determining where errors occurred. Description-md5: c034a489da482847d1aaa1c6157f9f71 Built-Using: gdb (= 7.10-1ubuntu3) Homepage: http://www.gnu.org/s/gdb/ Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu So what's doing this? I'll rebuild with the OABI_COMPAT set in this new image. What's the long term solution that's not deprecated? Thanks, Chris

I tried the Xenial this time. root@cubieboard:/boot# uname -a Linux cubieboard 4.6.2-sunxi #1 SMP Sat Jun 11 15:28:33 EDT 2016 armv7l armv7l armv7l GNU/Linux root@cubieboard:/boot# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial root@cubieboard:/boot# That booted normally the first time. Nice! Thanks! Chris

Moving a copy of uInitrd to the malfunctioning image allows it to boot ... Igor, what happened to that file? Chris

Mounting the SD Card on a CB2 I have running, I see the SD card has no uInitrd file under /boot ... ??

On a fresh download, configuring a CB1, Desktop Vanilla system, I get: U-Boot 2016.05-armbian (Jun 10 2016 - 17:25:48 -0400) Allwinner Technology CPU: Allwinner A10 (SUN4I) Model: Cubietech Cubieboard I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment HDMI connected: Setting up a 1280x720 hdmi console (overscan 0x0) In: serial Out: vga Err: vga SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c0b000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 5 USB Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2447 bytes read in 211 ms (10.7 KiB/s) ## Executing script at 43100000 0 bytes read in 151 ms (0 Bytes/s) 0 bytes read in 161 ms (0 Bytes/s) 25257 bytes read in 284 ms (85.9 KiB/s) ** File not found /boot/uInitrd ** ** Unrecognized filesystem type ** ** File not found uInitrd ** 6132416 bytes read in 714 ms (8.2 MiB/s) Kernel image @ 0x46000000 [ 0x000000 - 0x5d92c0 ] Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... scanning bus for devices... Found 0 device(s). SCSI device 0: Device 0: not available USB device 0: unknown device ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 DHCP client bound to address 192.168.20.16 (48 ms) *** Warning: no boot file name; using 'C0A81410.img' Using ethernet@01c0b000 device TFTP from server 0.0.0.0; our IP address is 192.168.20.16; sending through gateway 192.168.20.1 Filename 'C0A81410.img'. Load address: 0x42000000 Loading: T T T T T T T T T T Retry count exceeded; starting again I'm going to clear the decks and do a completely fresh, unmodified git clone. The first time I did that, I made some small changes in the kernel config for lcd backlight & pwm control, second time I just exited out of the kernel config and let it run to completion. I have a serial console set up to watch the boot. After the first failure, I did a badblocks check --- no bad blocks, This same hardware ran a legacy version with the modified u-boot just before this failure with a Vanilla image. After a pristine download, and not requiring any kernel configuration changes, I get the same failure. Selection: Full OS image, Cubieboard, next, Trusty, Image with Desktop environment --> boot fail. Anyone else seeing this? Chris

I found the problem: I have no gpio_para section in my script.bin. I modified the default script.bin turning on SPI, but I didn't check the GPIO section. Its missing in the default script.bin for some reason. Chris