Jump to content

hojnikb

Members
  • Posts

    315
  • Joined

  • Last visited

Posts posted by hojnikb

  1. Does 2G-IOT have any sort of reverse polarity protection ?

     

    Looks like i've accidently reversed it when hooking up an UPS board and now the board is seemingly dead. Is there a fuse or a diode that i can replace or is it straight to trash ?

  2. On 5/27/2017 at 6:08 PM, zador.blood.stained said:

    It boots on Samsung Evo 16GB and Samsung Evo Plus 16GB for me. Judging by console messages RDA BootROM is very sensitive to the card response timings to different commands, so it's not certain that it will or will not always work on all cards of certain type, brand and capacity.

     

    maybe this could be fixed by putting  uboot (or some other compatible loader) to nand and instruct it to continue booting off sd card.

  3. 2 hours ago, malvcr said:

    I put this in the Orange Pi forum ... but just for reference here.

     

    The machine doesn't boot properly with 16GB SD cards because of lack of power (it is not because the card could be damaged or something similar).  So, 8G class 10 must be used instead (it seems that as larger the card, bigger the consumption).  What I don't know is if this is a hardware design limitation or something related with the 1.6 version internal "bios".  The only issue with this is that 8G is going out of the market very quickly (local stores around here are bypassing that size for the 16GB) ... so it is necessary to find them online and with shipping and everything they could cost more than the 2G-IOT.

     

    As I have no idea about any compatible LCD for the 2G-IOT, I will find a GPIO based one (it is supposed to be Raspberry Pi compatible ... let's see what happens ...).

     

    Thats pretty sad. I've also encountered this, but luckily still had 8GB card lying around. Hopefully xunlong makes a rev2 with this and battery support fixed.

  4. I'd suggest using chromium:armhf on both arm and arm64 builds, as there really is no reason to use arm64 build of chromium, because it's more ram hungry and not faster on our ram limited boards. I've been using armhf version on PC2 for some time now and works just fine. Needs a tweak to get it working though.

  5. 7 hours ago, pfeerick said:

    It looks like there may also be an issue with the fact that the battery has a dedicated battery protection circuit, which will isolate itself from the outside world until the undervoltage lockout has been lifted... and since the AXP can't see it... you get a chicken-egg situation happening. Same stupid situation as the TP5100 lipo charge boards with protection circuitry... it needs power before it works, but when you first connect it stays off, so you need to bypass that protection to 'arm' it (hence why all the 'buy-your-own-battery' powerbanks all have a reset pinhole/switch in order to power them on when you first insert the batteries).

     

    34707942996_271826e429_n.jpg

     

    By rights, you can cheat if you didn't have a charger or variable power supply handy, and hook up a pair of AA batteries (i.e. 3v) to the lithium battery for 5-10 seconds, and that would have given it the (gentle) kick it needed to dis-arm the low-voltage cuttoff. Obviously you need to get the polarity right, otherwise you're going to really hope you used thin wires so you can feel them heat up or smoke if you get it back to front! 

     

     

     

    How about just lifting minimum voltage in AXP to above that of protection circuit ? This way, axp will cut off battery before internal protection can kick in. Or if you're brave enough, just remove protection from the battery all together and let axp do it's thing :)

  6. Any ideas how to enable battery support ?

     

    I soldered a 18650 cell to +/- pads on the board, but it doesn't power up. Plugging microusb boots the board, but it dies instantly when you plug it out.

    Am i missing something ?

  7. 1 minute ago, zador.blood.stained said:

    It's either 1-4 up, 5-8 down or the opposite way (1-4 down 5-8 up). AFAIK the former is OTG and the latter is host.

     

    thank you, will give it a try. :P

  8. Anyone knows how to correctly set up dip switches to have a working usb host ?

     

    I'm getting power to my usb, but isn't detected by lsusb (running unofficial armbian at the moment)

  9. 5 minutes ago, zador.blood.stained said:

    As noted previously in this thread, default baud rate for the BootROM, Andriod images and experimental Armbian images is 921600. Xunlong Linux image uses 115200 AFAIK, but you'll get some garbage from BootROM and u-boot before kernel switches to 115200.

    Thank you, this did the trick !

    This should be stickied somewhere :D

     

    Now, if someone would figure out how to flash "armbian" image to nand (and strip it to fit nand). 

  10. Any tips on how to connect serial ?

    I tried connecting like it's labeled on the board, but i'm getting a bunch of garbage in putty. Currently booting from sd card.

     

    What serial settings should i use ?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines