pzw

Members
  • Content Count

    82
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by pzw

  1. pzw

    Orange Pi Zero +2 H5 - SD to eMMC

    There is a reason why Etcher is recommended by the creators of Armbian... It is for sure one of the (few) image writing utilities which actually verify after the writing... And yes, that is important, because corrupted SD cards can generate strange issues..... Good to hear it is working, but I would strongly recommend using Etcher to create the flash cards in the future, to ensure you are not dealing with a corrupted image on the card...
  2. pzw

    Orange Pi Zero +2 H5 - SD to eMMC

    Could it be that the image on the SD card you first used was corrupted? Did you use Etcher to create the SD card? Just curious... :-)
  3. pzw

    RockPro64

    Just one question.. why did you set the emmisivity so low? The temperature reading is heavily influenced by the setting... You can see the heat spread through.
  4. Might seem unrelated to you... But what kind of power supply are you using? You need a good power supply which can easily supply high currents (2A). A standard phone charger will not work reliably. Also the quality of the SD card is very important. Samsung EVO cards have always worked great for me. FYI My 2E has been running Armbian mainline for the last 12 weeks non-stop, with a EVO 32GB card and a 5A PSU, which is also supplying some other power hungry stuff, but has for sure enough capacity for the 2E... No problems at all stability wise!
  5. You use different clock speeds between the Arduino and the OPi. Depending on the wiring parasitic capacitance, this can make the difference.... Also... Are you running the Arduino on 5V or 3.3V? I guess 3.3V since the LDC1314 is a 3.3V device.. But just making sure :-) . What surprises me is by looking at the scope images is that it seems that the SDA line is held at 1/2Vcc . You say that doesn't change depending on the pull up resistor value. And that is strange. Because that means it is a state which is voltage controlled, and not the result of a "latched up" driver or something. Because if that would be the case, the voltage would move depending on the pull up resistor. The driving element will be having the same resistance in the latched state... Just thinking out loud now...
  6. If the "0" level is not hitting ground, it means that the current through the switching device (BJT/FET etc) is too high. A pullup of 4k7 seems to be ok, but I am not 100% sure if there is a pull up on the die of the CPU... So I would personally start with removing the pullups... Or... You have a bad ground connection. Can you take a picture of the wiring?
  7. pzw

    NanoPI Duo availability

    What changes will be implemented?
  8. pzw

    NanoPI Duo availability

    I tried asking FA, but didn't get a reply... I need a few for a project which has only space for that module... (got 36mm width to use....) Every week I try to check it, but so far no luck. I am wondering if it would help to just order a few so I might get them sooner..
  9. pzw

    TTL to RS232 possible?

    The converters which were "faked" were the FTDI based USB <--> RS232 converters... The converter you are using is based on a Sipex 3232 (or Maxim MAX3232) chip. Those are so super basic converters (you can buy them on a PCB ready to go for 15 cents each!) that they are not worthwhile faking... I bet you that the issue you are having is just a cold (bad) solder joint, like in the picture below... The sad part is that this is a picture of an advertisement of one of those 15 cent converters ads on Aliexpress.... In this case the converter would actually work, since the cap with the bad connection is the power supply bypass... So their "quality control" would not even notice it in a functional test..
  10. @TonyMac32 Thanks for verifying it :-) . It did strike me as odd if FA would have overlooked this termination requirement... Also I would have expected network throughput issues because of it, but I couldn't find reports about that... So that made it almost certain that the termination was happening on the die.
  11. I'm currently designing a PCB which will use a nanopi duo board. Unfortunately it is not in stock at the moment so I can't order one yet to verify some measurements. Can someone (@guidol or @larry bank maybe?) who has one sitting on their desk please give me the following info; - Distance between headers. Total width is 1" so I guessed 0.9"... Is this correct? - length of the pin headers. So I know how high it will sit on the PCB - total height of the pins + PCB - is there anything on the bottom PCB which is higher than the plastic on the pin headers? In other words; can I push the whole module all the way down to a PCB and then only have the thickness of the plastic of the pin headers? Or is something "sticking" out.. - How much does the heatsink add to the total thickness? (Or what is the thickness of the heatsink...) Thanks in advance for your help and time.
  12. @chwe In the schematics it was not clear if there is a termination circuit inside the CPU... The headache referred to the required implementation of a termination circuit in my design.
  13. Great news! Thanks @guidol. Saves me a headache.. haha .. I suspected that the termination might be in the h2+ ... Thanks for confirming this..
  14. Thanks @guidol! Last question. Was that powered up?
  15. No termination there...??
  16. @chwe the snippets in my post come from their diagram of the module... I noticed forgot to add the snippets from the shield.. I'll add it when I'm home again. But that will show no termination circuit...
  17. I have one more question, which I hope @guidol can help with too... If I read the datasheet of "magjacks" made by Pulse (that is a connector with built in transformers / magnetics) I see the following; There is clearly an set of resistors terminating the lines from the magjack to the PHY (in the H2+)... However on the diagrams there is nothing like this; So I hope that someone can measure for me the resistance between pin 13&14 on the headers of the DUO when it is not plugged into a shield. If there is a resistance of about 100ohms, it means that these resistors are built into the CPU... If not, then I need to add them. (And FriendlyArm might need to revise their shield or module ;-) ) Thanks in advance!
  18. Great! That's all the information I was looking for! Thanks a lot @guidol
  19. I don't think aplay supports MP3. Use mpg123 for that..
  20. Which header are you connecting to? Single row or double row? You need to connect between pin 7 or pin 8 and pin 2 on the single row header...
  21. Shorting the power line to ground through a (relative) high resistance flat cable... Check if there are no strands touching at the end of the flatcable (at the connector)
  22. pzw

    Real time clock DS3231

    Thanks for the script... I had to adapt it a little, since the script assumes there is a module installed with EEPROM... My question is why...? I have a module without EEPROM ( https://www.aliexpress.com/item/New-I2C-RTC-DS1307-High-Precision-RTC-Module-Real-Time-Clock-Module-for-Raspberry-Pi/32610072259.html ) and had to change line 95 into " if [ TRUE ]; then " , since the original line doesn't work for boards without EEPROM. (It tries to evaluate "--" as a number...) Maybe you want to adapt the script in such a way that it is not depending on the presence of the EEPROM... :-)
  23. Typo from my end, it's indeed 472.. let's blame the human using a phone to type! Haha As far as I know the lower the pull ups, the higher the current, the faster the (parasitic) capacitance of the bus is charged. This should allow higher data rates. Or am I mistaken here?
  24. Those 473 (4k7) resistors are the pull ups. They are very high for a 3.3v application.
  25. All, I am looking for a 7 - 10" TFT display with SPI connection, and with touchscreen preferably via I2C, for a project of mine. I want to use the display to show just a static HTML page, without any window manager etc. Pretty basic principle I think. Looking at the website of www.buydisplay.com I see a few options with regards to the controllers used. The main options are: - RA8875 - RA8876 - SSD1963 I can find online references to the RA8875 being supported by fbtft, but there is also a statement on the github page of fbtft that there will be no more development of fbtft ... Before pulling the trigger on a display, I would really appreciate feedback which controller is supported by fbtft/armbian... :-) Thanks for your time.. Paul