nokirunner

August 3, 2020

On 8/2/2020 at 6:18 PM, jock said:

Good news, expecially for @nokirunner and @DaviMesquita

Finally we managed to make the ssv6x5x driver work on the ssv6256p chipset and it turns out the it is also working pretty well. I removed most of the logging messages it was spamming on the dmesg log, now it is much more silent and it is ok this way. Teaming with @fabiobassa we optimized performances quite a bit, so expect ~60 Mbit/s at least on optimal setups. It works on both 2.4Ghz and 5Ghz bands.

The driver will be included in the armbian images soon, but in the meantime anyone can test it.

Download ssv6x5x.koand put it into /lib/modules/$(uname -r)/drivers/net/wireless

Download ssv6x5x-wifi.cfgand put it into /lib/firmware

Download ssv6x5x-sw.bin and put it into /lib/firmware

Run depmod -a

Add blacklist ssv6051 in /etc/modprobe.d/blacklist-rk322x-box.conf (ssv6051 and ssv6x5x kernel modules clashes, we need to blacklist ssv6051 for the other to work)

Reboot!

Any testing report is appreciated!

good job guys, I felt that it would only be a matter of time for you to screw these drivers.
I'm going to test them right now.

July 5, 2020

33 minutes ago, jock said:

Yeah firefox scrolling is very good, about the load time... well the CPU is not strong enough for that

Looking at that onf I'm astonished X.org really starts

Are you on legacy or mainline kernel? Because mixing things can be make the box explode!

Good luck for the multiboot project, it is rather interesting and I'm sure a lot of people here will be interested (myself included)

honestly, I did some mix cocktails, I put kernels and libraries of the latest release of the legacy kernel in the sdcard that worked for me ... so theoretically I'm with the latest release ...
however, the fact is that now I have a good 2d acceleration ... but anyway there is something that engulfs the download and the upload of the browser navigation, I tried midori and it works a little better ...
As for the multi boot project I saw that there is grub for arm u boot but I am still too immature for these steps
https://forum.odroid.com/viewtopic.php?t=26894
https://packages.debian.org/sid/grub-uboot

July 5, 2020

1 hour ago, fabiobassa said:

you should put in the env also an olive, some martini and mix, not shake

ok other than this , yes would be anice idea have both , compliments for the idea

@fabiobassa hehehe for now I'm having fun when I have some free time ...

@jock
hey I can use firefox from the tv box, and the scrolling of the pages is superfast!, I managed to activate the 2d acceleration, the only thing is that it takes a long time to load the pages, how could I get around this problem? ... however this is the configuration I'm using on the xorg config file


Section "Device"
    Identifier  "Rockchip Graphics"
    Driver      "modesetting"
    Option      "DRI2"            "True"
    Option      "AccelMethod"    "glamor"     ### "glamor" to enable 3D acceleration, "none" to disable 

EndSection

Section "Device"
	Identifier	"Armsoc-compatible DRM driver"
	Driver		"armsoc"
	Option		"DRI"	"3"
	Option          "AccelMethod"    "glamor" 
EndSection

actually checking the xorg log file it tells me that it takes the first device ... I tried to do the opposite, putting armsoc first ... the configurations took them with armsoc driver, but was slow as the shit ...

only that doing so, if I start some application with glrun, these seem to go in full screen, which changes resolution but goes in "black screen" and I am forced to force a reboot.

July 5, 2020

deleted

July 5, 2020

2 hours ago, jock said:

Hello @nokirunner, glad to see you!

Are you using a recent image or it is an older installation?

hey @jock how are you?
yes, I'm using an old installation, it's working on my sdcard and I'm fiddling with that.
unfortunately on my board, I still can't install on emmc, I checked and I understood that I don't have a nand, my board is strange, if I try to make a firmware flash I fuck the bootloader, and I'm forced to do a maskrom recovery.
however I'm studying, my goal is to keep both android in one partition from a couple of gigabytes and Armbian on a second partition. I have already managed to make one of my armbian sdcard on the second partition in the emmc and I have been able to boot on the emmc by simply putting

rootdev = UUID = "id of the emmc partition"

in the sdcard armbianenv.txt file

my goal is obviously to be able to have a selection menu for multiple os and to be able to use the device without sdcard

Quote

Mainline kernel images instead should already get 3D acceleration out of the box, despite having slow X11 experience for now.

putting DRI 3 and glamor in both xorg config files I really had some improvements

July 4, 2020

Well guys I don't know if you have already done it, but I realized that there was no 3D acceleration on my desk (after installing the video drivers) so I modified the x11 config file and I restarted ... and now i have the tv box which can be used almost like a desktop ...

so Make a backup of the file "/etc/X11/xorg.conf.d/01-armbian-defaults.conf", and replace its content with the following:

Section "Device"
    Identifier  "Rockchip Graphics"
    Driver      "modesetting"
    Option      "AccelMethod"    "glamor"     ### "glamor" to enable 3D acceleration, "none" to disable 
    Option      "DRI"            "2"

    # You can disable Vsync for better 3D benchmark score, at the cost of worst video playing. Not recommended.
    # Option      "Dri2Vsync"      "false"

EndSection
Section "Screen"
    Identifier "Default Screen"
    SubSection "Display"
        Depth 24
        Modes "1920x1080" "1280x1024" "1024x768" "800x600"
    EndSubSection
EndSection

June 26, 2020

On 6/20/2020 at 3:49 PM, Reddwarf said:

will the ssv6051p chip (wich I seem to have) be supported in newer kernel(s)?

I believe it will be possible only if some acute wizard manages to take the source code and update and fix it. there are some sources of the drivers of these wifi chips on github, here is same example:

https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx

https://github.com/trustfarm/orangepi-zero-tfarm/tree/0a9ce3984366d54d4fdefb9abbdcf9b899d924e6/OrangePi-Kernel/linux-3.4/drivers/net/wireless/ssv6xxx

June 7, 2020

@jock
no recently having had little time, I just took a peek at the last comments ..
this is great news, as soon as i can i try to give it a peek. HURRA!

June 7, 2020

Ciao @jock are there any news in this new update from the point of view of 3D &video acceleration?

May 5, 2020

19 hours ago, jock said:

Youtube instead is out of reach, no way to watch a video even in low quality (480p) without having audio and video issues.

we hope that we will have more luck with the opensource gpu drivers in the near future ... everything will have to go through a mesa-opengl acceleration, including video ... va-api or samething

April 28, 2020

6 hours ago, jock said:

The method is called steP-nand (Ste Puttane di NAND)

I'm arming myself to try the new method just for this :lol:

April 20, 2020

On 4/17/2020 at 10:10 AM, jock said:

They remain because they are not partitions but devices.

Could you post the results of mmc extcsd read /dev/mmcblk2 here?

@jock sorry I did not have time in these days to devote to the tvbox ..
here is the result of your request

$ sudo mmc extcsd read /dev/mmcblk2
[sudo] password for neonoki: 
Sorry, try again.
[sudo] password for neonoki: 
=============================================
  Extended CSD rev 1.6 (MMC 4.5)
=============================================

Card Supported Command sets [S_CMD_SET: 0x01]
HPI Features [HPI_FEATURE: 0x01]: implementation based on CMD13
Background operations support [BKOPS_SUPPORT: 0x01]
Max Packet Read Cmd [MAX_PACKED_READS: 0x3f]
Max Packet Write Cmd [MAX_PACKED_WRITES: 0x3f]
Data TAG support [DATA_TAG_SUPPORT: 0x01]
Data TAG Unit Size [TAG_UNIT_SIZE: 0x04]
Tag Resources Size [TAG_RES_SIZE: 0x00]
Context Management Capabilities [CONTEXT_CAPABILITIES: 0x05]
Large Unit Size [LARGE_UNIT_SIZE_M1: 0x07]
Extended partition attribute support [EXT_SUPPORT: 0x03]
Generic CMD6 Timer [GENERIC_CMD6_TIME: 0x0a]
Power off notification [POWER_OFF_LONG_TIME: 0x3c]
Cache Size [CACHE_SIZE] is 65536 KiB
Background operations status [BKOPS_STATUS: 0x00]
1st Initialisation Time after programmed sector [INI_TIMEOUT_AP: 0x1e]
Power class for 52MHz, DDR at 3.6V [PWR_CL_DDR_52_360: 0x00]
Power class for 52MHz, DDR at 1.95V [PWR_CL_DDR_52_195: 0x00]
Power class for 200MHz at 3.6V [PWR_CL_200_360: 0x00]
Power class for 200MHz, at 1.95V [PWR_CL_200_195: 0x00]
Minimum Performance for 8bit at 52MHz in DDR mode:
 [MIN_PERF_DDR_W_8_52: 0x00]
 [MIN_PERF_DDR_R_8_52: 0x00]
TRIM Multiplier [TRIM_MULT: 0x02]
Secure Feature support [SEC_FEATURE_SUPPORT: 0x55]
Boot Information [BOOT_INFO: 0x07]
 Device supports alternative boot method
 Device supports dual data rate during boot
 Device supports high speed timing during boot
Boot partition size [BOOT_SIZE_MULTI: 0x10]
Access size [ACC_SIZE: 0x07]
High-capacity erase unit size [HC_ERASE_GRP_SIZE: 0x01]
 i.e. 512 KiB
High-capacity erase timeout [ERASE_TIMEOUT_MULT: 0x01]
Reliable write sector count [REL_WR_SEC_C: 0x01]
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x50]
 i.e. 40960 KiB
Sleep current (VCC) [S_C_VCC: 0x07]
Sleep current (VCCQ) [S_C_VCCQ: 0x07]
Sleep/awake timeout [S_A_TIMEOUT: 0x11]
Sector Count [SEC_COUNT: 0x01d5a000]
 Device is block-addressed
Minimum Write Performance for 8bit:
 [MIN_PERF_W_8_52: 0x00]
 [MIN_PERF_R_8_52: 0x00]
 [MIN_PERF_W_8_26_4_52: 0x00]
 [MIN_PERF_R_8_26_4_52: 0x00]
Minimum Write Performance for 4bit:
 [MIN_PERF_W_4_26: 0x00]
 [MIN_PERF_R_4_26: 0x00]
Power classes registers:
 [PWR_CL_26_360: 0x00]
 [PWR_CL_52_360: 0x00]
 [PWR_CL_26_195: 0x00]
 [PWR_CL_52_195: 0x00]
Partition switching timing [PARTITION_SWITCH_TIME: 0x01]
Out-of-interrupt busy timing [OUT_OF_INTERRUPT_TIME: 0x02]
I/O Driver Strength [DRIVER_STRENGTH: 0x00]
Card Type [CARD_TYPE: 0x07]
 HS Dual Data Rate eMMC @52MHz 1.8V or 3VI/O
 HS eMMC @52MHz - at rated device voltage(s)
 HS eMMC @26MHz - at rated device voltage(s)
CSD structure version [CSD_STRUCTURE: 0x02]
Command set [CMD_SET: 0x00]
Command set revision [CMD_SET_REV: 0x00]
Power class [POWER_CLASS: 0x00]
High-speed interface timing [HS_TIMING: 0x01]
Erased memory content [ERASED_MEM_CONT: 0x00]
Boot configuration bytes [PARTITION_CONFIG: 0x00]
 Not boot enable
 No access to boot partition
Boot config protection [BOOT_CONFIG_PROT: 0x00]
Boot bus Conditions [BOOT_BUS_CONDITIONS: 0x00]
High-density erase group definition [ERASE_GROUP_DEF: 0x00]
Boot write protection status registers [BOOT_WP_STATUS]: 0x00
Boot Area Write protection [BOOT_WP]: 0x10
 Power ro locking: possible
 Permanent ro locking: not possible
 ro lock status: not locked
User area write protection register [USER_WP]: 0x00
FW configuration [FW_CONFIG]: 0x00
RPMB Size [RPMB_SIZE_MULT]: 0x01
Write reliability setting register [WR_REL_SET]: 0x1f
 user area: the device protects existing data if a power failure occurs during a write operation
 partition 1: the device protects existing data if a power failure occurs during a write operation
 partition 2: the device protects existing data if a power failure occurs during a write operation
 partition 3: the device protects existing data if a power failure occurs during a write operation
 partition 4: the device protects existing data if a power failure occurs during a write operation
Write reliability parameter register [WR_REL_PARAM]: 0x05
 Device supports writing EXT_CSD_WR_REL_SET
 Device supports the enhanced def. of reliable write
Enable background operations handshake [BKOPS_EN]: 0x00
H/W reset function [RST_N_FUNCTION]: 0x00
HPI management [HPI_MGMT]: 0x01
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
 Device support partitioning feature
 Device can have enhanced tech.
Max Enhanced Area Size [MAX_ENH_SIZE_MULT]: 0x0000bb
 i.e. 7659520 KiB
Partitions attribute [PARTITIONS_ATTRIBUTE]: 0x00
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
 Device partition setting NOT complete
General Purpose Partition Size
 [GP_SIZE_MULT_4]: 0x000000
 [GP_SIZE_MULT_3]: 0x000000
 [GP_SIZE_MULT_2]: 0x000000
 [GP_SIZE_MULT_1]: 0x000000
Enhanced User Data Area Size [ENH_SIZE_MULT]: 0x000000
 i.e. 0 KiB
Enhanced User Data Start Address [ENH_START_ADDR]: 0x00000000
 i.e. 0 bytes offset
Bad Block Management mode [SEC_BAD_BLK_MGMNT]: 0x00
Periodic Wake-up [PERIODIC_WAKEUP]: 0x00
Program CID/CSD in DDR mode support [PROGRAM_CID_CSD_DDR_SUPPORT]: 0x01
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[127]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[126]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[125]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[124]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[123]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[122]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[121]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[120]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[119]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[118]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[117]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[116]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[115]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[114]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[113]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[112]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[111]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[110]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[109]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[108]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[107]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[106]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[105]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[104]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[103]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[102]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[101]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[100]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[99]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[98]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[97]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[96]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[95]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[94]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[93]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[92]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[91]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[90]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[89]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[88]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[87]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[86]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[85]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[84]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[83]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[82]]: 0x0e
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[81]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[80]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[79]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[78]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[77]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[76]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[75]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[74]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[73]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[72]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[71]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[70]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[69]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[68]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[67]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[66]]: 0x08
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[65]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[64]]: 0x03
Native sector size [NATIVE_SECTOR_SIZE]: 0x00
Sector size emulation [USE_NATIVE_SECTOR]: 0x00
Sector size [DATA_SECTOR_SIZE]: 0x00
1st initialization after disabling sector size emulation [INI_TIMEOUT_EMU]: 0x00
Class 6 commands control [CLASS_6_CTRL]: 0x00
Number of addressed group to be Released[DYNCAP_NEEDED]: 0x00
Exception events control [EXCEPTION_EVENTS_CTRL]: 0x0000
Exception events status[EXCEPTION_EVENTS_STATUS]: 0x0000
Extended Partitions Attribute [EXT_PARTITIONS_ATTRIBUTE]: 0x0000
Context configuration [CONTEXT_CONF[51]]: 0x00
Context configuration [CONTEXT_CONF[50]]: 0x00
Context configuration [CONTEXT_CONF[49]]: 0x00
Context configuration [CONTEXT_CONF[48]]: 0x00
Context configuration [CONTEXT_CONF[47]]: 0x00
Context configuration [CONTEXT_CONF[46]]: 0x00
Context configuration [CONTEXT_CONF[45]]: 0x00
Context configuration [CONTEXT_CONF[44]]: 0x00
Context configuration [CONTEXT_CONF[43]]: 0x00
Context configuration [CONTEXT_CONF[42]]: 0x00
Context configuration [CONTEXT_CONF[41]]: 0x00
Context configuration [CONTEXT_CONF[40]]: 0x00
Context configuration [CONTEXT_CONF[39]]: 0x00
Context configuration [CONTEXT_CONF[38]]: 0x00
Context configuration [CONTEXT_CONF[37]]: 0x00
Packed command status [PACKED_COMMAND_STATUS]: 0x00
Packed command failure index [PACKED_FAILURE_INDEX]: 0x00
Power Off Notification [POWER_OFF_NOTIFICATION]: 0x01
Control to turn the Cache ON/OFF [CACHE_CTRL]: 0x01

April 16, 2020

11 hours ago, jock said:

You may try with blkdiscard /dev/mmcblk2 that is the proper way to erase the eMMC.

@jock
obviously I did this too (and in this case, the device gose in mask rom directly directly as soon as I power up)
but despite the formatting those other "3 partitions" remain

however, formatting mmclk2p1 the sdcard patched with libreELEC starts, while the sdcard with the original rom created by you continues not to start .. So I assume I can't boot by installing on nand for some reason which is the same as that which does not start the sdcard ... anyway, what is particular about the patching with libreElEC that manages to start the sdcard, while the original rom created by you does not start?

