Joey, Yes. Allwiner produces SoCs which are based on ARM architecture. Just as Marvell(plugs) Amlogic, Broadcomm ( rPi), Mediatek, TI, .... SoCs are ARM.by bodhi - Off-Topic
syong Wrote: ------------------------------------------------------- > Correction! Just found the pin to be pulled up is > the TX instead of RX. My excuse is my USB2UART is > mislabeled. > > So shorting to 3.3v is not recommended although it > might work. This is real life, not ideal as what I > thought. > > Hope you did not fry anything. I didn't. :)by bodhi - Off-Topic
Hi xssa, The SATA 2nd port LED trigger is already supported in the kernel with my patch for the SATA driver. But the T5325 has only one exposed SATA. Now that you and CV have the 2nd SATA :) However, it seems that the T5325 SATA LED is hardwired (I did not need to do anything in the DTS for it to blink). It is good that you've verified that hardwired only to the SATA port 0! I donby bodhi - Debian
jay Wrote: ------------------------------------------------------- > hi, > anyone has hints to enable ssh? > i found a new pogoplug pro and tried to enable > ssh. > there are just open ports at 80 3333 and 3334. > i tried to register with my.pogoplug.com and the > device is found. > so i registered it, but i do not receive the > email. > the device is visiby bodhi - Debian
> Android 5.0 (Lollipop). So, it must be a 64-bit > 4-core CPU (sorry no brand/model of the CPU > found). This RCA-Viking-Pro-10.1 is 32-bit Mediatek MT8127, ARM Cortex-A7.by bodhi - Off-Topic
bobafetthotmail, I've read your tutorial. It's packed with well explained steps and looks like mostly it's going to work fine. Note: I've not looked closely at step 5 yet. 1. You mentioned 1.5MB reserved for u-boot and envs. This is not going to work with our u-boot in which the envs are defined at 0xc0000, which is 768K location. 2. To accomodate bad blocks, you shoby bodhi - Off-Topic
Now that I have some free time to get back to this subject for the new OXNAS kernel. I'm afraid the bad news is I'm going to wait out longer before building the OXNAS kernel. Since the 4.1 is a LTS kernel, it is basically 1 more year before it become obsolete. This was my conlusion after researching. There is an inherent problem with SMP in the ARM11MPCore, that people have been tryiby bodhi - Debian
rr4m, Thanks for the info. Do you have a serial boot log? can you post it here? BTW, GPIO1 11 is 43 :)by bodhi - Debian
Quote- ------------------------------------------------------------------------- Debian Security Advisory DSA-3566-1 security@debian.org https://www.debian.org/security/ Alessandro Ghedini May 03, 2016 https://www.debian.org/security/faq - ------------------------------------------------------------------------- Packageby bodhi - Debian
Lennong, Anything abnormal happened when you flashed new u-boot and u-boot envs? do you have a log for that? Regarding the bad blocks, it is really not a problem if the NAND has these bad blocks on its list. I would have had a good workaround for you even with the bad blocks in those areas. But if you scrubbed NAND, and they disappear then I'd say that your NAND right now is not relby bodhi - uBoot
This is a steal for $10! however, I've read somewhere the these 2 phones have CDMA (most likely with old Qualcomm chip). Is that true?by bodhi - Off-Topic
Thanks Gravelrash!by bodhi - Off-Topic
Please see Kodi announcement.by bodhi - Off-Topic
Lennong, Boot with USB rootfs and see how SATA behaves in Debian. It could be just the SSD. Did the stock u-boot detect this SSD OK before?by bodhi - uBoot
CV, Getto style or not. Good works :)by bodhi - Debian
Joey, Now that you've rooted it. You can try login through telnet or ssh.by bodhi - Off-Topic
> Finaly got it! > Booting kernel-4.4.0 with embedded latest > kirkwood-t5325.dtb and its uInitrd in /boot and > viola!!! rootfs on /dev/sdb4 mounted as expected > with label=rootfs. Glad it works for you :) FYI, also for the benefit of others who came from Arch or OpenWrt or a different distro. If you've followed the instructions in the Debian kernel/rootfs thread cby bodhi - Debian
xssa Wrote: ------------------------------------------------------- > There is bootlog: > > ## Booting image at 00200000 ... > Image Name: Linux-4.5.0-kirkwood-tld-1 > Created: 2016-04-24 23:01:46 UTC > Image Type: ARM Linux Kernel Image > (uncompressed) > Data Size: 3205937 Bytes = 3.1 MB > Load Address: 00008000 > Entry Pby bodhi - Debian
> > I know this isn't an Android forum (but you > did bring it up and I did buy one) I did not :) Rooting it first. That's the hard part.by bodhi - Off-Topic
xssa, IDE rootfs should work. Can you post your serial console boot log? Or you can install new u-boot: http://forum.doozan.com/read.php?3,26562. Try kwboot first and see if it all works for you. Please, pay attention to the mtdparts in u-boot installation. If you have changed it to boot latest rootfs, then it is easy. If not, slight adjustment is needed in the instruction (I need to revby bodhi - Debian
> And the question is: Why does the 88F6281 kernel > doesn't boot on the 88F6702, do I need to > recompile it? If so, what compilation parameters > should I edit? No need to compile. See the rootfs and kernel here: latest Kirkwood kernel builds and rootfs What you have is covered under the NSA310S and NSA320S. They are identical and have 6702 SoC. What box do you haby bodhi - uBoot
notoneofmyseeds, > But this time, I did not do after extracting: > sync > sync > sync > > Could this be the problem? If so, how do I > proceed, please? Not likely the reason. One possible cause is how you created the rootfs. You might have not followed the instruction closely enough. For example, If you did not copy and paste the instruction, but having to chaby bodhi - Debian
hecatae Wrote: ------------------------------------------------------- > finally got this working, thank you > > I have a 3tb gfh hdd, is there a recommended > partitioning scheme? Depending on your needs. But a simple parttioning is having 8 or 16GB for rootfs and the rest for data. The largest rootfs I ever have is about 6GB. That's because I kept all the kernel I eveby bodhi - Debian
So SATA boot is like this: load_initrd=ext2load ide 0:1 0x1100000 /boot/uInitrd load_uimage=ext2load ide 0:1 0x800000 /boot/uImage sata_boot=ide reset; run load_uimage; run load_initrd; bootm 0x800000 0x1100000 bootcmd=run usb_make_boot_args ; run sata_boot; resetby bodhi - uBoot
Damian, You've already found the address for zimage and uinitrd: #mtd2: 00228000 00004000 "zImage" #mtd3: 00300000 00004000 "initrd" However, I would not recommend to do this (you don't need to run the kernel in NAND). To boot with SATA, envs need to change to use ide command, and then ext2load as usual.by bodhi - uBoot
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > Both have bluetooth and wifi. > > By WiFi if you mean microwave cell tower access > yes, but only one has b, g and n, unless I read > that wrong. The other only had bluetooth. > Look at all infoby bodhi - Off-Topic
> But the phones on sale, choice between WiFi or > bluetooth, not both. Which is more important you > think? Both have bluetooth and wifi.by bodhi - Off-Topic