• Content Count

  • Joined

  • Last visited

About lordofduct

  • Rank

Recent Profile Visitors

866 profile views
  1. yeah, if I modprobe matrix-pwm, after enabling it in the fex file, I get /dev/pwm. But the source code still doesn't work. When it attempts to set the pwm using ioctl (from libc), it fails. Which is what led me to try sunxi-pwm.
  2. So yeah, I got the fex to enable pwm1 on pin 6 (not sure where on the board pwm0 is, but it's not on the gpio header). Still didn't work though, in the code when 'ioctl' is called to actually set the frequency, it fails. Anyways... off to other things. ... I was able to get something in /sys/class for pwm. By adding the module 'pwm-sunxi', while having pwm configured in the fex: modprobe pwm-sunxi I am able to find a grouping /sys/class/sunxi_pwm, but unfortunately the structure of this doesn't match anything like what I expect... heck, the name alone isn't what I expe
  3. I checked out matrix, and it says /dev/pwm doesn't exist... which it doesn't. Which leads me back to the turning it on in the fex... I'll dig into that some more.
  4. Well I haven't resolved my issue of not being able to access /dev/mem. But I got around it by using /sys/class/gpio. I wrote up my own code to drive the gpio through this interface using C# (my preferred language): This has got me up and running turning gpio pins on or off. Next I want to get pwm working, I've read around that there is a /sys/class/pwm, but this doesn't exist on my machine. I also noticed its through this that the python library from my previous post attempts to access it as well. I looked in the fex and noticed some entries relating to pwm:
  5. So I have a nanopi m1 and a neo. I'm running Ubuntu Xenial on them: https://www.armbian.com/nanopi-neo/ I'm attempting to access the gpio, when I attempt to echo to /sys/class/gpio/export I get permission denied (sudo or not, even if logged in as root). I've also found this library for python to handle gpio on the nanopi: https://github.com/jrspruitt/FriendlyARM_Python_GPIO But when I use it, it says: as root root@nanopineo:/home/admin# python test.py Traceback (most recent call last): File "test.py", line 7, in <module> gpio.gpio_init(16, 1) File "bui
  6. Ah, darn... admin@nanopim1:~$ dmesg | grep OV5640 [ 9.081894] [OV5640]error at sensor_detect [ 9.081900] [OV5640]chip found is not an target chip. OK, so chip not a target chip? Does this mean that the camera isn't ov5640??? admin@nanopim1:~$ dmesg | grep ov5640 [ 9.001216] [VFE]Find sensor name is "ov5640", i2c address is 78, type is "YUV" ! [ 9.001226] [VFE]Sub device register "ov5640" i2c_addr = 0x78 start! [ 9.128089] [VFE]Sub device register "ov5640" failed! OK, so it failed. admin@nanopim1:~$ dmesg | grep VFE [ 8.816405] [VFE]cci pr
  7. Thanks @lex for confirming those are the steps. So I went and found a fex file on the forums that looked like it might work: [csi0] vip_used = 1 vip_mode = 0 vip_dev_qty = 1 vip_define_sensor_list = 0 vip_csi_pck = port:PE00<2><default><default><default> vip_csi_mck = port:PE01<2><default><default><default> vip_csi_hsync = port:PE02<2><default><default><default> vip_csi_vsync = port:PE03<2><defa
  8. Hello all, just joined the forum since this is my first time using Armbian. So I got a NanoPi M1 and the dvp cam500b. From what I understand this camera uses the omnivision ov5640. I am having trouble getting this thing recognized in armbian. I get /dev/video0 to be listed by adding it to /etc/modules, but if I go to access it with any software it reports back 'no such device' or to the similar effect (this includes mjpg-streamer, fswebcam, ffmpeg). Researching around I find many forum posts of people saying one must modify the 'fex' file... to which I found out this is the decompiled v