Igor Posted April 27, 2019 Posted April 27, 2019 22 minutes ago, constantius said: I have build img for nano pi t3+ 5.85 armbian kernel 4.14.113 and it does not work either. I have the same memory number SEC 710. Only img from t3 without "+" is working but only with 1GB ram. Wrote some short version of this info at the download page - you should have rights for T3+ and Banana M2U, others are covered, but info was not updated.
crazystick Posted June 19, 2019 Posted June 19, 2019 I have the same problem, and another chip SEC 843... with the same board revision. Looks like the working chip might be the one-off here :-( I can also confirm as others have reported that the image for the T3 (non-plus) boots fine but only exposes 1GB memory.
crazystick Posted July 25, 2019 Posted July 25, 2019 18 hours ago, Vlado said: So, NOW it work!!! Armbian 64 2GB on T3+ Can you post a photo of your board showing memory chip P/N?
constantius Posted July 26, 2019 Posted July 26, 2019 which does kernel version work? or which armbian image do you use?
Vlado Posted July 26, 2019 Author Posted July 26, 2019 43 minutes ago, constantius said: which does kernel version work? or which armbian image do you use? It doesn't matter, work all!
constantius Posted July 26, 2019 Posted July 26, 2019 nothing is working.. i have tried The last Ubuntu 5.90 and Buster 5.91. Still segmentation fault. In fact kernel is the same...
Vlado Posted July 26, 2019 Author Posted July 26, 2019 @Igor can you please change in bl1 (file - startup_aarch64.S) 0x068 1010DE01 it also can be changed in img (may be faster way) 0x00000268 (01DE1010) In this case all people will be able to use armbian img for T3+
constantius Posted July 26, 2019 Posted July 26, 2019 Can you write where i should make a change? what does mean in bl1
Vlado Posted July 27, 2019 Author Posted July 27, 2019 13 hours ago, constantius said: Can you write where i should make a change? what does mean in bl1 it also can be changed in img on SDcard (may be faster way) 0x00000268 (01DE1010)
constantius Posted July 27, 2019 Posted July 27, 2019 it also can be changed in img on SDcard (may be faster way) 0x00000268 (01DE1010) I still dont understand... Where in img? Path to the file?
constantius Posted July 27, 2019 Posted July 27, 2019 Can anybody explaned me in which file on sd-card i should put 0x00000268 (01DE1010)? Thanks
Vlado Posted July 27, 2019 Author Posted July 27, 2019 5 hours ago, constantius said: Can anybody explaned me in which file on sd-card i should put 0x00000268 (01DE1010)? Thanks After you've written img on SDcard you should change value at address on SDcard
constantius Posted July 27, 2019 Posted July 27, 2019 sory im not developer. I dont know about you speak
NoXQS Posted July 27, 2019 Posted July 27, 2019 Does that change the memory allocation, from 1 to 2gb? Like what I mentioned in my earlier post?
Vlado Posted July 28, 2019 Author Posted July 28, 2019 14 hours ago, NoXQS said: Does that change the memory allocation, from 1 to 2gb? Like what I mentioned in my earlier post? On 7/24/2019 at 9:43 PM, Vlado said: So, NOW it work!!! Armbian 64 2GB on T3+ Yes, need change bl1, or simple way After you've written img on SDcard you should change value at address on SDcard should put 0x00000268 (01DE1010)
Vlado Posted July 28, 2019 Author Posted July 28, 2019 So, for everyone, I wrote Igor about changes. Waiting answer!
Vlado Posted July 28, 2019 Author Posted July 28, 2019 It looks like not fast process (with renew img). So, after you have recorded img on SD card you should change value (01DE1010) at this addres 0x00000268. You can do it with HEX editor.
constantius Posted July 28, 2019 Posted July 28, 2019 ok i have installed okteta. But which file have I to edit on sd-card?
Vlado Posted July 29, 2019 Author Posted July 29, 2019 20 hours ago, constantius said: ok i have installed okteta. But which file have I to edit on sd-card? It not file!!! It data on SD card! You should open your SD card at HEX editor.
Vlado Posted July 29, 2019 Author Posted July 29, 2019 @constantius just read in google how edit data on SD card
Vlado Posted July 29, 2019 Author Posted July 29, 2019 34 minutes ago, Vlado said: @constantius just read in google how edit data on SD card tierradatarecovery.co.uk/examining-the-raw-data-on-your-hard-drive-with-a-hex-editor/
constantius Posted July 29, 2019 Posted July 29, 2019 hi Are you sure that it has to be 01DE1010? When i open sdcard as the local drive it has 9 numbers not 8 ( offset ) When i open img file it has 8 numbers and i have 01DE1010 but that is empty space I use HxD
constantius Posted July 30, 2019 Posted July 30, 2019 53 minutes ago, Vlado said: Should be OK finally i have prepared mini how to .: 1. Burn Armbian image > 5.90 into micro sd-card 2. Download and install HEX editor into your windows machine https://mh-nexus.de/en/hxd/ 3. Run Hex as admin 4. Open in HEX your sd-card device ( phisical disk not logical ) 5. Set up program in make of copy disk before write 6. Change offset example to 9 numbers 7. Find and change the memory value for offset 000000260 and write 01DE1010 It Should be 000000260 01 C8 0C 10 01 66 08 50 01 DE 10 10 04 01 66 66 6. Save 7. Its done 8 Boot Nanopi T3 PLUS from micro sdcard
Vlado Posted July 31, 2019 Author Posted July 31, 2019 So, it works? will be good if write here chip model where it run my is K4B4G1646D-BCK0 (728)
constantius Posted July 31, 2019 Posted July 31, 2019 15 minutes ago, Vlado said: So, it works? will be good if write here chip model where it run my is K4B4G1646D-BCK0 (728) yes works thanks a lot i have edited this.: https://www.armbian.com/nanopc-t3-plus/ it depends from memory number my is .; SEC710 K4B4G16 - the last edition - i bought that on june 2019
Vlado Posted July 31, 2019 Author Posted July 31, 2019 2 hours ago, constantius said: yes works thanks a lot i have edited this.: https://www.armbian.com/nanopc-t3-plus/ it depends from memory number my is .; SEC710 K4B4G16 - the last edition - i bought that on june 2019 K4B4G16 last letter (D,E, ...) after char ?(BCK0)
Vlado Posted July 31, 2019 Author Posted July 31, 2019 Better to write like this: if it not work on your T3+ use this hack. Because it doesn't depend from chip modification
Recommended Posts