martinayotte
-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
According to A20_Bananapi_Schematic.pdf, Yes !
But as Zador mentioned, do you have a PullUp resistor on this GPIO ?
How your DTS looks like ?
-
1 hour ago, B3RN0UT said:
E.g for PD25 this would be ( 4 - 1) * 32 + 25 = 121 + 25 = 146 (since 'd' is the 4th letter).
Nope ! it should be read as :
PD25 this would be ( 4 - 1) * 32 + 25 = 96 + 25 = 1211 hour ago, B3RN0UT said:I'm unsure what exactly is the mentioned Pin
No, it is not header pin number but GPIO name
-
2 hours ago, B3RN0UT said:
I have to add again +25
Why ? This is not true ... Rely only on the linux-sunxi formula ...
-
@Igor, is Steven planned to ship us Dev's samples ?
-
Zador is right, you don' t need SPIDEV overlay for ENC28J60, but you need that custom overlay ...
-
In Armbian Mainline, the SPI is enabled using an overlay. For that you need to add "overlays=spi-spidev" in /boot/armbianEnvt.txt and then reboot.
For longsleep images, I think you need to enable the SPI simply by changing 'status="disalbed"' to 'status="okay"' in its DT.
-
Effectively, CONFIG_USB_SERIAL is not set at all in linux-odroidc2-dev.config.
But that could be added easily ...
-
Yes, for PC, https://github.com/duxingkei33/orangepi_PC_gpio_pyH3
For Zero, there someone who forked it and adjusted the mapping.h for few Zero pins differences, but I can't remember the link.
EDIT : I've finally found it for Zero : https://github.com/nvl1109/orangepi_PC_gpio_pyH3
-
Good !
Now you should be able to place files into that partition ...
-
The output you've posted earlier :
root@pine64:~# fdisk -l /dev/sda Disk /dev/sda: 28.9 GiB, 31043616768 bytes, 60632064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytesIt seems incomplete since it doesn't show any partition ...
With proper partitioning, it should look like :
root@pine64:~# fdisk -l /dev/sda Disk /dev/sdb: 29.8 GiB, 32026656768 bytes, 62552064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000c3d6a Device Boot Start End Sectors Size Id Type /dev/sda1 2048 61926527 61922432 29.5G 83 Linux -
The output of "fdisk -l /dev/sda" doesn't show any partition ...
But strangely, the previous log mentioned you have /dev/sda1.
Are you sure you provided the complete output of fdisk ?
-
/dev/sda seems to be present !
Did you check its partitions with "fdisk -l /dev/sda" ?
-
The best place to find docs is always linux-sunxi :
https://linux-sunxi.org/Table_of_allwinner_based_boards
https://linux-sunxi.org/Xunlong_Orange_Pi_Zero
https://linux-sunxi.org/Xunlong_Orange_Pi_PC#Variants
-
OPiZero and OPiZeroPlus2 are not the same, therefore schematics are not the same and UART2 header pins neither...
http://linux-sunxi.org/Xunlong_Orange_Pi_Zero_Plus_2
UART1 is not exposed on header since it is connected to BlueTooth.
UART2 : TX=10, RX=12, CTS=15, RTS=22.
-
Obviously, I've missed the clearly visible 8198FTV, I was searching for the AP6212A
-
They remove the eMMC and the WiFi to leave room for the ETH, but they didn't care using a new name for the board ...
-
If you have an USB-TTL Serial dongle attached, it would be easier to figure out since you will see all the booting phase logs.
-
-
The H3 SPI has 64 bytes FIFO, so where did you find that it is 16 bytes ?
Why do you think that your issue is coming from FIFO size since smart card reader usually has short messages ?
In Mainline, we are applying a patch for interrupt driven FIFO that let manage messages up to 65535 bytes.
-
Yes, except that for H5, you need the SUNXI_PIO_BASE "unsigned long" tweak I've mentioned ...
-
With a little search, you would have found that : http://linux-sunxi.org/GPIO
In summary, all SoC from AllWinner use the same formula :
(position of letter in alphabet - 1) * 32 + pin numberFor OpiPC2 specific, look at the schematic :
http://linux-sunxi.org/File:ORANGE_PI-PC2-V1_2_schematic.pdf
For Python library, use https://github.com/duxingkei33/orangepi_PC_gpio_pyH3
But for any 64 bits, you need to fix a small issue : change all references to SUNXI_PIO_BASE in gpio_lib.h/gpio_lib.c from "unsigned int" to "unsigned long" to have a 64 bits pointer.
-
By looking at the bytes pattern you've posted above, it is really looking strange with multiples duplicated bytes.
Something must be wrongly connected ...
-
Isn't that reversed : it is the lower that was working but not the upper ...
This is now fixed with this commit : https://github.com/armbian/build/commit/cc4e1ccc8e236b0a3eadabaa9c7b74af43065512
-
2 hours ago, chwe said:
15/16 are the pins from opi 0 maybe this confused him..
Not really, because he was asking for OPiOne and before answering about STATUS_LED and MUTE, I've verified in the OPiOne schematic.
Which card choose to deploy an educational open source OS in schools ?
in Off-topic
Posted
Yes, The OPiPC+ is one of my favorite, one of the reason is price/feature ratio, having eMMC is really nice.
I'm also using those in my daily job.
But, all my boards are headless, so I can't give hint about 3D stuff.