Jump to content

maxman190

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by maxman190

  1. The A83T used on the M3 has an internal temperature sensor and I provide RPi-Monitor templates to monitor this stuff (see above).

     

    Regarding useable OS images from 'them': well, they suck more or less and you won't see Armbian support anytime soon for any device based on A83T. Why don't you try to get support from the vendor? Why don't you push them to provide something more useable? Why do all the M3 users accept that they bought an expensive paperweight and do not complain publicly so others could learn to avoid the so called 'Banana Pi' M2/M3?

    I would try to push them, but I see you and a few other members trying to do that as well on their website, but it didn't seem to do anything. You guys have more credibility and more knowledge than I do, so I figured that it would be pointless for me to complain.

  2. Another funny update on the M3 (and the M2 as well, this SBC also suffers from lack of support). The reason you can not use 1-Wire sensors on both Banana Pi M2 and M3 is that the vendor has no clue how to setup settings correctly. Banana Pi M2 and M3 are the only SBCs on this planet where you can't use popular thermal sensors like DS18B20 since the vendor's software support sucks.

     

    So what to do? You've to fix the problem yourself (it's easy, all that's missing is CONFIG_W1 and also CONFIG_W1_SUNXI + the driver but 'Team BPi' simply forgot to include this driver).

     

    Now a user created a patch https://github.com/BPI-SINOVOIP/BPI-M2-bsp/pull/5 ( based on earlier work for the A20) for the M2 that will work also with the M3. And what is 'Team BPi' doing? Instead of merging the pull request and immediately providing a fix to their customers, they simply ignore it. As usual. They don't give a sh*t whether you can use an SBC as an SBC or as a paperweight. But since their customers also don't care it's just another example for a great business model.

    Ugh... Since I already the board and I can't return it, I tried to make the best of it.... I tried all their images for M3, for some reason I can't detect any temperature on anything on the board, does M3 not capable of sensing the temperature? Since I'm new to this whole Linux thing, what do you do with the config files that is in the Github? Do you compile it yourself to make your own Linux image? It's fine if you don't have the time to give me the details, but I'd appreciate if you can point me the right direction, like what to google and stuff.

  3. Lol, so I decided to just mess around with the board using my multimeter.... I touched the negative probe to GPIO pin 2 and touched the positive probe to pin 6, the probes were like 2-4mm thick, so I accidentally touched the positive probe (while still touching pin 6) to either pin 5 or pin 8 or maybe all 3 together, then the SMD ferrite bead (https://www.dropbox.com/s/9pssmriob7prlnz/20151214_180731.jpg?dl=0) to the left of micro usb/dc power, sparked and the board won't turn on anymore...

     

    Is it possible that only the ferrite bead burnt and nothing else? I think I can replace it... but even then, the schematics sinovoip posted doesn't have the values listed on the components...

  4. :((( I bought this before doing research on it... I encountered everything you brought up... Is it possible to burn the linux image onto emmc? Also, whenever I use the Arch Linux image that was recently released, my M3 keeps locking up and crashing. The watchdog detecting lockup on CPU 0 or something...

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines