Search the Community

Showing results for tags 'rk3328'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
  • Community/Newbie forums
    • Board does not start
    • Off-topic
    • Reviews, Tutorials, Hardware hacks
    • Help wanted
    • TV boxes
  • Hobbyists forums
    • P2P help
    • Feature Requests
  • Bug tracker - supported boards and images only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5, H6 and H616
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Board Bring Up
    • Armbian Project Administration
    • Development
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android fanboys's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues
  • Kobol Forum's Helios4
  • Kobol Forum's Helios64

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

Found 2 results

  1. Greetings, After receiving an "mx10 pro 4k" 4gb 32gb I tried booting armbian on it. Strangely, after trying multiple images, dtbs I couldn't boot into armbian no matter what. Becoming frustrated I proceed to open the box which surprised me: both the dusty packaging and PCB advertise an rk3328, but after removing the heat sink I found out that it actually contains an rk3318 as adb and android warned me. https://imgur.com/a/Hv1Qlw3 Not only did I get "scammed" (the box still works on android, and the average user wouldn't even notice), but now I seem to own an unknown box as it seems I can't trust the seller for anything they said. So here I am, trying to reverse engineer the box, it doesn't contain apparent I2C or any other serial port but I successfully connected with adb root, I would like to extract the blobs but I never did such a thing before with android so help will be appreciated
  2. It seems the Linux kernel 5.8+ on aarch64 is incompatible with the U-Boot from 2017, at least on the RK3328 boards. This apparently affects the Rock64 as well as my own Renegade. Essentially U-Boot gets stuck on "Starting kernel..." In this post https://archlinuxarm.org/forum/viewtopic.php?f=23&t=14657&start=10 they fix it by recompiling u-boot, newer version from upstream In addition to the existing rock64 defconfig, it seems that the defconfig for the Renegade was finally upstreamed on May! https://github.com/u-boot/u-boot/commit/bab972948e152e468fa5ab34764769fc4cddcaab No more 2017 U-Boot from rockchip for me, perharps... I modified https://archlinuxarm.org/packages/aarch64/uboot-rock64/files/PKGBUILD for the renegade and actually got a system that can boot Linux 5.8. (flashed the loader1 and an .itb file) I have 2 (possibly 1) issue: 1) Like the current branch in the armbian build, uboot is missing the ums (USB mass storage) command which is really useful to modify the emmc from a pc. 2) The 2020 uboot i compiled shows DDR4 333 in the first stage, instead of the older DDR4 786Mhz. Does that mean the RAM gets initialized at a lower speed? Maybe, but at least I can boot newer kernels now. Also Maybe the Rock64 and Renegade armbian packages should actually use the upsteam uboot instead of rockchip's 2017 version. I don't know if you already do this in the build tools, but it would be cool!