• Content count

  • Joined

  • Last visited

About chwe

  • Rank
    Elite member

Profile Information

  • Location
  1. Does it spin-up? How do you power your OPi PC2 (type of PSU)?
  2. Banana Pi randomly not working

    Were the discs connected during the test? Did you 'force' some disc activity to let them spin up? I know you use some sort of power dock, but just to make sure, there's no voltage drop during spin-up of your drives...
  3. How do you power your HDD when connecting to the OPi PC2? If you power it through the SBC ist most probably a power issue...
  4. Needs also a bit more documentation. It needs a little bit more explanation. Olimex boards have a lot of gpio possibilities and you can address all of them (e.g gpio1, gpio2, lcd etc.). Since most others don't have more pinheaders I named it GPIO (do have a difference capital/small letters to the Olimex boards). Or when using the nanopi duo J1 and J2 (according to the datasheet) when you install the lib with minishield it's also called 'GPIO'. There's also a pin-header called LED (normally LEDp1 = POWER_LED, mostly the red one and LEDp2 = STATUS_LED) and a pin-header "BUTTON" (BUTTONp1 = BUTTON_1, but not tested yet). It should also be possible to use the GPIOs delivered by the CSI pin-header: This should give 14 GPIOs + I2C (TWI2) more.... I didn't implement them in the library now, cause it would need adjustments in the fex file for the legacy kernel, and I've no clue whats needed on mainline to use them as normal GPIOs. Maybe @Igor or @zador.blood.stained can comment this? If you're not sure about the naming for your board, just consult pyGPIO/pyGPIO/gpio/mapping/your_board_name.h to get some additional information (I hope I find time to write this stuff down in a small documentation).
  5. Award for implementing Banana Pi M3 into armbian

    To quote @Igor Me neither, but it's never too late to learn something new... Just as an example (for sure easier than your project): In the meantime, I learned how to maintain websites with Django CMS. And my background isn't in system administration nor web-design (I'm in science.. ).
  6. Forum upgrade

    from my french lessons years ago ' la pomme de terre' and potato is also feminine, it's named LePotato but La would make much more sense... fun fact: code button disappears (chrome) when using fullscreen for PMs but it appears when I shrink my browser window (1366x768, yeah I have a shitty screen on my laptop.. )
  7. The pyA20 gpio library is quite famous when people start to play with gpios , spi or i2c on sunxi boards but mapping needs often adjustments to work on your own board. This situation is not really friendly for 'beginners'. pyGPIO should help to make armbian a little bit more 'IoT friendly'. I didn't touch the 'backbone' of pyA20, so the syntax should be similar to its original (except pinname when using port instead of connector). How can I use this library: Cause all of this boards have (more or less) the same pinheader (sometimes other pins are deployed on the pinheader) pyGPIO tries to unify the mappings, so that code can be shared and deployed on all boards without touching the code. The mapping follows the pin naming of the RaspberryPi (it's not because I think their naming is perfect, but it should be the easiest way to port code from the 'RPi world' to Armbian. What is done: -Initial support for: OrangePi Zero/PcPlus/Lite/Plus2E NanoPi Duo(with and without Minishield)/Neo Olimex Lime/Lime2/Micro (pins are not renamed PG10,PG11 etc. instead of GPIO2, GPIO3 etc. cause those boards doesn't have a 'RPi Pinheader' Templates for 24,26 and 40 'RPi compatible' pin header -Board detection (when using Armbian) to check if your board is supported -Manual assignment when your board is not supported (yet) or automatic board detection fails What is not done: Testing testing testing! Documentation Meaningful examples (still the originals from olimex which wouldn't work anymore) What do you need to test the Library: You need python-dev and the Library which you'll find on my GitHub page. The installation should be easy, just follow the instructions... sudo apt-get install python-dev git clone cd pyGPIO sudo python install Testing is the part where I need help. I don't have most of the boards which are supported (only OPi0 and OPi Pc Plus). I tested I2C and GPIO on the OPi0, for all the rest, I need you as testers, bug hunters, and feedback. Here are two short python snippets which should do the exact same thing (once with connector): import os, sys if not os.getegid() == 0: sys.exit('start script as root') from pyGPIO.gpio import gpio, connector from time import sleep gpio.init() gpio.setcfg(connector.GPIOp7, 1) #pin 7 as output n = 0 while n < 5: gpio.output(connector.GPIOp7, 1) sleep(1) gpio.output(connector.GPIOp7, 0) sleep(1) n +=1 sys.exit('finished ;-)') and once with port: import os, sys if not os.getegid() == 0: sys.exit('start script as root') from pyGPIO.gpio import gpio, port from time import sleep gpio.init() gpio.setcfg(port.GPIO4, 1) #gpio4 as output n = 0 while n < 5: gpio.output(port.GPIO4, 1) sleep(1) gpio.output(port.GPIO4, 0) sleep(1) n +=1 sys.exit('finished ;-)') Annotation: When using NanoPi Duo you've to possibilities with or without Minishield. Pin name is the same on both possibilities but when using port but pin numbering when using connector: Minishield: 3.3V |1·| 5V GPIO2 I2C0_SDA |3·| 5V GPIO3 I2C_SCL |5·| GND GPIO4 |··| GPIO14 UART1_TX GND |··| GPIO15 UART1_RX GPIO17 SPI1_MOSI |··| GPIO18 GPIO27 SPI1_MISO |··| GND GPIO22 SPI1_CLK |··| GPIO23 SPI1_CS 3.3V |··| NC (on mini shield) Without (e.g. connector.J1p7 or connector.J2p5) : J1 J2 (UART0_RX) |1| microUSB |1| 5V (UART0_TX) |2| |·| 5V GND |3| |·| 3.3V GPIO3 (TWI_SCL) |4| |·| GND GPIO2 (TWI_SDA) |5| |·| GPIO4 (IR_RX) GPIO23 (SPI1_CS) |6| |·| GPIO18 (IOG11) GPIO22 (SPI1_CLK) |7| |·| DM3 D- GPIO27 (SPI1_MISO) |·| |·| DM3 D+ GPIO17 (SPI1_MOSI) |·| |·| DM2 D- GPIO15(UART1_RX) |·| |·| DM2 D+ GPIO14 (UART1_TX) |·| |·| RDN (CVBS) |·| |·| RDP (LINEOUT_L) |·| |·| TXN (LINEOUT_R) |·| |·| TXP (MICP) |·| |·| LED-LINK (MICN) |·| microSD |·| LED-SPD Buttons (bigger orange pi boards) are mapped, but I didn't test if it works (mapping here, if somebody is interested in testing them, see mapping.h of your board): {"BUTTON", { { "BUTTON", SUNXI_GPL(4), 1 }, { { 0, 0, 0} }, } },
  8. Banana Pi Zero

    it's everything there... just open your eyes... And I don't use it, I was only interested in the script.bin file... It boots, wifi 'works' but without an external antenna, it's not stable in an urban environment.
  9. Banana Pi Zero

    false.. it boots... ____ ____ _ __ __ ____ _____ | __ ) __ _ _ __ __ _ _ __ __ _ | _ \(_) | \/ |___ \ |__ /___ _ __ | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | | | |\/| | __) | / // _ \ '__| | |_) | (_| | | | | (_| | | | | (_| | | __/| | | | | |/ __/ / /| __/ | |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_| |_| |_| |_|_____| /____\___|_| ___ / _ \ | (_) | \___/ Welcome to ARMBIAN 5.34 user-built Debian GNU/Linux 8 (jessie) 3.4.113-sun8i System load: 4.33 1.66 0.61 Up time: 2 min Memory usage: 13 % of 494MB IP: CPU temp: 69°C Usage of /: 4% of 30G Seems that @Lion Wang figured out which two files he had to write to build an own 'armbian'...
  10. ArmbianIO API proposal

    I'm currently working on a fork of the pyA20 python library which is used quite often by people here when playing with GPIO, spi or i2c. It's not ready for public at the moment, but it will be soon. It has an automated board detection, pin naming is consistent so that you can use your python scripts on every supported board without renaming everything. And it has a 'board detection' mechanism to use the right pin mapping during the installation.
  11. will be in the future... (but I've to clean up and do some testings to make sure it works for the inexperienced + writing a "getting started guide" before announcing it public here - just need ~1 week to fix it). Why not mark it as .eos instead of .csc (I know it had never "full" support but it would make it clear that "nobody" works on it). It was also the reason I joined armbian... But it's sitting as paperweight somewhere on my desk.
  12. Forum upgrade

    seems to work now. Thanks to Igor!
  13. By reading this whole thread or using the search engines... By reading another thread....
  14. 5.34 release

    Build it on your own with armbians build script or 'apt-get update' followed by 'apt-get upgrade'
  15. Banana Pi Zero

    But BPi-M2+ has 'no voltage regulation' for CPU. Which makes it 'not useful'. Maybe you can fix this issue (and make an annotation in your documentation for this board) when you produce the next batch of this board?