martinayotte
-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
2 hours ago, tkaiser said:
To avoid specific devices, eg. don't buy OPi Zero Plus 2 H5 but H3 instead since the latter is suitable for specific use cases while the H5 variant simply will suck forever.
Why H5 variant sucks ?
We first added the OPiPC2, then we added ZeroPlus2-H5 ... They are working fine.
Of course, the DRAM size is a limitation. We should also limit our expectations ...
-
13 hours ago, pfeerick said:
Not naming names. But rest assured it's no-one from this forum
I was aware : someone from another forum ...
-
On 2017-06-18 at 9:30 PM, pfeerick said:
down the throat of another "moderator" that I know someday...
Is it the one we all know ?
-
Yes, I figured out when I came back to the original thread ...
-
As @Igor said, it suppose to run fine since May 20th ...
(at least, I got my board running fine with my own build done on May 11th with manual copies of the firmware)
-
Funny guy !
Since he was the OP, he still had the right to change the thread title from "dwmac-sun8i" to "problems-with-orange-pc" within minutes after I said that he hijacked the thread ...
EDIT : oouups ! I think it is one of the moderators that decide to split the thread ...
-
(btw, you don't need to post in BOLD)
It is stricly impossible that you got an Chinese Android from Armbian build, and if you had flash the eMMC, this Android should never came up !
So, you simply did NOT succeed to flash eMMC !
(... and you didn't answered if you plugged a USB Serial and capture boot log to prove your facts ...)
(@op1tjaap is right, you seems to hijack this thread : do you known what dwmac-sun8i driver is ?)
-
This screenshot is for sure the stock Android from eMMC !
If you are not a beginner with Linux and SBC, then you should have already hooked-up an USB Serial on the Debug Serial Port !
You will see that it is booting for sure from eMMC ...
-
As I said above, pyspiflash is a good library for that. Plain "C" could achieve that too, but you will need to find library to ease development.
The protocol mentioned is only related to SPIFlashes. SPI itself doesn't have any protocol other than describing how serialization is done.
The protocols are defined by the slave devices, for example, a SPI SDCard, or a SPI LCD Display have there own different protocols, although they can be attached on the same SPI bus.
-
I think you misunderstood how SPIFlashes are working. Even if you write into /dev/spidevX-X, it doesn't write into SPIFlash.
It is simply sending the stream of data over the SPI bus, but the device, SPIFlash, doesn't understand that stream since it is not containing the proper command, since the stream is purely garbage.
For example, to write a sector in SPIFlash, it is expecting to receive the write-enable command 0x06, then block-erase 0x20 followed by block number, then byte-page-program 0x02 along with address, and the 256 data bytes.
-
How do you use "dd" for that ?
You can not use "dd" directly with /dev/spidevX-X, since it doesn't handle SPIFlash commands ...
Either you use "flashrom" utility to write whole image or use python pyspiflash library and manage sector/page erase/read/write yourself.
Don't expect been able to use it as filesystem, first because MTD partition kernel driver is probably not in Legacy builds, and second because those SPIFlash are pretty small.
Those SPIFlash are ususally present to place U-Boot bootloader to allow booting from other devices such USB Storage or Network share.
-
The OrangePiPrime is equiped with RTL8723BS WiFi module.
The driver for this module exist in Mainline 4.12, I've tried it out and it is working.
But we don't wish to waste our time trying to back port it under 4.11, so we will have to wait few weeks/months when Armbian will switch to 4.12.
-
Hoping that next time in the future, the upgrade will be less tedious...
-
For the /boot/bin.old, I will leave the question to other people, since I'm not using any Legacy builds but only Mainline ... (sorry for not providing answer here)
You said that you've replaced UUID by /dev/mmcblk0p1 and still doesn't work ... uuummm ! strange ...
Could you copy/paste your /etc/fstab ?
(I bet that perhaps you did a common mistake by leaving the word "UUID=/dev/mmcblk0p1", it should be "/dev/mmcblk0p1" alone without the word UUID)
-
Yes, I've read the whole thread, but the message "waiting for root file system" and hanging there proved that it is NOT a network issue (trust me here), but the fact that it doesn't find the rootfs partition.
There seems a mismatch between rootdev found armbianEnv.txt and the one present in /dev/fstab ...
EDIT : The fact that network is not running is simply due to that network services are not started yet since kernel still wait for rootfs to be mounted, waiting forever ...
-
This seems to look like the root partition is not found ...
You should look at the armbianEnv.txt to see if rootdev UUID is matching with the one from your SDCard.
-
If you are playing with SBCs, you will use them often.
Personally, I've more than 6 of those, since sometime I need to debug multiple things else without pluging/unpluging them all the times.
-
1 minute ago, Aux said:
A good idea, but for serial debug session has no tools
What do you means ?
If you don't have any USB-Serial adaptor, it is probably good time to purchase one, they are less than $1.
-
By using picocom or putty on serial debug, and copy/paste the output ...
-
Also, BT enable handling (BT-WAKE-AP and BT-RST-N) in DT need to be added.
(It is not currently present, because no body added it)
-
You can not use "gpio-keys" and "plain sysfs gpio" at the same time. You need to choose on or the other.
With "gpio-keys", you can check events with "evtest".
To use your "gpio_watch" application, you will need to remove all the things you've added to DTS.
-
How this new OPi.GPIO library is related to SPI ?
-
Ah ! Ok ! I thought at first it was on Mainline. But yes, the above link should make it work.
-
You should see a /dev/mmcblk0 and /dev/mmcblk0p1.
Then, you can mount it using "mount /dev/mmcblk0p1 /mnt" and access file tree in /mnt.
Bluetooth on Orange Pi Win Plus
in Allwinner sunxi
Posted
No, Bluetooth pins are not even added in the DeviceTree.