• Content Count

  • Joined

  • Last visited

About shaddow501

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well since Orange PI Win uses the same chip, and since it is no secret that china copies almost everything, I wont be surprised if Banana A64 and Orange PI Win uses the exact hardware configuration, if one is EOL most likely that they both be moving to the exact next revision of the chips. (DDR & Wifi/BT) Best way is to compare between them.
  2. Hello The problem I think it is that the manufacturer updated the hardware (it is now V1.2) Here is the official answer; our products and systems need to be updated, so every batch of hardware and software is updated. The products produced this year have updated DDR materials, so I think This is one reason. In addition, since armbian is not our official system, I have asked for technical help, and they have no way to solve this problem. We will remind on the official website that WiFi is unavailable. I think it is the problem of the crashes.
  3. 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..
  4. 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)
  5. I have a another question. Do you happen to know how to enable the DSI interface to work with DSI LCD?
  6. 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.
  7. 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....
  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...