Jump to content

denni_isl

Members
  • Posts

    125
  • Joined

  • Last visited

Reputation Activity

  1. Like
    denni_isl got a reaction from TRS-80 in Firfly-rk3399 have not been booting up reasent images from Armbian   
    This is a good summary of the most useful u-boot commands with some explanations https://docs.embeddedarm.com/U-boot_commands
     
  2. Like
    denni_isl got a reaction from TCB13 in NanoPi M4 V2 - M4 Image not working   
    Erueka! Now the wifi is working perfectly.
     
    Did fallow part of this instructions https://askubuntu.com/questions/621452/something-keeps-changing-my-wireless-regulatory-domain
     
     
  3. Like
    denni_isl reacted to chwe in eliminating hardware bloat   
    assuming that nobody uses it cause you don't use it is kind of.. Clearly  a bunch of people don't use GPIOs. Sarcastically 90% of the SBCs will collect dust as soon as 'it's not funny anymore' so they don't even need an SoC..
    As @Igor pointed out.. there are a bunch of SBCs for different use-cases.. Connectors are mostly cheap, so they solder as much as possible on it.. E.g. for the HC1 I would love to have at least an I2C bus and some GPIOs wired out.. (for some DS18b20 ore something like that to monitor the temperature).. If you want performance you'll have to pay for it anyway no matter if there are only a few or a bunch of connectors.. See RK3399 boards..
     
    Something else you've to consider.. you need some storage for the bootloader.. Normally those SoCs can't boot directly from SATA.. you either need an SD-Card, eMMC or SPI flash.. Here as well SD-Card is just the 'most convenient' way of doing it. Not much can go wrong and in case it does.. just reflash it.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines