• Content Count

  • Joined

  • Last visited

About winfried

  • Rank

Profile Information

  • Gender
  • Location
  • Interests
  1. It tried on /usr/src/linux-headers-5.1.12-sunxi for olinuxino A20: same problem (/bin/sh: 1: scripts/mod/modpost: not found) when I compiled modpost additionaly in headers: sudo make M=scripts/mod I could compile my module, so somewhere mod is missing in the "make scripts" even it is listed as subdir ... anyhow it works, but it is not a fix..
  2. Thanks, I tried now flash with orginal Olimex sdcard image (kernel 3.4.103) [1] and used the nandinstall script there and it worked. I will look further in next days maybe to format nand properly for armbian to get the right "mbr magic" und update this comment to this topic [1]
  3. On an Olimex Lime2 NAND 4GB I installed Armbian legacy debian jessie server on an sd-card. "lime2 3.4.112-sun7i #10 SMP PREEMPT Sun Oct 23 15:49:51 CEST 2016 armv7l" I followed: and after reboot without card, it did not boot: (from serial console) [...] [ 0.366] flash init finish [ 0.367] mbr magic is not correct [...] Anyhow I didnt understand as prerequisits in description: "pre-installed system on NAND (stock Android or other Linux)" I erased the nand before, since I used it otherwise: dd if=/dev/zero of=/dev/nand bs=512 count=16 Question: Is my NAND broken or must I install some mbr before in the nand ? Any advice ? mfg winfried Appendix: complete boot output: HELLO! BOOT0 is starting! boot0 version : 2.0.0� read dram para. dram driver version: 1.15 dram size =1024MB 0x00018608 super_standby_flag = 0 Succeed in opening nand flash. block from 2 to 6 deal block 2 Succeed in reading Boot1 file head. The size of Boot1 is 0x00068000. The file stored in 0x00000000 of block 2 is perfect. Check is correct. Ready to disable icache. Succeed in loading Boot1. Jump to Boot1. [ 0.159] boot1 version : 2.0.0 [ 0.159] script installed early ok [ 0.160] pmu type = 3 [ 0.265] bat vol = 942 mv [ 0.278] axi:ahb:apb=4:2:2 [ 0.278] set dcdc2=1400mv, clock=912M successed [ 0.281] key [ 0.293] no key found [ 0.293] flash init start [ 0.293] NB1 : enter NFB_Init [ 0.296] NB1 : enter phy init [ 0.299] [NAND] nand driver(A20) version: 0x0x00000002, 0x0x00000012, data: 0x426fff64 1111692733 [ 0.308] set retry default value: [ 0.311] 0x00000020[ 0.314] 0x00000020[ 0.316] 0x00000073[ 0.318] 0x000000c1[ 0.321] [ 0.322] get the good blk ratio from hwscan : 870 [ 0.327] NB1 : nand phy init ok [ 0.366] NB1 : init ok [ 0.366] flash init finish [ 0.367] mbr magic is not correct [ 0.370] fs init fail [ 0.372] fs init fail, jump to fel [ 0.376] set retry default value: [ 0.380] 0x00000020[ 0.382] 0x00000020[ 0.384] 0x00000073[ 0.386] 0x000000c1[ 0.389] [ 0.390] [NAND]dumy read,chip 0x00000000
  4. UPDATE - CAN Bus didnt work: It always hung after some seconds of receiving until we found that it was a electrical problem, a non isolated CAN-Bus on another voltage ground. Unfortunately we could not finish the tests before return of the vehicle, therefore I cannot confirm the working patch until now. PS: I will do another try on the CAN-Bus of my Zero E-motorcycle in spring and report.
  5. Thanks again. This brings me to another question before I go testing tomorrow: - How to name the packages, for example linux-image ? If having the same name as the distribution on update it will be overwritten easily. I want to distribute the kernel debian packages to be installed in the nodes and updated if I update them on server. Since I apply some patches I also would add this info like "linux-image-sun7i-3.4.112-rt-can_5.20_armhf.deb" or for koco modules. "linux-image-sun7i-koco_5.20_armhf.deb" Where can I change naming and version numbers of generated debian packages ?
  6. I thought so, but then I saw userpatches/overlay... It is mentioned it is for the image, but I do not really understand how I can use it, is there an example ? so I cannot put additional driver source in it. Ok, I will do so and test beginning next week, when I have access to a CAN bus again and post it here ? Thanks for the answers.
  7. Hello, I am not very experienced on the Armbian development and want to add a kernel driver to the legacy kernel using the development tool, but did not grasp the best practice to add the kernel source reading some forum posts and docs. As a start lets add the sunxi-can driver for the Olimex CAN-A20 interface for legacy kernel for Olimex lime2 A20 board like described in the Wiki at Olimex: I did: a) an virtual box on my machine and can successfully build kernel packages and apply user-patches enable some patches like the copy /patch/kernel/sun7i-default/0015-sunxi-codec_LL.patch.disabled to user-patches/... and build new kernel packages for my board and tested it. To add the driver a) cloned the driver source: git clone So the first questions for best practice: 1) where to place the source so it is not removed on updates ? 2) How to change linux-sunxi/drivers/net/can/Kconfig and linux-sunxi/drivers/net/can/Makefile ? 3) How to change the linux config without everytime run the menuconfig and being able to update new versions of config file if new kernel arrives ? mfg winfried