would it be complex to create a script that makes your rom more universal starting from sdcard? (just ask out of curiosity)

Edit:
I'm doing research on what these three partitions are, (in my case, i saw through arbian and each boot is 2mb, and the other is 256 kb)
at this link
https://github.com/ScottW514/GF-Hardware/wiki/02_Firmware-Overview
I found this description:

Quote

The storage appears as four separate hardware devices:

mmcblk2rpmb (0 MB): Replay Protected Memory Block. This is not directly accessible to the user and does not appear to be utilized by the Glowforge.

mmcblk2boot0 (16 MB): This has a single partition that stores the "Recovery" firmware image. This image is booted after a watchdog timer timeout, and when requested by the user with a power on and button pressing sequence (hold print button down, turn power on, release button within 1 second of powering on). The recovery process will be detailed further in a future section.

mmcblk2boot1 (16 MB): This has a single partition. It only has bin, games, include, lib, sbin, share, and src directories. It's actual purpose is unknown at this time

April 15, 2020

@fabiobassa

ok I understood, it was for the excitement of being able to do something that had a meaning ..
I reflash the loader at 300mhz.
I continue to have the problem that I can not put the system on nand ... deleting it completely I ca in mask mode and therefore I do not start from sdcard with the systems that created @jock

so I wonder I noticed that there are two other "partitions" but they are not, because if I try to manage them with fdisk it won't let me access ... so it's as if they were 3 other micro memories apart ... mmcblk2boot0 mmcblk2boot1 mmcblk2rpmb ..
could it be that they are the ones that cause me problems ??

now I have tried to format mmcbk2p1 manually ... to see if it allows me to access it from sdcard with a jock image

root@rk322x-box:/mnt# lsblk -f
NAME         FSTYPE LABEL   UUID                                 FSAVAIL FSUSE% MOUNTPOINT
mmcblk0                                                                         
└─mmcblk0p1  ext4           e6f899a4-a9ff-4aa7-85d5-33a21bcdb1de   25,6G     9% /
mmcblk2                                                                         
└─mmcblk2p1  ext4   armbian 363eece8-f5d4-4e46-bb6b-77d58f1c0499                
mmcblk2boot0                                                                    
mmcblk2boot1                                                                    
mmcblk2rpmb                                                                     
zram0                                                              40,3M    10% /var/log
zram1                                                                           [SWAP]

April 15, 2020

54 minutes ago, fabiobassa said:

So PLEASE.. don't overclock DDR

@fabiobassa I did it! :lol:
and everything works perfectly, both with android and with armbian

before I tried to flash the loader by @jock, but it did not work well, I could not enter usb mode to flash other things, also I did not start android, only armbian from sdcard ... so I entered mask mode rom and I flashed the original firmware ... then I loaded the custom loader at 300mhzRK322A_loader_v1.10.256.bin

Spoiler

(./boot_merger --pack --verbose -c RK322A -1 ../bin/rk32/rk322x_ddr_300MHz_v1.10.bin -2 ../bin/rk32/rk322x_usbplug_v2.56.bin -d ../bin/rk32/rk322x_ddr_300MHz_v1.10.bin -b ../bin/rk32/rk322x_miniloader_v2.56.bin )

and I saw that everything worked perfectly ..
but I was tempted to flash the 400mhz RK322A_loader_v1.09.256.bin

Spoiler

(./boot_merger --pack --verbose -c RK322A -1 ../bin/rk32/rk322x_ddr_400MHz_v1.09.bin -2 ../bin/rk32/rk322x_usbplug_v2.56.bin -d ../bin/rk32/rk322x_ddr_400MHz_v1.09.bin -b ../bin/rk32/rk322x_miniloader_v2.56.bin)

version to see what was happening ... at most if it didn't start I would do a total reset ... but everything worked as smooth as oil .. :lol:

on the chip I was sure what it was because it was written on the rom and also the bootloader so now I went from bootloader 2.38 to 2.56 with usbplug

April 15, 2020

3 minutes ago, fabiobassa said:

_by_SergioPoverony.zip

@fabiobassadei poveri :lol: .... ok I go back to 300 mhz .. ... e se ci piallassi qualcosa a raffreddamento a liquido funzionerebbe a 400mnz? :lol:

April 15, 2020

@jock
it worked!
for some reason ul wasn't working ...
i had to use from here http://opensource.rock-chips.com/wiki_Rkdeveloptool

rkdeveloptool wl 0x40  loader.bin

April 15, 2020

@jock

46 minutes ago, jock said:

run sudo ./rkdeveloptool rk322x_loader.bin, it should finish in less than 5 seconds

probably indendevi with the addition of ul, otherwise it tells me that illegal operation ...
however I tried and I get the same result ...

sudo ./rkdeveloptool ul rk322x_loader.bin
The device does not support this operation!

meanwhile, I had also gone to create the custom loader, having investigated the type of chip and ram taken from the official firmware and from the network by reading the datasheet on the type of ram mounted on the pcb ...
but I always get stuck at the usual point ...

am I wrong wrong connection mode with the usb ??
do I have to enter mask rom ??
to flash the image I can, but not to flash the loader ..

$ ./boot_merger --pack --verbose -c RK322A -1  ../bin/rk32/rk322x_ddr_400MHz_v1.09.bin -2 ../bin/rk32/rk322x_usbplug_v2.56.bin  -d ../bin/rk32/rk322x_ddr_400MHz_v1.09.bin  -b  ../bin/rk32/rk322x_miniloader_v2.56.bin
enable debug
W: [main] do_merge
fix opt:RK322A_loader_v1.09.256.bin
---------------
USING CONFIG:
[CHIP_NAME]
NAME=RK322A
[VERSION]
MAJOR=2
MINOR=56
[CODE471_OPTION]
NUM=1
Path1=../bin/rk32/rk322x_ddr_400MHz_v1.09.bin
[CODE472_OPTION]
NUM=1
Path1=../bin/rk32/rk322x_usbplug_v2.56.bin
[LOADER_OPTION]
NUM=2
LOADER1=FlashData
LOADER2=FlashBoot
FlashData=../bin/rk32/rk322x_ddr_400MHz_v1.09.bin
FlashBoot=../bin/rk32/rk322x_miniloader_v2.56.bin
[OUTPUT]
PATH=RK322A_loader_v1.09.256.bin
---------------

W: [getBCD] ret:2
W: [getBCD] ret:56
W: [getTime] 2020-4-15 17:17:27
W: [getChipType] chip:RK322A
W: [getChipType] type:0x33323241
W: [mergeBoot] write hdr
W: [mergeBoot] write code 471 entry
W: [saveEntry] write:../bin/rk32/rk322x_ddr_400MHz_v1.09.bin
W: [saveEntry] write:../bin/rk32/rk322x_ddr_400MHz_v1.09.bin
W: [getName] path:../bin/rk32/rk322x_ddr_400MHz_v1.09.bin, name:rk322x_ddr_400MHz_v
W: [getFileSize] path:../bin/rk32/rk322x_ddr_400MHz_v1.09.bin, size:10468
W: [saveEntry] align size:12288
W: [mergeBoot] write code 472 entry
W: [saveEntry] write:../bin/rk32/rk322x_usbplug_v2.56.bin
W: [saveEntry] write:../bin/rk32/rk322x_usbplug_v2.56.bin
W: [getName] path:../bin/rk32/rk322x_usbplug_v2.56.bin, name:rk322x_usbplug_v2.5
W: [getFileSize] path:../bin/rk32/rk322x_usbplug_v2.56.bin, size:86096
W: [saveEntry] align size:88064
W: [mergeBoot] write loader entry
W: [saveEntry] write:../bin/rk32/rk322x_ddr_400MHz_v1.09.bin
W: [saveEntry] write:../bin/rk32/rk322x_ddr_400MHz_v1.09.bin
W: [getName] path:FlashData, name:FlashData
W: [getFileSize] path:../bin/rk32/rk322x_ddr_400MHz_v1.09.bin, size:10468
W: [saveEntry] align size:12288
W: [saveEntry] write:../bin/rk32/rk322x_miniloader_v2.56.bin
W: [saveEntry] write:../bin/rk32/rk322x_miniloader_v2.56.bin
W: [getName] path:FlashBoot, name:FlashBoot
W: [getFileSize] path:../bin/rk32/rk322x_miniloader_v2.56.bin, size:89904
W: [saveEntry] align size:90112
W: [mergeBoot] write code 471
W: [getFileSize] path:../bin/rk32/rk322x_ddr_400MHz_v1.09.bin, size:10468
W: [mergeBoot] write code 472
W: [getFileSize] path:../bin/rk32/rk322x_usbplug_v2.56.bin, size:86096
W: [mergeBoot] write loader
W: [getFileSize] path:../bin/rk32/rk322x_ddr_400MHz_v1.09.bin, size:10468
W: [getFileSize] path:../bin/rk32/rk322x_miniloader_v2.56.bin, size:89904
W: [mergeBoot] write crc
W: [getFileSize] path:RK322A_loader_v1.09.256.bin, size:203082
W: [getCrc] crc:0x0dbe3e51
merge success(RK322A_loader_v1.09.256.bin)
noki@runner:rkbin-master/tools$ sudo ./rkdeveloptool ul RK322A_loader_v1.09.256.bin
[sudo] password di noki:          
The device does not support this operation!

