Ribster

  • Posts

    8
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Ribster reacted to tkaiser in BPi R16   
    Just FYI: the first interesting Banana board since ages: BPi R16 based on Allwinner's A33 SoC (R16 is just a relabeled A33 with a different Allwinner business unit being responsible for).
     

     
    For R16 exists a horribly outdated 'SDK' made by Allwinner's BU5: https://github.com/tinalinux/linux-3.4 (relies on unpatched kernel 3.4.39 which might contain more security flaws than features in the meantime. Their tinalinux approach combines this with an outdated Android 4.4 and somehow also a smelly OpenWRT version for reasons unknown to me. Surprisingly they also rely on their own proprietary LiveSuit image format no one on this planet outside of Allwinner wants to use).
     
    But the good news is: There are some mainline kernel branches with patches for A33 around that are in a pretty good shape eg. https://github.com/Icenowy/linux/tree/a33-cedrus-pr (seems Icenowy also managed to get Allwinner video engine working with mainline kernel already). So most probably no need to fiddle around with Allwinner's tinalinux stuff or SinoVoip OS images at all
     
    For me personally such an R16 IoT board has one big advantage over el cheapo H2+/H3 boards: PMIC support and therefore the ability to use/charge a connected battery (and also control voltage/useage and act on accordingly).
     
    Let's see whether SinoVoip manages to introduce the usual design flaws (eg. not being able to use an external aerial unless you desolder components on the board), when they release (hopefully accurate) schematics, how the battery connector looks like and whether this device will be priced competitively.
     
    Edit: According to the above pictures the same DRAM as on NanoPi Air is used (512MiB K4B4G1646Q-BCK0 DDR3) and at least not the ultra-slow eMMC they used on every other board since BPi M2+ (there they use KLM8G1WEMB-B031 -- can't read the exact writing on the picture above)
     
    Edit 2: According to linux-sunxi IRC Ampak AP6212 is used on the board (WiFi/BT combo like on nearly all other Banana boards and also NanoPi Air or the upcoming OPi Zero 2 -- so we then have 3 flat and lightweight boards with eMMC, camera connector and the same Wi-Fi/BT combination but from 3 different companies using 3 different Allwinner SoCs. Funny)
  2. Like
    Ribster reacted to mariuszb in Hdmi 1280 x 800 display   
    I tested already 1280x800 resolution and works properly with my previous calculations.   {HDMI1280x800_60, 0,83460000, 0, 1280, 800, 1680, 200, 64, 136, 828, 24, 1, 3, 1, 1, 0, 0, 0}, {{Video ID  , 4 , 0,    96,  5,   3,  3,  1,   1,  0, 0,  0, 144,  64, 136, 32, 28, 1,  1 }}, PLL_VIDEO 334 In addition, I did the calculation in a different location and width of sync pulses (another school  ) - it also works properly.   {HDMI1280x800_60, 0,83910000, 0, 1280, 800, 1656, 32, 32, 312, 841, 17, 16, 8, 1, 1, 0, 0, 0}, {{Video ID  ,  4 ,   0,  96,     5,   8,     3,  1,   16, 0, 1,   0,  120,    64,    56, 32,  41,  1,  1 }}, PLL_VIDEO 336 Personally, I am use this second setting.   Can you add it to Armbian?  
  3. Like
    Ribster reacted to martinayotte in Orange Pi Zero, Python GPIO Library   
    Right, you don't need my DT overlay shown in the spoiler if you are not using spidev in userspace.
    In fact, you just need to replace in the main DT the status "disabled" by "okay".
    For accessing the SPI itself in kernel-space, I'm not fluent with that, but you can take a look at other drivers present in the mainline.
  4. Like
    Ribster reacted to martinayotte in Orange Pi Zero, Python GPIO Library   
    In Mainline, the devices are defined my Device-Tree loaded by the kernel.
    There is plenty of docs/tutorial that you can find on Google about DT.
    Some for different platforms, but it doesn't matter if it to read and learn about DT.
     
    For PiZero specific case, the SPIs are already defined in DT, but not visible in userspace until you add an SPIDEV overlay like the following one.
    The /dev/spidev0.0 will appear and could be used by python library orangepi_PC_gpio_pyH3.
    The /dev/spidev1.0 won't appear unless you disable led_status and uart3 since they are sharing the same pins.
     
     
     
  5. Like
    Ribster reacted to martinayotte in Orange Pi Zero Kernel SPI & GPIO   
    Right ! That is the lib to use for python, but internals C function can also be copied/pasted to any C program.
  6. Like
    Ribster reacted to Brian Greul in Sharing info for others on the Orange Pi Zero (Mac Prefix and PinMap)   
    The MAC address of your wifi port on your Orange Pi Zero probably starts with C8:27:A7:F9:xx:xx 
    I obsfucated the last 4 digits of mine.
     
    The Ethernet Port MAC starts with : de:ae:b8:d7:xx:xx
     
    I needed this when I was trying to find the device on my network to SSH in.
     
    root/1234
     
    It showed up on my network as a reasonably "fast" device with 0ms lag.  I'm running a Cat 6 network with a gigabit switch.
     
    A nice pinout that Linux34 from Orange Pi posted.

     
     
     
  7. Like
    Ribster reacted to Mohammad Mubin in ILi9341 TFT Video   
    Hi everyone i made a video for the ILI9341 2.4" tft Module check it out