Jump to content

hipboi

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by hipboi

  1. 10 hours ago, martinayotte said:

    I don't remember where I got it on Jan 3rd ... The file is named ROCKPI-V13-sch-20180901.pdf but Google didn't find it ...

     EDIT : I found the source :

    @Igor in a PM on Jan 3rd, but I don't know if it can be released, I will leave him to confirm or not ...

     

    You can release it. We will polish the schematic formats and release it anyway...

  2. 15 hours ago, chwe said:

    WIP so things like that are expected.. :D Provide a bootlog and I'll have a look into it..

     

    [small to medium rant]

    If it's a Raxda produced 'Armbian' things might not work and I'll not fix it.. They decided to use their own 4.4 kernel fork and I'm not willing to look into it. If they want a more stable 4.4 based armbian Image they should contribute to Armbians 4.4 Kernel (basically @ayufan one with some patches). And not something like this:

     https://github.com/brian541/build

    We won't maintain a third RK3399 bsp kernel only cause there's a new board out which throws us a bunch of errors with ayufans kernel..

     

    That's where their armbian previews came from... The whole device tree looks like a fire and forget push.. e.g.

     

    https://github.com/radxa/kernel/blob/155a65a72b20b477663218ce47fd9130579ab375/arch/arm64/boot/dts/rockchip/rockpi-4b-linux.dts#L645-L707

    doesn't make sense at all.. The CSI populated on the board is a 2 lane 'RPi alike one' whereas ov13850 is a 13mp camera normally connected via 4lane mipi csi.. Looks like some leftover from a firefly or so.. Even then, it's on a different i2c bus which also looks fishy..

     

    https://github.com/radxa/kernel/blob/155a65a72b20b477663218ce47fd9130579ab375/arch/arm64/boot/dts/rockchip/rockpi-4b-linux.dts#L271-L286

    didn't work.. At least only one LED could be triggered.. or there's a third led somewhere which I didn't spot.. Unfortunately there aren't public available schematics to get a clue how things are soldered together here..

     

    https://github.com/radxa/kernel/blob/155a65a72b20b477663218ce47fd9130579ab375/arch/arm64/boot/dts/rockchip/rockpi-4b-linux.dts#L855-L957

    there's no IR led populated per default.. so this stuff looks just wrong...

     

    Maybe things get better once the board reaches mainline: https://patchwork.kernel.org/patch/10745929/

    normally the peer review there stops people from messing up stuff.. but this will take some time..

    [/rant]

     

    Currently, time doesn't allow to dig into it.. I've a lot of other work to do and my rockPi runs productive on mainline for a numbers crushing project I'm in (since 7 days it runs 24/7 at roughly 80°C and it does well here).. So I won't stop it from it only to fix a 4.4 kernel which is broken.. I can have a look into debug from console but not much more..

      

    First I would try to boot it from SD-Card not burning images directly onto eMMC.. Attach an USB-UART and provide us bootlogs.. Then we see where it stucks..

     

     

     

    Thanks for pointing it out. I will have out engineer look at it and clean the device tree. We would like to contribute to Armbian and get some decent support on ROCk Pi 4. Apparently, we should do it in the right way.

  3. 7 hours ago, pbies said:

    @martinayotte I am not asking about Armbian. I am asking about the mentioned OSes.

      

    I have Armbian on armv7l and it is 32-bit. At least provided binaries are 32-bit.

     

    I ask about bitness of the provided OSes for Rock Pi 4.

     

    There is no Armbian for this board.

     

    The radxa people is working on Armbian support for this board. I think it will be soon to have Armbian on ROCK Pi 4.

  4. Hi, this is Tom from Vamrs, I reply some of the questions you might want to know about Ficus board.

    Quote

     

    - what about PCIe situation? Did you test successfully 

     

    PCIE x16 is working, we've tested PCIE to M.2 adapter with M.2 SSD and PCIE to dual SATA card, both works fine.

     

    Quote

     

    - Do you plan an enclosure? By looking at the position of the PCIe slot some very custom enclosure is needed since PCIe cards are protruding ~25mm over

     

    Well, this is the not so good part I have complained to the author of 96boards Spec. Since the 96boards never considered the enclosure. I have also considered to change to PCIEx4 and indent ~25mm to fit the enclosure, I also suggested to change 96boards ee spec and add this option,  but it was not approved...

     

    Quote

     

    - no heatsink mounting holes. Why?

     

    We think a small heatsink with glue is enough for the big board.

     

    Quote

     

    - Pricing of board and add-ons (like BMC)?

     

    For the BMC, it must have the following feature:

    * it has ethernet

    * it has usb host, can port/run the rockchip firmware upgrade tool

    * it has web interface development environment

    * it must be stable and robust, and always boots

     

    It doesn't leave us much choices so we choose the wifi router chip with openwrt for quick development with features we want, ie remote management and remote firmware upgrade. The current design is based on the module Wrtnode 2P.  It's around 10 to 14usd for retail.  

     

     

    Btw, we need developers working on OpenWRT on WRTnode 2P, takes as below:

    1. port rkdeveloptool on OpenWRT

    2. test and verify the rk3399 power control, maskrom mode

    3. simplify the web interface, remove all the router things

    4. implement remote firmware upgrading function, basically download the firmware, make rk3399 in maskrom mode and run rkdeveloptool

    5. optional get 4G module working(uart interface)

     

    We are really lack of hands. If anyone is interested in tasks above, we are happy to send a set of kits to develop.

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines