• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map






Everything posted by Technicavolous

  1. I thought I had edited that out ... total 'oops' moment ...
  2. I also like to reference the heartbeat but sometimes I've thought to have it code out a load level in morse ;]
  3. Does this update vary the heartbeat speed with load?
  4. Certainly looks to me to be a receiver only
  5. Thanks for this. dist-uprade and full-upgrade generally do nothing for quite a while now.
  6. YES it will be overwritten, but sometimes we can outsmart it if we use a temporary HDD ... There is probably a 'proper' way to do this, but I'm not that advanced. So try this - burn your new SD. Put in a different HDD temporary and boot (best if same size and model), use armbian-config to move data and then shutdown and replace the HDD. Some security may not allow this but it should work. On some units may have to edit UUID. From now on, after making your system and it is working, maybe duplicate the SD and tape it to the top of the unit? ;]
  7. Third link on XU4 and HC1,2 MC1 download pages are 404 not found. Building an archive for a workshop I'm doing next week and got the 404. No big deal, just wanted to make a note.
  8. Last night I noticed a slight difference in shutdowns. sudo shutdown -h now appears to shut down the board properly, the red light goes out. sudo halt leaves the red light on indefinitely. I have only recently got my build system working, and frankly this is the first time I've ever done that ... I just left everything default, selected the board, current kernel, no kernel config, os with desktop. I've not even opened any config files yet. My coding days were back in the MS C++ 7 era, predating VC ;] so it will take me a bit to get acclimated to the build system.
  9. @Sean Mathews if you make any progress please give a share! As for "how and how much," consider a monthly subscription. Some of us do that ;] Or Buy Igor a Beer or tank of gas. Or watch the wish list for something you'd like to contribute. ( @Igor is there still an Amazon wish list page somewhere??) @mboehmer I've rebooted my C4 over and over with several downloaded images, I've not had a single stick. Finally compiled my own image. Sticks every time on shutdown -r now. I have the Hardkernel eMMC 16GB, but also tried Sandisk 32GB U3. I am using lab power supplies ...
  10. I ignored the warning and everything seemed to go fine. I've successfully compiled two images for boards I'm familiar with. Now on the the C4 ;] Thanks again for your help!
  11. I was thinking that some of the syntax may lead you to discover your own solution. Looks like there has been some other discussion on the topic on this forum but I'm still exercising my forum search skills ;] I'm sure you've studied all the code in the reference but it looks like you can change the amount of memory and file size. I didn't think of that but why not see what happens? You DO have a test unit, don't you?? ;] You might want to see what rsync is doing, what the aXWv switches do ...
  12. Check out line 3 3. If you don't need detailed archived logging. You can protect your sdcard from hourly writes by telling log2ram to not write syslog and kern.log to disk. As a bonus at boot your ramdisk will not be filling with previous session's logs. on This Post Not quite what you're looking for but it might give a hint?
  13. Awesome thanks. Let me know what $$ you need. This looks right up my alley hihi I've been a bench tech all my (professional) life.
  14. After successfully building an image, I decided to build one for another board. Got a warning something like [warn] low disk space [5GB] I deleted the output directory and still states only 6 GB. I had given virtualbox 30 gb for this drive. What is the proper way to clean out the drive after a compile? Just ignore it, does it over write? Sorry if I missed this in the docs somewhere but I didn't find anything about it.
  15. How does one acquire these marvelous boards?
  16. Completed without error thank you again ... although I think I will allocate more resources to the VM it took all night hihi. I understand the next run will be much faster since it doesn't have to download and build those toolchains. Thanks again
  17. I submitted an application on the maintainer page for the C4.
  18. @Werner yes that got me past the gcc linaro error thank you!! it is doing more now, looks to be going fine now thank you again!
  19. I'm new to building the toolchain so sorry if I missed something basic. I installed Virtualbox greater than the version noted on the instructions page. ( Used the mini image at per above page. During the install I did not check any options for system software. Started the os and installed git using sudo per the instructions page in the second line above. After it completed I changed to the build directory and issued the compile sudo ./ and seems to run as expected. I select Full OS Image -> Show a kernel configuration menu -> (select ANY board) -> Current, and it seems to run fine until it gets to the following error - 2013?? This is the roadblock every time for me. What step did I miss or err? After a few tries I noticed it has a very brief error on boot - but I don't see how that would cause a download error or use a file from 2013? Guidance would be awesome at this point ;] .
  20. Armbian Rocks!! Thanks Igor!!
  21. Will the C2 image (S905) work with the C4 (S905X3)? Is anything coming for Armbian to support the C4? Love my Odroid stuff, love Armbian, marry them as often as possible ;]
  22. PLAY is the name of the game - if we don't, we die! (All work and no play makes Mac a dull boy ;] )
  23. How are things going over there? Did you get more or less time because of the CV? We'd sure like to use more peripherals designed for the Pi on Armbian supported boards ... I've got to the point I'd pay someone to get gpio audio cards working with Armbian. I am fairly good at a lot of things, but kernel modules and that level stuff I seem to rely on you guys for ;] Hope all is well.
  24. As in this Armbian forum I am regularly diagnosing power issues. I've answered with this info on a few different posts over the years but I wanted this in one place so my students and the Armbian forum could discuss it. You will read over and over the importance of good power, both in the supply, the cables, and the connection. Anything that causes the voltage to drop below each boards threshold will cause problems that seem to have no explanation. The board may run and appear to be 'working' but operations that draw more power may fail and let the processor continue running. You might think a fully functional board has software failures. It's hair pulling, especially for those uneducated in power issues. Without attempting to teach a power class I've come up with some tools that can 'prove' weather the power supply and cables can deliver the power you expect. There's deep math and science to all of it, but what we really need is to be able to 'trust' our power. These tools can help us 'prove' our power is at least staying above the levels we expect. When there are so many variables in a situation we have to eliminate things to narrow down the problem. Since power is frequently the problem and fairly easy to prove, it's smart to start there. But how? We use our tools to test what we need to eliminate. We used to use banks of resistors and separate power and current meters to measure power draw and voltage drop, but these days there are inexpensive tools called DC Electronic Loads that do this for us. I've purchased numerous versions and models, and they've all been good at what they are designed for yet lacking in some other things. A trade off of quality for expense, but good enough really is good enough. Basically they have a transistor and a very low value resistor across the output and your power supply is pulsed with a PWM across that transistor. The width of the pulse determines the current draw on your power supply, effectively 'simulating' power draw from your device while displaying the voltage at the point of the load and the draw current. You simply attach your power supply and increase the load until the voltage drops below the supply's rating. If the voltage stays above its voltage rating at its rated current, it passes. If not, it fails. Almost as simple as that. I usually let the thing run for a while and check for heating, voltage drop over time and shutdown. Sometimes failure comes with heat. If you have a 5v power supply that's rated at 4 amps, and your load reports 4.9v at 4A draw, your supply has failed. The image below shows a successful test of a popular power supply, the Meanwell RD65A., a dual voltage supply rated for 3A at 12v, and 6A at 5v. As you can see in the photos the voltage stays above its rating at the rated current. This particular photo was taken after approximately 40 minutes running at full load, which is highly inadvisable for this kind of power supply. Usually one would never run over 80% load continuously, but hey, this was a burn test. The only thing that failed here was the load, as the fan sensors on these particular models are somewhat flawed and overheat at less than their rating and shut down. Both the load and supply were run to their limits and we 'proved' this is a viable supply for our purposes. Here is an ebay search in the US that has similar inexpensive loads - and Amazon - They can be inexpensive and the fancy high power ones can be quite expensive ... find one that suits your needs. With another voltmeter you can check the drop in your cables. Set up the load to draw what you think is appropriate, note the voltage at the load. Then using the voltmeter measure the voltage at the power supply. Note the difference between the voltage at the supply and the voltage at the load. Viola, there's your drop. Is it good enough to run your board? Most 5v boards complain at 5v. They want above 5v, like 5.1. This is only a basic test, you can go a lot further but this will definitely prove your supply or fail it. If you really get into testing get some inline current measuring tools so you can see what your board is actually drawing. Most voltmeters have inline current meters and many are quite accurate and detailed. Watching the current draw on your board as you perform various operations can tell you if you have a hardware problem; if it draws more than the manufacturer specifies then there may well be a hardware issue. I hope this motivates someone to go farther with testing and proving their power.
  25. You have wiped out your input voltage circuit. To be brutally sincere you've probably destroyed the board. That being said, take a look at the schematics - select your model ... scroll down to page 14 and look at U9 - the regulator ... if all you did was wipe that out, you could replace it. You will need hot air soldering equipment and skills. HOWEVER, it's my experience that when over voltage is applied to a regulator, many times it fails by passing the power rather than blocking it. There is a good chance that 19 volts was applied to many 1.8 and 3.3 v circuits. In that case your board is toast. Mark it up to expensive education ... we've all done it. Most of us have plugged 12v into 5v boards that have no regulation. In that case the board is also toast.