Jump to content

Xalius

Members
  • Posts

    154
  • Joined

  • Last visited

Posts posted by Xalius

  1. You have to update the devicetree blob or fex file with the new capacity and internal resistance of your new battery, then reset the AXP to restart the self-learning process. It will take a couple of cycles for the gauge to become correct again.

     

    http://linux-sunxi.org/Fex_Guide#pmu_configuration

     

    The two most important ones are

     

    pmu_battery_rdc: battery internal resistance in mΩ

    pmu_battery_cap: battery capacity in mAh

     

    There might be other ones you might want to tweak, but you have to keep in mind the overall power budget of the device and the charger/power adapter. Also don't burn down your house :)

  2. What Igor said :-), you can also use an overlay to enable it at run-time. Ayufan just added a script to toggle existing nodes without creating an overlay for each.

     

    https://github.com/ayufan-rock64/linux-build/blob/master/package/root/usr/local/sbin/enable_dtoverlay

     

    The eth1 interface was disabled by default since it creates issues when there is no magjack mounted on the Rock64 for it, e.g. when you don't have the top-board with the audio DAC, this is also the usual Linux convention for boards with headers.

  3. You have to be aware that the 4.4.x kernel series is the BSP kernel maintained by Rockchip (mostly based on Linaro LTS releases), which is different from mainline Linux with regards to drivers and other patches.

     

    RK's upstream for BSP Linux is here: https://github.com/rockchip-linux

    And you get all the info from: http://opensource.rock-chips.com/wiki_Main_Page

     

    Mainline Linux is developed by the community, but RK supports it too with patches: https://patchwork.kernel.org/project/linux-rockchip/list/

     

    You have to decide what kernel you want to run on your board, BSP is generally a bit more complete, for example it has VPU drivers, see status matrix here:

     

    http://opensource.rock-chips.com/wiki_Status_Matrix

     

    So you can't just patch your 4.4.x codebase up to current mainline, you have to work from the upstream repository...

  4. 12 hours ago, NickFoley said:

    Hi Xalius, thanks for the quick reply.

     

     

    I have started comparing both boards. However i do not have a particularly clear schematic of this custom board, so it is proving difficult. I have the base linux-image (and android image) that the manufacturer provided.  Would i be able to use the uboot/kernel provided with it or be able to pull the devicetree information from it?

     

    Do you have the fex files (if BSP Linux/Android )for the custom board or the devicetree (if mainline Linux) file? You can extract the devicetree blob from your custom board's Linux image and use that maybe, what kernel is running on the custom board?

  5. The first thing to do is to compare the schematic of your board to the schematic of whatever board you take as a reference for the image and find out all the differences, then take that board's devicetree file for u-boot and for Linux and update it with all the differences. Most of the time it's power related things that are controlled in a different way and what GPIOs are used for various controls, different pin mux settings for busses that have multiple pinouts etc...

  6. 14 hours ago, joaofl said:

    Video drivers were added to the H6 GPU at Allinner's git repository:

    https://github.com/Allwinner-Homlet/H6-CedarC

     

    Is there any progress with Armbian for the H6 boards?

     

     

    Those are not really video drivers, it's more or less just the glue layer between Cedarx (AW's proprietary video libraries) and the kernel drivers for Android BSP (Linux 3.10.x).... so it's more or less just a reference to look up some things that are not in the documentation (which might be released soon...)

  7. I tried to build that u-boot 2014 release from the BSP too... after fixing the error in the Makefile like you mentioned, I also got stuck on the u-boot build unless I use the specific linaro toolchain contained within that BSP drop, but the scripts are totally broken because they split up the BSP into several repos...

  8. Philipp Rossak is working on A83T H3 H5 A80 A64 Thermal driver (WIP: Philipp Rossak (embed-3d) wipbranch: sunxi-ths patch v2: contains only a83t and h3) 

     

    https://lkml.org/lkml/2018/1/28/406

     

    https://github.com/embed-3d/linux/tree/embed-3d/sunxi-ths

     

    So once the thermal drive is done, the next step is to implement DVFS operating points and more importantly, cooling devices based on those for safe operation of the SoCs...

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines