Jaret Burkett

Members
  • Content Count

    6
  • Joined

  • Last visited

  1. I have spent the greater part of the day trying to get fbtft working on an ili9341 display on the nano pi neo with the legacy kernel. I have looked through the forum over and over and I cannot find out how the pins are numbered for fbtft. I got https://github.com/wertyzp/WiringNPand did a gpio readall and that gives me some pin numberings. I have tried both the pins from wPi and BCM. Neither work. I have done this many times on a raspberry pi, but cannot seem to get it to work on any of the H3 stuff. I saw in the forums that in the mainline kernel, there is a mathematical equation for pin numberings. I tried that as well, with no luck. I also tried giving the actual portpins (gpios=reset:PG8,dc:PG9) but that gave me an error. Is there a reference for pin numberings somewhere or am I doing something wrong. I am running the following to enable the module. sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:7,dc:13 speed=16000000 rotate=90 bgr=1 and testing with sudo SDL_VIDEODRIVER=fbcon SDL_FBDEV=/dev/fb8 mplayer -vo sdl -framedrop BigBuckBunny_320x180.mp4 Seems to run fine, and the display shows some blinks here and there. I am connected on the spi0 port. cs0 and reset:PG8,dc:PG9. What am I missing?
  2. I have this same issue. It is only on the hdmi console not ssh. I am trying to figure out what is causing it. I have been digging in the code all day. No luck so far.
  3. Thank you for this writeup. I have been gaining a lot of interest in these h3 boards since finding orange pi about a year ago. I learned more in the 5 min reading this that I have over the past year of looking over datasheets and experimenting with the Orange pi boards I have. I am really looking forward to the H3 getting mainlined.
  4. It was not really a value loss for me, agreed. But it was showing up there, and it was wrong, sooo... I had to fix it. OCD I guess. I have been putting together a pretty thorough customize-image.sh script to get it exactly the way I like. (adding wifi credential, changing hostname, adding a user, making adjustments to the terminal (the cursor was not showing up for me on hdmi), and of course installing custom packages.) I saw the ip address showed at login was wrong, so I just figured, while I was at it....
  5. 'hostname -I' spits out the correct local ip. This works as well. Both of you are awesome. hostname -I will probably work in most scenarios unless there are multiple network connections then it might spit out 2 different addresses, but that would be a rare case. Not sure how that will work. I'll just add grep to my solution for now as it would still only spit out 1 ip address in the rare case of there being 2.
  6. I have Armbian Jessie running on a Orange Pi Lite board and the login script is showing the local loopback ip (127.0.0.1). It appears to be doing this because /etc/update-motd.d/30-sysinfo calls ifconfig -a and pulls the first ip, which in this particular case, is the local loopback. For the orangepi-lite, i wrote the following command in customize_image.sh and it fixes the problem in this case. sudo sed -i "s/ifconfig -a/ifconfig wlan0/g" /etc/update-motd.d/30-sysinfo It basically changes the script to pull the ip address from wlan0 instead of whatever one it finds first This could also be called from the command line for the same effect instead of during compilation. However, for other boards using an ethernet adapter, this obviously wont work without changing wlan0 to eth0 or whatever network you have. I am not the best a bash script, and I am trying to find a way to edit the script in /etc/update-motd.d/30-sysinfo to display the first valid inet address instead of just the first inet address it finds. It is currently pulled like so. ip_address=$((ifconfig -a) | sed -n '/inet addr/s/.*addr.\([^ ]*\) .*/\1/p' | head -1) Anyone have any ideas?