Daniel J.

  • Content Count

  • Joined

  • Last visited

About Daniel J.

  • Rank

Recent Profile Visitors

342 profile views
  1. Some experimentation on, privoxy installed, so while for a while I was suspecting some kind of "bad sectors" on the SD card after it failed twice on the exact same operation, it seems that probably isn't the case at all. I put the pigtail back, screwed on an antenna, booted in running from battery, and successfully connected to wifi... doing an apt-get update through wlan without issues. I don't know about power. I have no idea what counts as "undervolted" for this board. AFAIK the Allwinner 20 operates at 3.3V, and SD cards require 2.7V at a minimum... I seriously doubt even 4.5V would be a real undervolt condition, I mean the whole thing also runs off of a 3.7V Li-Ion battery... Spikes are a possibility of course, but I had the Fluke on it set to Peak Detect - that's analog peak detection, anything that causes things to malfunction in the board should be picked up... and the USB power input side never went below 5V...
  2. Like whaaaaaa... Okay, so long and frustrating story short, I have been having inexplicable stability issues on my Banana Pro. I have blamed the SD card, the power supply, the micro USB cable, but none of those leads seemed to actually lead anywhere. I connected up a Fluke multimeter to the SATA power output, set to peak min mode, to see if I get any undervolting... Nope, no problem there. I ran stress tests on my sd card on my computer - it was PERFECT. I was completely stumped... Until, after getting an Anker charging cable, and having a really good run with the new Armbian release - the system had been working for an hour without glitches, apt-get worked, I have upgraded and installed mc, ran "stress" for 20 minutes with no issues... I decided to try if Wifi will work... (I suspected it might not, as I was (still am) getting errors like these in dmesg: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) brcmf_p2p_create_p2pdev: timeout occurred brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5So following the "getting started" guide, I kicked off nmtui-connect, typed in my password for my 2.4 wifi ap, and then all hell broke loose. Everything fell apart right there and then, with error messages like these: mmc0: card stuck in programming state! mmc_erase: group start error -5, status 0x0 ext4fs: This should never happen etc.Well... that's when I looked at my board, neatly inside a Chinese enclosure, with a Chinese RP-SMA pigtail connected up to the WiFi, the cable actually touching the board... So I'm like "wait a minute right there, this can't be no coincidence"... So I removed the pigtail, re-flashed the memory card, rebooted, and for a while things were working. I upgraded the system, installed mc, tried connecting to the WiFi (didn't work without antenna), tried scanning for APs (detected the closer ones successfully)... I was pretty happy, posted here about how WiFi interference was probably the real culprit, left the battery to charge, with the system running "stress" constantly, checking in now and then on AC voltages in /sys/power (between 4.8V and 5.1V), and CPU temp (below 61C)... and then, after two hours, I decided to install Privoxy.. and right enough, during apt-get, the MC card errors again. Stuck in programming state, i/o error, error -5 sending status command, the whole deal. Again. Really I don't get it. EDIT 2: I booted up again, this time pulled off the battery to make sure that charging doesn't accidentally undervolt anything... Voltage safely above 5V according to /sys/power... Logged in again, sudo apt-get install privoxy again, mmc error again, remounted read-only, that's it. It's an EVO32 - the SD card people keep recommending as THE card to use with SBCs... According to testing it's 100% good...
  3. So I have a question... I'd like to manage Li-Ion battery operation on SBCs using the AXP209 power management chip (especially the Banana Pro, as that's what I have...) I soldered a connector to the battery terminals on my BPro for portable operation, and it would be nice to have some kind of solution to raise an alert at low battery charge (like via the onboard LEDs), and automatically call system shutdown at a certain level. Googling has shown that the AXP209 has an i2c interface for sensors, and there are a few scripts for reading battery status here: http://hardware-libre.fr/2014/11/banana-pi-axp209-battery-power-monitoring/ My current plan is to probably use a shell script set as a regular cron job to monitor the battery and act accordingly, which should do the job but feels a bit too duct-tape-ey. Has anyone done something like this? Any observations or ideas? What battery voltage should I use as a cutoff?
  4. Hm I'm wondering if it's a good idea at all to try and power an actual hdd through the BPro... I mean with 'lesser' cables we have issues even without one.
  5. Oh wow, I think you just solved my problem. Nah, I couldn't get it to work due to lack of appropriate cables lying around, but yes, this makes a lot of sense. I used some thin 2m data cable that apparently has AWG28/2c for power... I'm positive as the cpu throttles up, and there's a lot of mmc access, the voltage gets, well, underwhelming. I've actually come across this issue before with a mini-usb external hard drive... I once had this long thin mini-usb cable that I got for some keyboard or something lying around, and connected it up... and the drive motor would stop intermittently after a few minutes of operation. At first I thought the drive was dead, but no, the cable was shit - and that was powered from a regular notebook USB port. Anyway I guess I need to find a good 20AWG USB cable for this thing then...
  6. Actually, I'm having very similar problems. I have just checked the SD card with f3, and it's 100% perfect. (It's a Samsung EVO 32.) I use a white iPad charger as the power source, on paper it delivers 2.4A at 5V, so it SHOULD be good, but I'm starting to suspect it. Anyway... what happens is when I first boot, everything seems fine. However, when I do a system upgrade, it seems to want to upgrade the whole base system, including kernel modules, systemd, the whole thing... and it drops out mid-update. The Debian Jessie image errored out when upacking the kernel modules, saying that /usr is mounted read only... After that the whole system was borked. I tried the Ubuntu Xenial image next, it also wanted to upgrade the whole base system, and also died out during upgrade - I got an infinite repeat of low-level errors on the mmc device, since it cleared off the screen I didn't see yet which package was at fault. My first reaction was that maybe the SD card is counterfeit or defective, but it isn't, according to f3. So... what if the latest upgrade IS bad? I'm on a Banana Pro, and tried doing the apt-get update/upgrade first thing, before doing the other steps for changing device type - so maybe that's the problem? Dunno.