April 15, 2020

@fabiobassa thanks for the link, now the situation is a little more understandable, however I have this problem, that when I run these commands, I don't get the idbloaders from the eemmc -rom loaded ..
or maybe I'm doing something wrong and I have to get the idbloader from somewhere else ??

Quote
Get idbloader for eMMC from Rockchip release loader

No need to package a idbloader.img for eMMC if you are using Rockchip release loader, you can get idbloader on eMMC with below command:
rkdeveloptool db rkxx_loader_vx.xx.bin
rkdeveloptool ul rkxx_loader_vx.xx.bin

April 14, 2020

@jock @fabiobassa

i can't understand some issues ..
I tried to do some experiments on the nand ..
first I deleted directly to see if I can start armbian from sdcard, and it did not boot .. so I investigated why, and I found that the device went directly to mask rom mode as soon as I gave it power

so I tried flashing armbian directly with the command ./rkdeveloptool wl 0x0 <armbian-image.img>
I can flash but the device does not boot.

also I can't in any way flash the bootloader nor do it the bakup with /rkdeveloptool db (or ul)

what am i doing wrong?

the only possibility I have at the moment is to restore the original firmware and use the sdcard with armbian-libreelect boot

April 14, 2020

14 hours ago, nokirunner said:

this source ... what do you say they could be?
https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx

https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx/tree/khadas-vim3-pie/ssv6x5x

guys, you have not commented on this, can these driver sources be useful?

April 14, 2020

5 hours ago, jock said:

You disguised very well I would have said you were American, or Mexican

Nope didn't experience anything like that, but I will definitely check. Which image are you using?

In the meantime, could you run openssl speed -multi 4 rsa and post the summary results here? It's just an openssl benchmark to compare performances.

@jock don't tell me ... are you italian too?

Well there is to say that I experienced that the system had become very fluid, but today when I turned the TV box back on it no longer booted from sdcard ...
I have to investigate why, I put the sdcard in the pc, so I have access to the files, but I don't know what to manage ...

April 14, 2020

guys, can someone explain something to me?
as soon as i installed the full firmware package from armbian comfig, the system became noticeably more responsive, almost reaching the capabilities of a real desktop, can anyone explain this to me?
have you checked ??
the reason why i installed the full signing package was because the usb wifi that i am using had no firmware installed ...

P.S. I am very happy that I managed to install the octoprint server without difficulty

April 13, 2020

@fabiobassa

2 hours ago, fabiobassa said:

Where are you located @nokirunner ?

non si era capito? :lol:

2 hours ago, fabiobassa said:

Could be a good apport finding the sources ( whole sdk ) of the android rom. Full sdk including the kernel source
Any way @jock is the coder man, I am just the hardware supplier so wait till he enlight us

I'm having fun, so I'll see if I can sift the net like a good truffle mole ..
also because the usb wifi that i currently have available armbian tells me that the firmware are not loaded ... by the way, if i take the firmware from linux for x86 and insert it in the armbian do I have any chance that it works?

this source ... what do you say they could be?
https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx

https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx/tree/khadas-vim3-pie/ssv6x5x

April 13, 2020

I believe that they have unified it and have put the x x as a reference which is a general driver for all this variants of wifi chip,
it seems to me the most logical thing.

Sign In

Forums

Store

Crowdfunding

Applications

Events

Raffles

Community Map

Posts posted by nokirunner

Important Information