shaddow501

Members
  • Content Count

    31
  • 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. I have a another question. Do you happen to know how to enable the DSI interface to work with DSI LCD?
  2. 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.
  3. 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....
  4. git clone https://github.com/notro/fbtft_tools/
  5. git clone https://github.com/notro/fbtft_tools/
  6. 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.
  7. 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/vdso.lds', needed by 'arch/arm64/kernel/vdso/vdso.so.dbg'. 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?
  8. like this: sudo ./compile.sh BOARD=bananapim64 BRANCH=dev KERNEL_ONLY=yes KERNEL_CONFIGURE=no EXPERT=yes
  9. the only way it let me go to the dev is by using the command. since no menu have given me the selection sudo ./compile.sh BOARD=bananapim64 BRANCH=dev KERNEL_ONLY=yes KERNEL_CONFIGURE=no
  10. Could it be that you have special developer rights that you do get this menu? I dont know, I just dont get it here!!
  11. 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...
  12. 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 ?
  13. You are right, but it doesnt let me choose, try for yourself, when you select bannapim64 you dont have any choosing....
  14. When i go with sudo ./compile.sh 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 ]
  15. Cool I really would like to but when I do build (Armbian build => sudo complie.sh) 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