Board Bring Up Station P1 rk3399, M1 rk3328


balbes150
 Share

8 8

Recommended Posts

14 hours ago, Winguo said:

Hey friends,

We recommend you all to boot other systems from SD card.

We will publish tutorials continuously.

Please stay tuned!

Thank you for all your support!

I can't seem to get anything to boot from the SD card.  Almost seems like it is disabled by the current Station OS installed on the P2.  Can you explain?

 

Thx.

Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

5 hours ago, redjr said:

I can't seem to get anything to boot from the SD card.  Almost seems like it is disabled by the current Station OS installed on the P2.  Can you explain?

 

Thx.

1st. This thread is about the Station P1, not P2.

2nd. For RK3399 at least it is normal that the boot order is SPI, eMMC, SD. If there is a valid boot loader found on either SPI or eMMC it will boot from there. Armbians workaround for this is to put a bootloader in that redirects on microSD first and if that was unsuccessful to use default order. Other operating systems often don't do that.

Link to post
Share on other sites

5 hours ago, Werner said:

1st. This thread is about the Station P1, not P2.

2nd. For RK3399 at least it is normal that the boot order is SPI, eMMC, SD. If there is a valid boot loader found on either SPI or eMMC it will boot from there. Armbians workaround for this is to put a bootloader in that redirects on microSD first and if that was unsuccessful to use default order. Other operating systems often don't do that.

Noted.  I just thought I could perhaps find some useful, related information here that would make my quest a little easier.  I believe the architecture of the P1 and P2 are similar but use different ARM Rock chipset.  Perhaps Firefly will start to post more information on the Station P2,  Perhaps even a useful forum on their own site.  :)

Link to post
Share on other sites

27 minutes ago, redjr said:

I believe the architecture of the P1 and P2 are similar but use different ARM Rock chipset.


It could be very different in term of software support. Chip integrator are getting initial generic SDK (with chip from Rockchip in this case) for providing some demo software which is usually made around some old (BSP) Linux kernel fork. For RK3566/RK3568 this is made around 4.19.y which is traditionally full of dirty hacks combined with proprietary hacks and blobs. Usable mainline support (which is done by 3rd party paid staff and community) is probably a year, two away. Hard to judge and predict how long before running proper OS such as Armbian without looking very closely on the chip diff (well supported RK3399 found in P1).

Link to post
Share on other sites

05.07.2021 в 14:52, JMCC сказал:

That seems very interesting. I already built patched Kodi packages for Debian Bullseye (available for download here), but they were not too useful without the kernel-side patches. If you can add those patches to Armbian mainline, we could give it a try.

Do I understand correctly, to test your new packages,  need to build a version of Bullseye + a new kernel (with patches for LE) ?

By the way, are you planning to build new packages with the latest developments for KODI-19 ?

Link to post
Share on other sites

1 minute ago, balbes150 said:

Do I understand correctly, to test your new packages, you need to build a version of Bullseye + a new kernel (with patches for LE) ?

That is correct. I did it for AllWinner when I made the packages, but kernel development was still in a very early stage, so only 1080p H264, and not all files played well IIRC.

 

3 minutes ago, balbes150 said:

By the way, are you planning to build new packages with the latest developments for KODI-19 ?

Right now, I cannot take care of it, due to many new things coming along in personal life. Maybe later, I am not sure.

Link to post
Share on other sites

7 минут назад, JMCC сказал:

Right now, I cannot take care of it, due to many new things coming along in personal life. Maybe later, I am not sure.

I asked about this because I want to understand if it makes sense to support a new kernel now. If you have no plans to use it, I want to reduce the number of different cores and remove it from support (remove it from the official build system, so as not to produce unnecessary entities).  :)

Link to post
Share on other sites

2 minutes ago, balbes150 said:

I asked about this because I want to understand if it makes sense to support a new kernel now. If you have no plans to use it, I want to reduce the number of different cores and remove it from support (remove it from the official build system, so as not to produce unnecessary entities).  :)

I see. Are you talking about a legacy kernel, or mainline? In any case, I don't have intentions to make any update to the legacy kernel packages, all new work would be done in mainline.

Link to post
Share on other sites

25 минут назад, JMCC сказал:

I see. Are you talking about a legacy kernel, or mainline? In any case, I don't have intentions to make any update to the legacy kernel packages, all new work would be done in mainline.

We are talking about the kernel Station-current  (which now uses all the patches for LE).

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

8 8