moonki123
-
Posts
22 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by moonki123
-
-
[twi_para]
twi_port = 0
twi_scl = port:PA11<2><default><default><default>
twi_sda = port:PA12<2><default><default><default>It seems to have been automatically changed since the update
but still i can't use 0x68
-
@nopnop2002
i try like you but i can't see i2c address
it's not working
i want to try another way...
-
Um "i2cdetect" is not showing the devices
so it's same result ...
also A few months ago an orange pi zero succeeded in connecting i2c but now Orangepi Zero showed same result as the nanoPi neo air
Is there no other way to use another address?
-
no i didn't PullUps on my bus but i connected MPU-6050 Vcc Pin - NanoPi Neo Air Vcc 5v in...
oh... if i use NanoPi Neo Air 5v(IN) i have to change 3.3v(OUT)? or 5v(OUT)?
and i'm not using pre-fab module
-
I do not know if the peripherals I think are right, but let me tell you.
my peripherals is mpu-6050(accleration + gyro-sensor)
Now i using H3 chip and i don't know manufacturer
my processor is ARMv7 Processor rev 5 (v7l)
hardware is sun8i
i used this Wiring - git clone git://github.com/wertyzp/WiringNP
and my gpio -v is
Copyright (c) 2012-2014 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warrantyBanana Pro Details:
Type: Model A, Revision: 1.2, Memory: 1024MB, Maker: LeMakerThat's all I know.
-
i want to use 0x68 address
How can I use the peripherals I want?
-
thanks your reply
you mean change this part
[twi0_para]
twi0_used = 1 // (enable)
twi0_scl = port:PB00<2><default><default><default> // i think Hardware pin number
twi0_sda = port:PB01<2><default><default><default> // also pin number
but i want to use another i2c address
now 0x48 address be used so i want to use another one
so your method is not match to this question so what should i do?
-
uname -a : Linux nanopiair 3.4.113-sun8i #18 SMP PREEMPT Thu Jun 15 02:16:06 CEST 2017 armv7l armv7l armv7l GNU/Linux
i installed i2c-tools, libi2c-dev, python-smbus
but if i try like this
i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --i can't use i2c
gpio load i2c
-> gpio: Unable to load i2c-sunxi
so i tried like this
so i add overlays = i2c0 i2c1
/boot/armbianEnv.txt and /etc/modprobe.d/blacklist.conf(checking i2c-bcm2708 and i2c-dev)
add from /etc/modules -> i2c-bcm2708, i2c-dev
Eventually I could not find a possible i2c number
so what should i do?
please tell me detail ~
-
Hi i wonder why ISR result is strange
first i test in orangepi zero Plus H5
that result is repeated infinite recall function
summary - recall infinite function if i input interrupt pin(button)
i test
result repeat
second i test in orangepi zero(H2)
that result is only called function once
#include <wiringPi.h>
#include <stdlib.h>
#include <stdio.h>
#include <unistd.h>void signal_both(void){
printf("Signal Both\n");
}void signal_falling(void){
printf("Signal Falling\n");
}void signal_rising(void){
printf("Signal Rising\n");
}int main(int argc, char **argv){
int mode=INT_EDGE_BOTH;
int pin = 0;
if(wiringPiSetup() == -1) {
printf("wiringPiSetup Error\n");
}
if (argc == 2) {
mode = atoi(argv[1]);
}
if (argc == 3) {
mode = atoi(argv[1]);
pin = atoi(argv[2]);
}
pinMode(pin,INPUT);
printf("pin=%d\n",pin);
if ( mode == INT_EDGE_BOTH) {
printf("INT_EDGE_BOTH\n");
wiringPiISR(pin, INT_EDGE_BOTH, signal_both );
} else if ( mode == INT_EDGE_FALLING) {
printf("INT_EDGE_FALLING\n");
wiringPiISR(pin, INT_EDGE_FALLING, signal_falling );
} else if ( mode == INT_EDGE_RISING) {
printf("INT_EDGE_RISING\n");
wiringPiISR(pin, INT_EDGE_RISING, signal_rising );
}
while(1) {
sleep(10000);
}
return 0;
}can you explain why result is different?
code is same in Orange Pi Zero and Orange Pi Zero Plus H5
-
Thank you for always kindly responding.
have a good day~
-
Hi martinayotte i have good news
i successed uart communication, thank you very much
but i wonder why another ttyS1 or ttyS3 pin is not working
i heard orangepi zero provide 3 uart pin
anyway i add "overlays=uart1 uart3" after checking uart2
and also i tried picocom -b 115200 /dev/ttyS1 and picocom -b 115200 /dev/ttyS3
then ttyS1 note can't use and ttyS3 can use
so i tried ttyS3
- connect a jumper pins(i tried 10, 11 40 because GPS just send Data(Tx))
- nothing happen
- orangepi zero plus H5 provide just 1 uart pin?
thanks for your advise and care
i always respect all developers ^^
-
I erase param_uart1_rtscts=1 and i test serialRead.c
I'm use example - serialRead.c -> gcc -o test serialRead.c -lwiringPi -lpthread
sudo ./test
-> nothing to receive ... (I tried GPS(TX) - OrangepiZeroPlusH5(RX) - (RXD3, RxD2, RxD1 - I tried all pin)my source is just put out receive data when data is received
#include <stdio.h>
#include <string.h>
#include <errno.h>
#include <wiringSerial.h>int main ()
{
static int lsize = 0;
int fd ;
int rdata = 0;if ((fd = serialOpen ("/dev/ttyS3", 9600)) < 0) // i tried all ttyS1, ttyS2, ttyS3
{
fprintf (stderr, "Unable to open serial device: %s\n", strerror (errno)) ;
return 1 ;
}for (;;)
{
rdata = serialGetchar(fd);
if(rdata>=0)
putchar(rdata);fflush(stdout);
}
}> gpio readall
my orangepi zero Plus H5 - GPIO here
+-----+-----+----------+------+---+-Orange Pi+---+---+------+---------+-----+--+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
| | | 3.3v | | | 1 | | 2 | | | 5v | | |
| 12 | 8 | SDA.0 | ALT5 | 0 | 3 | | 4 | | | 5V | | |
| 11 | 9 | SCL.0 | ALT5 | 0 | 5 | | 6 | | | 0v | | |
| 6 | 7 | GPIO.7 | ALT3 | 0 | 7 | | 8 | 0 | ALT3 | TxD3 | 15 | 13 |
| | | 0v | | | 9 | | 10 | 0 | ALT3 | RxD3 | 16 | 14 |
| 1 | 0 | RxD2 | ALT3 | 0 | 11 | | 12 | 0 | ALT3 | GPIO.1 | 1 | 110 |
| 0 | 2 | TxD2 | ALT3 | 0 | 13 | | 14 | | | 0v | | |
| 3 | 3 | CTS2 | ALT3 | 0 | 15 | | 16 | 0 | ALT3 | GPIO.4 | 4 | 68 |
| | | 3.3v | | | 17 | | 18 | 0 | ALT3 | GPIO.5 | 5 | 71 |
| 64 | 12 | MOSI | ALT4 | 0 | 19 | | 20 | | | 0v | | |
| 65 | 13 | MISO | ALT4 | 0 | 21 | | 22 | 0 | ALT3 | RTS2 | 6 | 2 |
| 66 | 14 | SCLK | ALT4 | 0 | 23 | | 24 | 0 | ALT4 | CE0 | 10 | 67 |
| | | 0v | | | 25 | | 26 | 0 | ALT3 | GPIO.11| 11 | 21 |
| 19 | 30 | SDA.1 | ALT4 | 0 | 27 | | 28 | 0 | ALT4 | SCL.1 | 31 | 18 |
| 7 | 21 | GPIO.21 | ALT3 | 0 | 29 | | 30 | | | 0v | | |
| 8 | 22 | GPIO.22 | ALT3 | 0 | 31 | | 32 | 0 | ALT3 | RTS1 | 26 | 200 |
| 9 | 23 | GPIO.23 | OUT | 1 | 33 | | 34 | | | 0v | | |
| 10 | 24 | GPIO.24 | ALT3 | 0 | 35 | | 36 | 0 | ALT3 | CTS1 | 27 | 201 |
| 20 | 25 | GPIO.25 | OUT | 0 | 37 | | 38 | 0 | ALT5 | TxD1 | 28 | 198 |
| | | 0v | | | 39 | | 40 | 0 | ALT5 | RxD1 | 29 | 199 |
+-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+----------+------+---+-Orange Pi+---+------+----------+-----+-----+
my armbianEnv.txt
add -> overlays = i2c0 i2c1 uart1 ttyS1
I think wiring is not problem...
help me...
-
Hi Igor~ i success connect i2c pin !
just add overlays=i2c0 i2c1 like this ... in cd /boot -> armbianEnv.txt
but! now i can't connect to uart pin...
i tried to add -> overlays=uart1 like this and
param_uart1_rtscts=1
but it wasn't work
i check dmesg | grep ttyS then
[ 1.635332] console [ttyS0] disabled
[ 1.655531] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 27, base_baud = 15 00000) is a U6_16550A
[ 1.655587] console [ttyS0] enabled
[ 1.676199] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 28, base_baud = 15 00000) is a U6_16550A
[ 1.696663] 1c28c00.serial: ttyS2 at MMIO 0x1c28c00 (irq = 29, base_baud = 15 00000) is a U6_16550Aso what should i do?
cd /dev/ -> in there i have tty0 to ttyS0~ttyS3
-
Igor!
now i reference https://docs.armbian.com/User-Guide_Allwinner_overlays this site
during i try Using custom overlays part, i have question
in there they offer some example overlays
example overlays is based on H3 chip
but Orangepi Zero Plus H5 is based on H5 chip
so i think, it is not match
what do you think?
-
Ok I'll try thanks!
have a good day
-
i'm not well in armbian knowledge
so.. just wait to stable becoming Images?
Afterwards Other developers make enabling I2C?
-
Hello Today i download Orangepi Zero Plus H5 Armbian OS
then i tried gpio - i2c test
but it's not work ...
I did like this
sudo apt-get install python-dev
sudo apt-get install python-smbus
sudo apt-get install i2c-tools
sudo apt-get install libi2c-dev
sudo nano /etc/modules -> add - i2c-dev, i2c-bcm2708
and i refer https://github.com/longsleep/linux-pine64/pull/17/commits/d915860a9c57a9a3ab3df7775c942ca205c8e16d this site
i think adding I2C configs is not problem
so give me some advice
-
is it not good ? BSD ?
now i'm using Ubuntu16.04 OS download in Orangepi Site
-
before i installed libi2c-dev, i2c-tools, python-smbus
anyway i tried add overlays but it's not work and the message is Could not open file '/dev/i2c-0' or '/dev/i2c/0': NO such file or directory
i can't see i2cbuseswhat should i do?
-
Hi martinayotte
I have question ! can you reply for me?
I can't use i2c in orangepi zero plus H5
My OS is Ubuntu
I heard you made your own style kernel so you can detect i2c pin
Can you share your method ?
NanoPi Neo Air - Unable to load i2c-sunxi
in Allwinner sunxi
Posted
Do you mean arm board?
I checked the mpu-6050 at Aduino_mega
But the mpu-6050 did not matter
I have raspberry pi, orangepi zero and orangepi zero plus
but also same symptom in orangepi zero(not working I2C)
before It worked in orangepi zero using I2C device
It seems to be caused by an update issue