• Content Count

  • Joined

  • Last visited

  1. Looking at the pinout table Pin 7 and PIN26, also the schematic, PWM is PA6 For this board, the overlay, is saying PWM is PA5, is it PA5? (sun50i-h5=pwm.dts) For SPI_1, CS_1 is PA10, but the table does not list a PA10, is that pin 26? (sun50i-h5-spi-add-cs1.dts)
  2. Is the work being done based on the code drop from Allwinner
  3. Would it just easier to use serial over USB and use the DFU to upload firmware?
  4. QuadCopter - 2 basic designs (1) is the flight controller connected to an I/O processor for PWM IN/OUT (2) Flight supervisor.
  5. The SPI select is driven by software, ie. drivers/spi.c not hardware. Looking at spi.c spi_transfer_one_message assert CS setup/clear upper level call backs call into SPI driver sun6i_spi_transfer_one clear ISR callbacks etc setup SPI chip etc start the transfer. So, even if the SPI transfer rate is increased, the about of time from CS is asserted to the first SPI data transfer should be constant (i.e the time it takes to execute the code)
  6. Here is a how-to for servos, yes it is for micro-python, but it provides info on how to set it up and values.
  7. Might what to review the patches for the zero:!topic/linux-sunxi/mdrG_TVmzUE I was doing the same thing: - Used patches from SUNXI - added Ethernet, and CPUX regulator support For u-boot I'm using orangePI-ONE defconfig. IMHO, The Zero is more like the orangePI-ONE then the OrangePI-PC FYI: I'm using buildroot.
  8. I've updated sun8i-h2-plus-orangepi-zero.dts (4.9x Linux) to include cpu thermal trip points and included the THS driver. Able read the temp, /sys/class/thermal/thermal_zone0/temp reports around 33794. How to test to see if CPU throttling is working?
  9. Well, I'm having issues as well with SPI, the first byte sent is "glitched" it is similar to was was posted before. he first byte should be 0x71
  10. I'm using applying the following patch - Ethernet works - I2C works - Have not tested SPI, in progress. I've added spi static const struct of_device_id spidev_dt_ids[] = { { .compatible = "rohm,dh2228fv" }, { .compatible = "lineartechnology,ltc2488" }, { .compatible = "spidev" }, //TCM:FIX to spidev to get around creating a overlay. I'm still clueless why kernel developers have not made this modification.
  11. What is required to get the OV5640 working on a orangePI PC? Is it possible to use the latest (sunxi) 4.8.x ?
  12. Any success getting SPI to work with mainline i.e 4.7rc?
  13. @martinayotte, is it possible to get your SPI/I2C patches? Are there any patches yet for CPU/therm throttling for 4.5.0+? Is it possible just to take these and merge them?