gprovost

Members
  • Content Count

    255
  • Joined

  • Last visited


Reputation Activity

  1. Like
    gprovost reacted to count-doku in Helios4 Support   
    Hi Xavier,
     
    Kernel 5.5 is currently not supported by us. Our current kernel 4.19 has complete hardware support, dev kernel (5.4; which you need to compile yourself with https://github.com/armbian/build) should also have working PWM. 

    If you need to use Kernel 5.5 you are on your own, you can try to use the patches from 5.4 (https://github.com/armbian/build) to get PWM working...
     
    Cheers,
    count-doku
  2. Like
    gprovost got a reaction from TRS-80 in Helios64 Annoucement   
    Effectively I should have blurred the domain info, I made the assumption it was one of those domains from anonymizer email portal
     
     
    Yup happy to that and move on And be sure we appreciate to you seem to very interested by our board.
     
     
    Maybe @aprayoga can bring a bit of clarification here about the the chance that the work that has been done U-boot mainline could translate into not having to use RKBIN preloader one day.
     
     
    Yeah the main reason we added the M.2 SSD slot was to give more option in term of enclosure design for people having specific use case to address. The other reason is that the M.2 Slot has also USB 2.0 interface and can be used to installed NPU extension board.
  3. Like
    gprovost reacted to tekrantz in Helios4 Support   
    Hi,
    my helios4 was not running when I cam in this morning.  When I cycle power all I get is :
     
     
    BootROM - 1.73
    Booting from MMC
    Card did not respond to voltage select!
    Error initializing MMC - FFFFFFEF
    Trying Uart

    and nothing else.  I tried leaving it powered off for an hour and tried again and I get the same thing.
     
    Any suggestions?
     
    Thanks,
     
    Tim Krantz
     
     
    UPDATE!
    I finally got the idea to eject and re-insert the micro-sd card and now all is well.
     
    Have I mentioned how much I love this little machine?
     
  4. Like
    gprovost got a reaction from TRS-80 in Helios64 Annoucement   
    @TRS-80 Effectively all your messages ended up in SPAM, most probably because your first message contained a link :-/ FYI this is the result of Disqus SPAM engine not our actions... and it's not like I'm checking the SPAM box every 5 mins. I just approved all of them except the one where you start claiming we are censoring messages. Maybe next time before jumping to conclusion better to get in touch by other channel (like here) and ask what's happening. I mean honestly what would have been our interest in censoring your message on free software ? Our track record on Helios4 shows that we have always been super transparent. Plus your question is more towards Rockchip than us, since they are the one who so far are keeping their SoC pre-loader close source... there is clearly nothing hide. Anyone the pre-loader issue is something that will improve soon.
     

     
    TRS-80 EDIT: I believe you if you say so. But I removed picture showing partial personal info (email address) in your spam management console as I am very privacy conscious person.
     
  5. Like
    gprovost reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    I took a first pass at making a Google Sheet to track testing.
     
    https://bit.ly/2TGaeZN
     
    I'd love some feedback.  Feel free to modify.
  6. Like
    gprovost got a reaction from count-doku in Armbian 20.02 (Chiru) Release Thread   
    Adding @aprayoga
  7. Like
    gprovost got a reaction from lanefu in Armbian 20.02 (Chiru) Release Thread   
    Adding @aprayoga
  8. Like
    gprovost got a reaction from bartvz in Helios64 Annoucement   
    At later stage we will introduce a variant using SDRAM with on-die ECC feature. We are still waiting the 8Gb version to hit the market.
  9. Like
    gprovost reacted to aprayoga in Helios4 Support   
    Between middle-to end of November 2019, Armbian change the version and branch naming.
    Version from something like 5.91 become something like 19.11.x, if i'm not mistaken Year.Month, like Ubuntu versioning.
    Then the branch name,
    DEFAULT become LEGACY NEXT become CURRENT To upgrade to new version, use armbian-config.
    sudo apt-get update sudo apt-get -y upgrade sudo armbian-config
     
    Select System > Other, to switch to other kernel

     
    Confirm the action

     
    And after some process, you will be presented by list of kernels

     
    Select linux-image-current-mvebu. The system will install the new kernel and automatically reboot.
    Confirm the kernel installed correctly and Armbian changed to new branch CURRENT by executing,
    uname -a grep "BRANCH" /etc/armbian-release  
  10. Like
    gprovost reacted to DBwpg in Helios64 Annoucement   
    Kobol is now taking pre-orders:
    https://shop.kobol.io/
  11. Like
    gprovost got a reaction from gounthar in Helios64 Annoucement   
    We will post all those info in due time on out wiki, still so many things to do :-/. Typical idle power consumption of Helios64 with 5x WD RED is between 25-30W. Obviously power consumption will depends a lot on HDD brand / model you use. The reason of 120 watt PSU is you need to take in consideration current spike during HDD spin-up start, and you should always provision for a bigger PSU because PSU becomes less effective with time and you want to be sure the power budget is always easily covered by the PSU. But using your Helios4 PSU will do the job too because we are able to mitigate HDD spin-up current spike with on board power sequencing.
     
    I post some of the pics here
     



  12. Like
    gprovost reacted to count-doku in Helios64 Annoucement   
    Looks good! Congrats to the Kobol team for designing another interesting NAS board.
     
    Is the 12V 10A power supply neccessary though? I mean thats 120W, with that much power one can easily run a real x86... 
    How much does the board itself consume? 
     
     
  13. Like
    gprovost reacted to DBwpg in Helios64 Annoucement   
    Looks like they will be taking preorders as of next week😁
    https://blog.kobol.io/2020/01/02/helios64-annoucement/
  14. Like
    gprovost reacted to orion in Helios64 Annoucement   
    It seems so. Also they kept their promises for the case.
    The price for all what it offers I think it is quite decent. I like the expansion capability through the USB-C (DAS) I hope it works well with armbian.
     
    What is the opinion of more experienced people?
     
  15. Like
    gprovost got a reaction from gounthar in Helios64 Annoucement   
    Yeah I should have mentioned that also. Through the same USB Type-C we also support Flash over USB with the rockchip dev/flash tools available. The recovery button is on one of 3 push button on the board. Each on-board memory (SPI and eMMC) can be disabled with a proper jumper ( No need to have 16 fingers to flash the board ).
     
    We will try our best. Also we will sell a simple adapter kit in order for people to use Helios64 with any mini-ITX and ATX PSU. This way people could recycle their old case and save money.
  16. Like
    gprovost got a reaction from gounthar in Helios64 Annoucement   
    We will offer an ECC option. The Rockchip RK3399 SoC itself doesn't have a memory controller that has ECC feature, however we are currently working with a SDRAM vendor that now offer built-in ECC feature inside the SDRAM directly. It's not impossible it will be available on day one.
     
     
     
    No. It is not a use case that make sense from our point of view. I don't believe there will be a lot of people out there with a USB Type-C power adapter that can delivered up to 100W. Plus the power circuitry (and the PSU) would be quite expensive.
     
     
    No. It's a pure M.2 SATA port. FYI it's share with the SATA port 1, so the combination is either ( 1x M.2 SSD + 4x HDD/SSD ) or 5x HDD/SSD.
     
     
    Yes there is a 128Mb SPI NOR Flash.
     
     
    Something we didn't disclose because too much info already on the picture, the USB Type-C has been designed with a 4-in-1 mode concept :
    - Display Port
    - DAS mode
    - Host mode
    - Serial Console Access
    We will explain more at a later stage... but it's quite a unique design we did.
     
     
    We wanted to make the eMMC a basic feature of our board. I mean what's the point to sell it as a module when you know that in 90% of the case your user should use eMMC instead of SDcard. It also help in term of software support to know that all user Helios64 user will have the same config, therefore we can focus on installation guide that use the eMMC.
     
     
     
    You guess right this is not just some bare bone carrier board with a SoC in the middle. Between the PCIe-to-SATA bridge, the 2.5Gbe interface, the built-in UPS feature, RAM, eMMC, etc... it adds-up quickly. We also paid a lot of attention on the different power rails, this is a premium design compare to all the RK3399 board out there.
    Helios4 was USD200 with the full kit (PSU, case, cable, fan, etc...), our goal it to try to be in the same ballpark. This time we will sell a-la-carte style, you can just buy the board alone, our with the case, if you already have a PSU then no need to order one...
     
  17. Like
    gprovost got a reaction from gounthar in Helios64 Annoucement   
    Hi guys,
     
    I guess some might have heard that we (Kobol Team) were spinning a new project to succeed to Helios4. Here it is... Helios64
     

     
     
    We didn't have to look too far for the board name since in essence the goal was to redesign from scratch Helios4 with a 64-bit SoC and try to improve every key features that made Helios4 a very targeted board for NAS setup.
     
    Right now we are at the prototyping test phase, hopefully in a 2 month time will have dozen of Eval boards to send around for evaluation and review... and if all goes well first batch should be available for order in Feb / March 2020.
     
    Happy to answer any question :-)
     
  18. Like
    gprovost got a reaction from orion in Helios64 Annoucement   
    Yeah I should have mentioned that also. Through the same USB Type-C we also support Flash over USB with the rockchip dev/flash tools available. The recovery button is on one of 3 push button on the board. Each on-board memory (SPI and eMMC) can be disabled with a proper jumper ( No need to have 16 fingers to flash the board ).
     
    We will try our best. Also we will sell a simple adapter kit in order for people to use Helios64 with any mini-ITX and ATX PSU. This way people could recycle their old case and save money.
  19. Like
    gprovost got a reaction from orion in Helios64 Annoucement   
    We will offer an ECC option. The Rockchip RK3399 SoC itself doesn't have a memory controller that has ECC feature, however we are currently working with a SDRAM vendor that now offer built-in ECC feature inside the SDRAM directly. It's not impossible it will be available on day one.
     
     
     
    No. It is not a use case that make sense from our point of view. I don't believe there will be a lot of people out there with a USB Type-C power adapter that can delivered up to 100W. Plus the power circuitry (and the PSU) would be quite expensive.
     
     
    No. It's a pure M.2 SATA port. FYI it's share with the SATA port 1, so the combination is either ( 1x M.2 SSD + 4x HDD/SSD ) or 5x HDD/SSD.
     
     
    Yes there is a 128Mb SPI NOR Flash.
     
     
    Something we didn't disclose because too much info already on the picture, the USB Type-C has been designed with a 4-in-1 mode concept :
    - Display Port
    - DAS mode
    - Host mode
    - Serial Console Access
    We will explain more at a later stage... but it's quite a unique design we did.
     
     
    We wanted to make the eMMC a basic feature of our board. I mean what's the point to sell it as a module when you know that in 90% of the case your user should use eMMC instead of SDcard. It also help in term of software support to know that all user Helios64 user will have the same config, therefore we can focus on installation guide that use the eMMC.
     
     
     
    You guess right this is not just some bare bone carrier board with a SoC in the middle. Between the PCIe-to-SATA bridge, the 2.5Gbe interface, the built-in UPS feature, RAM, eMMC, etc... it adds-up quickly. We also paid a lot of attention on the different power rails, this is a premium design compare to all the RK3399 board out there.
    Helios4 was USD200 with the full kit (PSU, case, cable, fan, etc...), our goal it to try to be in the same ballpark. This time we will sell a-la-carte style, you can just buy the board alone, our with the case, if you already have a PSU then no need to order one...
     
  20. Like
    gprovost got a reaction from orion in Helios64 Annoucement   
    Hi guys,
     
    I guess some might have heard that we (Kobol Team) were spinning a new project to succeed to Helios4. Here it is... Helios64
     

     
     
    We didn't have to look too far for the board name since in essence the goal was to redesign from scratch Helios4 with a 64-bit SoC and try to improve every key features that made Helios4 a very targeted board for NAS setup.
     
    Right now we are at the prototyping test phase, hopefully in a 2 month time will have dozen of Eval boards to send around for evaluation and review... and if all goes well first batch should be available for order in Feb / March 2020.
     
    Happy to answer any question :-)
     
  21. Like
    gprovost reacted to aprayoga in Helios4 Support   
    Good to hear you got it working.  I tried the instructions first on my system and did not encounter such error. Could you share your u-boot version?
     
     
    I test on fresh Armbian_19.11.3_Helios4_buster_current_4.19.84.img
     
    1. I don't encounter such error when accessing the system from Windows using PuTTY or thru serial console
       UPDATE: i tried to SSH from my Ubuntu machine (got id_ID locale), indeed there are perl warning regarding locale but armbian-config is still usable to generate the locale, no need to manually edit file. After the locale generated by armbian-config, no more perl locale warning.

    2. Confirmed
    3. Confirmed.
    cat: /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies: No such file or directory cat: /sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors: No such file or directory /usr/lib/armbian-config/jobs.sh: line 1075: Error: Expected at least 5 tokens for --menu, have 4. Use --help to list options. / 1000: syntax error in expression (error token is ": Expected at least 5 tokens for --menu, have 4. Use --help to list options. / 1000") The path is not exist, even though the driver is compiled. I will need to investigate further.
    ---
    I also tried using fresh Armbian 5.91 then upgraded to Armbian 19.11.3, but strangely i don't see the System - CPU menu.

     
    4. As mentioned on @sirleon link, apparently Buster make use nftables by default and on our kernel is not enabled. You could try to switch to iptables-legacy version.
    CONFIG_NF_TABLES=m CONFIG_NF_TABLES_SET=m # CONFIG_NF_TABLES_INET is not set # CONFIG_NF_TABLES_NETDEV is not set # CONFIG_NF_TABLES_IPV4 is not set # CONFIG_NF_TABLES_ARP is not set # CONFIG_NF_TABLES_IPV6 is not set # CONFIG_NF_TABLES_BRIDGE is not set meanwhile, i will try to enable those modules and test.
     
    @Igor, could you take a look whether armbian-config issues also occur on other board?
  22. Like
    gprovost reacted to aprayoga in Helios4 Support   
    Hi @sirleon, the tutorial is intended for moving the rootfs to USB thumb drive and due to spi_workaround it does not work with SATA seamlessly but you almost there..
    I suggest to move the rootfs to drive that connected to SATA0 (most likely /dev/sda), because there is known issue that u-boot failed to recognized SATA device other than on SATA0.
     
    To boot from SATA you need to:
    1. Move the rootfs with sata-nand-install while spi_workaround is disabled, and reboot.
        The system will boot from SD card.
    2.  Unmount /boot and copy over boot files from /media/mmcboot/boot to /boot
    umount /boot cp -rf /media/mmcboot/boot/* /boot/ 3.  Edit /etc/fstab and remove/comment 2 lines that have mount point to /media/mmcboot and /boot.
    4.  Reboot the system and cancel u-boot auto boot.
    5.  Run following commands on u-boot prompt to add sata boot and reboot
    setenv boot_targets "usb0 scsi0 mmc0 pxe dhcp" setenv bootcmd_scsi0 'devnum=0; run scsi_boot' saveenv You could reorder the boot order on boot_targets variable. On above command, it would tried to boot from USB and if failed try SATA/SCSI and so on.
     
  23. Like
    gprovost reacted to dkxls in ZFS on Helios4   
    @gprovost Sure. I wasn't aware that you accept community contributions to the wiki.  I might take a stab at that once I have my own setup working ... If someone else, probably more experienced with ZFS, is up for that, please go ahead - I for one would certainly appreciate it.
  24. Like
    gprovost reacted to dkxls in ZFS on Helios4   
    @qstaq this sounds interesting. Would you be willing to share these scripts/settings either in public or private? I reckon this could be very useful, especially for beginners like me.
  25. Like
    gprovost reacted to sfx2000 in Helios64 Annoucement   
    16MB SPI NOR is a good choice, not just for uBoot, but one could put an entire operating system in there (openwrt for example)
     
     
    I agree - @chwe - solder down is going to offer benefit of cost and board space - 16GB is plenty of space considering the other connectivity.
     
    @gprovost - nice board...