• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map





Everything posted by shaddow501

  1. Update this crash happens after it try to load or load the network interfaces also notice that during those crashes it start to ruin the installed image..
  2. Hello Got a new board recently and trying to load the latest image Armbian 5.90. I get crashes with every boot: Starting kernel ... [ 9.306138] Unable to handle kernel paging request at virtual address ffff00007bfa3420 [ 9.314093] Mem abort info: [ 9.316964] ESR = 0x96000005 [ 9.320170] Exception class = DABT (current EL), IL = 32 bits [ 9.326418] SET = 0, FnV = 0 [ 9.329469] EA = 0, S1PTW = 0 [ 9.332606] Data abort info: [ 9.335484] ISV = 0, ISS = 0x00000005 [ 9.339315] CM = 0, WnR = 0 [ 9.342282] swapper pgtable: 4k pages, 48-bit VAs, pgdp = (____ptrval____) [ 9.349161] [ffff00007bfa3420] pgd=00000000bbffe803, pud=0000000000000000 [ 9.355960] Internal error: Oops: 96000005 [#1] SMP [ 9.360832] Modules linked in: brcmfmac snd_soc_simple_card brcmutil snd_soc_simple_card_utils snd_soc_spdif_tx snd_soc_hdmi_codec snd_soc_core cfg80211 snd_pcm_dmaengine snd_pcm lima snd_timer snd gpu_sched soundcore ttm sun4i_gpadc_iio axp20x_adc axp20x_battery axp20x_ac_power dw_hdmi_cec dw_hdmi_i2s_audio industrialio cpufreq_dt zram thermal_sys pinctrl_axp209 realtek [ 9.393687] Process swapper/2 (pid: 0, stack limit = 0x(____ptrval____)) [ 9.400385] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.19.57-sunxi64 #5.90 [ 9.407337] Hardware name: BananaPi-M64 (DT) [ 9.411604] pstate: 00000085 (nzcv daIf -PAN -UAO) [ 9.416398] pc : irq_work_tick+0x1c/0x60 [ 9.420320] lr : update_process_times+0x3c/0x58 [ 9.424845] sp : ffff000008013dd0 [ 9.428155] x29: ffff000008013dd0 x28: ffff80007bfa3280 [ 9.433462] x27: ffff80007bfa2d40 x26: 0000000000000002 [ 9.438771] x25: 0000000000000080 x24: 000000022a52c35a [ 9.444079] x23: ffff80007bfa2da0 x22: 0000000000000000 [ 9.449386] x21: ffff00000919bdf0 x20: 0000000000000000 [ 9.454693] x19: ffff000008d66000 x18: 0000000000000000 [ 9.460001] x17: 0000000000000000 x16: 0000000000000000 [ 9.465308] x15: 0000000000000259 x14: 0000000000000400 [ 9.470616] x13: 0000000000000000 x12: 0000000000000001 [ 9.475925] x11: 00000000026b9c98 x10: 0000000000000040 [ 9.481232] x9 : ffff000008d91f48 x8 : ffff800079400248 [ 9.486541] x7 : ffff000008d6a940 x6 : 000000001bd17a29 [ 9.491848] x5 : 0000000000000415 x4 : 000080007323d000 [ 9.497156] x3 : 0000000000000001 x2 : 000080007323d000 [ 9.502463] x1 : ffff000008013dd0 x0 : ffff000008d66420 [ 9.507771] Call trace: [ 9.510217] irq_work_tick+0x1c/0x60 [ 9.513789] update_process_times+0x3c/0x58 [ 9.517972] tick_sched_handle.isra.5+0x30/0x48 [ 9.522498] tick_sched_timer+0x48/0x98 [ 9.526331] __hrtimer_run_queues+0xe4/0x1f8 [ 9.530597] hrtimer_interrupt+0xf4/0x2b0 [ 9.534607] arch_timer_handler_phys+0x28/0x40 [ 9.539049] handle_percpu_devid_irq+0x80/0x138 [ 9.543577] generic_handle_irq+0x24/0x38 [ 9.547584] __handle_domain_irq+0x5c/0xb0 [ 9.551678] gic_handle_irq+0x58/0xa8 [ 9.555336] el1_irq+0xb0/0x140 [ 9.558475] arch_cpu_idle+0x10/0x18 [ 9.562049] do_idle+0x1d4/0x298 [ 9.565275] cpu_startup_entry+0x20/0x28 [ 9.569195] secondary_start_kernel+0x18c/0x1c8 [ 9.573724] Code: 910003e1 90006013 91108260 d538d082 (f8626803) [ 9.579812] ---[ end trace 2e56c3b86178f377 ]--- [ 9.584425] Kernel panic - not syncing: Fatal exception in interrupt [ 9.590775] SMP: stopping secondary CPUs [ 9.594696] Kernel Offset: disabled [ 9.598181] CPU features: 0x0,24802004 [ 9.601924] Memory Limit: none [ 9.604978] Rebooting in 10 seconds.. How to get this fixed? what should I do? is it the module problem? since the original image from BPI works (based on kernel 4.4.89)
  3. I have a another question. Do you happen to know how to enable the DSI interface to work with DSI LCD?
  4. I moved to the newer image based on Ubuntu 18x since with the older image that I have had installed that was based on kernel 4.x , when updated to the new kernel the xfce were kind of slow and unresponsive, it also didnt let me update the u-boot to the new one so decided to go with a fresh new image. I am still looking how to create the u-boot logo, but it is not so important.
  5. Dear martinayotte Thanks for the help, my parameters are: ads7846_device model=7846 cs=1 gpio_pendown=234 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=150 x_min=3900 x_max=200 y_min=3900 y_max=200 busnum=1 I was finally was able to trick and install the driver. I dont say it is the correct way but it worked. 1. Install kernel headers => dpkg -i linux-headers-dev-sunxi64_5.90_arm64.deb 2. go into the /usr/src/headers... & make modules (till it it has the error I posted before) 3. go into the make the driver in the ads7846_device and just "make" (not make install !!!) 4. Delete /usr/src/linux-headers.. 5. Install kernel headers => dpkg -i linux-headers-dev-sunxi64_5.90_arm64.deb => but now not to "make modules" anything just to have it there. 6. go into the make the driver in the ads7846_device and now perform the "make install" + depmod (now to goes to the right location) 7. Reboot. And now the touch is working!!! I am not sure if I had to do all those steps but hey it is working, I am happy and now I have battery support + 1-wire support, the python GPIO are working, the WiringPI is working. the only thing that I am now facing is to have u-boot - logo... but it is not that important since everything else is working. Thanks for your help. sure I would like to have your patch install but I do not know were exactly to put my values....
  6. git clone
  7. git clone
  8. Well in the previous kernels I havent got any issues and also I could compile the "make modules" in the linux headers without any errors. How do you create that patch? it is easier sure for someone that know how to do it? Remember I moved to this kernel because I wanted to fix the functionality of the 1-wire & now I am facing a whole new problems. It like going to the car repair shop to fix an oil leak, but no lets replace all the engine, but not the engine doesnt fit so lets replace the whole car really??? Surely it is a problem with the "Linux headers" it should have been compiled without any issues. Please help.
  9. Ok finally created a new image with a new Kernel and started the process of installing all the hardware, so now yes I see that I have battery support & onewire is shown under GPIO. And now started to install the touch panel as like that I have done with the previous kernel. first install Linux headers dpkg -i and the Linux headers, ok installed! not quite... need to go inside the Linux headers and "make modules" in order that I will able to compile the kernel module... and this is what I get: root@bananapim64:/usr/src/linux-headers-5.1.15-sunxi64# make modules UPD include/config/kernel.release UPD include/generated/utsrelease.h CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o CC scripts/mod/devicetable-offsets.s UPD scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost make[1]: *** No rule to make target 'arch/arm64/kernel/vdso/', needed by 'arch/arm64/kernel/vdso/'. Stop. arch/arm64/Makefile:166: recipe for target 'vdso_prepare' failed make: *** [vdso_prepare] Error 2 ok, dont know what it is but lets see if I can go on, next to that I need to run the command "make scripts" this command finish without any issues. go back to the driver make succeed, I dont see any errors, make install, again no errors cool.... than depmod, again no errors. when trying call the driver by modprobe ads7846_device I get FATAL: Module ads7846_device not found in directory /lib/modules/5.1.15-sunxi64 apparently it created a folder 5.1.15 and installed there the "extra" folder with the drivers inside. OK.. moved that extra folder into the 5.1.15-sunxi64 folder.. and deleted the 5.1.15 folder. Now try again...: running depmod again and again there is a folder name 5.1.15 with the extra inside.. created link: sudo ln -s /lib/modules/5.1.15/extra/ads7846_device.ko /lib/modules/5.1.15-sunxi64/ depmod -a next: modprobe: FATAL: Module ads7846_device.ko not found in directory /lib/modules/5.1.15-sunxi64 but it is there!!! ok different approach edited the MakeFile obj-m := ads7846.o KDIR := /lib/modules/5.1.15-sunxi64/build PWD := $(shell pwd) all: $(MAKE) -C $(KDIR) M=$(PWD) modules clean: $(MAKE) -C $(KDIR) M=$(PWD) clean install: $(MAKE) -C $(KDIR) M=$(PWD) modules_install than finally when I try to run i get another present. ERROR: could not insert 'ads7846_device': Exec format error dmesg says: ads7846_device: version magic '5.1.15 SMP mod_unload aarch64' should be '5.1.15-sunxi64 SMP mod_unload aarch64' I think when people curse you "Go to hell" they mean that you start to work with Linux! why depmod dosnt enter the files to the right location? WHY??? Well, I think I know why, it is because of the Linux headers that didnt complete the make... But how to fix it?
  10. like this: sudo ./ BOARD=bananapim64 BRANCH=dev KERNEL_ONLY=yes KERNEL_CONFIGURE=no EXPERT=yes
  11. the only way it let me go to the dev is by using the command. since no menu have given me the selection sudo ./ BOARD=bananapim64 BRANCH=dev KERNEL_ONLY=yes KERNEL_CONFIGURE=no
  12. Could it be that you have special developer rights that you do get this menu? I dont know, I just dont get it here!!
  13. I am interested only in u-boot and kernel but I dont have those menus that you have, the bananapim64.conf file is the same as yours. look, when I select the bananapim64 it start working... I dont get menu for choosing next or dev. here are the menus that I have. sorry it got mixed the selection of the u-boot and kernel is before the selection of the board, but I cant seem to change the order here...
  14. Ill check and update, I know that I have the default settings as eas downloaded from git. But do you think that this 5.1 kernel will solve the battry and w1 issue ? in your pine 64 do you have ac and bsttery under sys/class/powersupply ?
  15. You are right, but it doesnt let me choose, try for yourself, when you select bannapim64 you dont have any choosing....
  16. When i go with sudo ./ EXPERT=yes then it loads the screen that i can select kernel + u-boot or full image than I select bananapiM64 and=> It still goes to => Checking git sources [ linux-mainline orange-pi-4.19 ]
  17. Cool I really would like to but when I do build (Armbian build => sudo it only let me have the latest bananaPI kernel which is the 4.19.57-sunxi64 #5.90, how can I get the newer one?? and the file 0001-add-pine64-DT-files.patch is located at /armbian/build/patch/kernel/pine64-default
  18. In the pine 64 at 0001-add-pine64-DT-files.patch there is: + onewire_device@0 { + compatible = "w1-gpio"; + gpios = <0x30 0x2 0x8 0x0 0x0 0x0 0x0>; + pinctrl-names = "default"; + pinctrl-0 = <0xba>; + status = "okay"; (in two places) + onewire_device@0 { + compatible = "w1-gpio"; + gpios = <0x30 0x2 0x8 0x0 0x0 0x0 0x0>; + pinctrl-names = "default"; + pinctrl-0 = <0xba>; + status = "okay"; I dont know if it is relevant or not.. also in pine 64.dts onewire_device@0 { compatible = "w1-gpio"; gpios = <0x30 0x2 0x8 0x0 0x0 0x0 0x0>; pinctrl-names = "default"; pinctrl-0 = <0xba>; status = "okay"; }; in the sun50i-a64-bananapi-m64.dts there is nothing that relate to onewire. also none onewire at bananapim64.dts could it be related to the issue?
  19. Clearly something is different. About your pine64 did you able to get support for AC/battery Power? Since I didnt find anything that could fix that on my BPI_M64 with Armbian kernel. When I do root@bananapim64:/sys/kernel # dmesg | grep axp [ 1.800114] axp20x-rsb sunxi-rsb-3a3: AXP20x variant AXP803 found [ 1.803353] input: axp20x-pek as /devices/platform/soc/1f03400.rsb/sunxi-rsb-3a3/axp221-pek/input/input0 [ 1.809240] axp20x-rsb sunxi-rsb-3a3: AXP20X driver loaded [ 3.022651] axp20x-gpio axp20x-gpio: DMA mask not set [ 3.023118] axp20x-gpio axp20x-gpio: AXP209 pinctrl and GPIO driver loaded [ 5.478240] axp20x-battery-power-supply axp20x-battery-power-supply: DMA mask not set [ 5.478682] axp20x-adc axp813-adc: DMA mask not set [ 5.483612] axp20x-ac-power-supply axp20x-ac-power-supply: DMA mask not set And there is no support for battery. root@bananapim64:/sys/kernel # ls /sys/class/power_supply root@bananapim64:/sys/kernel # (nothing) - > should be ac , battery folders... With BPI_M64 image based on kernel 4.4.89 I do have those features but I cannot get my 5" display working properly, and have no idea how to add the 1-wire + spidev support. it seems that with every image there are issues....
  20. I think that "Allwinner" based modules only winning by confusing us...and giving us a hard time.. is this post give you any idea ?!topic/beagleboard/cR3SxXbWeKc or this;
  21. Done it dtc -O dtb -o w1-gpio-overlay.dtbo -b 0 -@ w1-gpio-overlay.dts w1-gpio-overlay.dtbo: Warning (unit_address_vs_reg): /fragment@0/__overlay__/onewire@0: node has a unit name, but no reg property than mkdir /sys/kernel/config/device-tree/overlays/w1 cat /root/w1-gpio-overlay.dtbo > /sys/kernel/config/device-tree/overlays/w1/dtbo cd /sys/kernel/config/device-tree/overlays root@bananapim64:device-tree/overlays # ls w1 root@bananapim64:device-tree/overlays # cd w1 root@bananapim64:overlays/w1 # ls dtbo path status but it didnt change anything... oot@bananapim64:~ # dmesg | grep w1 [ 5.222841] w1-gpio onewire@0: gpio_request (pin) failed [ 5.222862] w1-gpio: probe of onewire@0 failed with error -22 By the way I am now with updated Kernel version - 4.19.57-sunxi64 #5.90
  22. Lol at least you have some ideas, I have none I had a similar issue with the touch panel "pendown" that it didnt accept the GPIO number "64" and I had to work around and set it to gpio "234" You can see what I did with this post: but I dont know what to do with the W1-GPIO
  23. Everything looks good, here have a look U-Boot 2019.04-armbian (May 03 2019 - 17:44:31 +0200) Allwinner Technology CPU: Allwinner A64 (SUN50I) Model: BananaPi-M64 DRAM: 2 GiB MMC: Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000' mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from EXT4... MMC: no card present In: serial Out: serial Err: serial Allwinner mUSB OTG (Peripheral) Net: phy interface7 eth0: ethernet@1c30000 Warning: usb_ether using MAC address from ROM , eth1: usb_ether MMC: no card present MMC: no card present 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 1 for devices... 1 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found scanning bus 3 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3042 bytes read in 1 ms (2.9 MiB/s) ## Executing script at 4fc00000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 694 bytes read in 1 ms (677.7 KiB/s) MMC: no card present 33861 bytes read in 4 ms (8.1 MiB/s) 794 bytes read in 2 ms (387.7 KiB/s) Applying kernel provided DT overlay sun50i-a64-i2c0.dtbo 496 bytes read in 2 ms (242.2 KiB/s) Applying kernel provided DT overlay sun50i-a64-i2c1.dtbo 1039 bytes read in 2 ms (506.8 KiB/s) Applying kernel provided DT overlay sun50i-a64-spi-add-cs1.dtbo 784 bytes read in 2 ms (382.8 KiB/s) Applying kernel provided DT overlay sun50i-a64-spi-spidev.dtbo 777 bytes read in 2 ms (378.9 KiB/s) Applying kernel provided DT overlay sun50i-a64-w1-gpio.dtbo 3795 bytes read in 2 ms (1.8 MiB/s) Applying kernel provided DT fixup script (sun50i-a64-fixup.scr) ## Executing script at 44000000 tmp_bank=D tmp_pin=4 5416592 bytes read in 265 ms (19.5 MiB/s) 14311432 bytes read in 698 ms (19.6 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 5416528 Bytes = 5.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49ad5000, end 49fff650 ... OK Loading Device Tree to 0000000049a64000, end 0000000049ad4fff ... OK Starting kernel ...
  24. Ok removed it from the /etc/modules-load.d/modules.conf but it didnt change anything.. root@bananapim64:~ # dmesg | grep w1 [ 5.336416] w1-gpio onewire@0: gpio_request (pin) failed [ 5.336438] w1-gpio: probe of onewire@0 failed with error -22
  25. Hello There seems to be a problem with the latest kernel 4.19.53-sunxi64. I cannot configure the 1-wire support. In ArmbianEnv it is configured as: overlays= w1-gpio param_w1_pin=PD4 param_w1_pin_int_pullup=1 Than in /etc/modules-load.d/modules.conf I have: w1-gpio w1-therm with the dmesg | grep w1 I get: root@bananapim64:~ # dmesg | grep w1 [ 4.452698] w1-gpio onewire@0: gpio_request (pin) failed [ 4.452724] w1-gpio: probe of onewire@0 failed with error -22 root@bananapim64:~ # cat /sys/kernel/debug/gpio gpiochip1: GPIOs 0-255, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-120 ( |bananapi-m64:red:pwr) out hi gpio-142 ( |bananapi-m64:green:u) out lo gpio-143 ( |bananapi-m64:blue:us) out hi gpio-166 ( |cd ) in hi gpio-233 ( |usb0_id_det ) in hi IRQ gpio-234 ( |ads7846_pendown ) in lo IRQ What could be the problem??