martinayotte
-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
The simplest way is to call those commands from inside /etc/rc.local (before the exit 0)
-
Zador, if you remember, I've committed a patch few days ago to get large transfers under 4.9.
-
It is enabled by default as you can see with "console=ttyS0"
If you don't see any output, you should suspect your USB-TTL.
Be aware that your USB-TTL dongle should be 3.3V compatible.
-
Missing data is because Github had severe problems yesterday ...
Yes, yesterday Github was returning 504 during several hours, for any kind of requests, except for Web accesses.
-
@martinayotte
Just did a git pull and used compile.sh to create a new mainline image for orangepizero. The half duplex is still there. I assume you also used the compile.sh script for your images. If not let me know, I can try your way as well.
Yes, it was my own builds done with compile.sh
-
BTW, From this other thread, I've figured out that resolution change is already available from Mainline using another method :
-
There is a thread where someone tweak the kernel to get this functionality :
https://forum.armbian.com/index.php/topic/1558-w1-therm-driver-modifications/#entry12058
But it seem that he never completed the task to provide actual patch for Armbian build.
Looking at kernel history, I saw that someone else done it a different way :
https://github.com/megous/linux/commit/0a19f129d71f18e73249d54de96c835186b8607e
It should be done like :
echo 12 > /sys/bus/w1/devices/28-000005a2fac5/w1_slave
But comments say that this change is volatile and will be reset at next power recycle :
Writing a value between 9 and 12 to the sysfs w1_slave file will change the precision of the sensor for the next readings. This value is in (volatile) SRAM, so it is reset when the sensor gets power-cycled. To store the current precision configuration into EEPROM, the value 0 has to be written to the sysfs w1_slave file. Since the EEPROM has a limited amount of writes (>50k), this command should be used wisely. -
@dran, I've several kind of boards, but my W1 is currently on my OPiPlus2E.
But I don't see why it would be different on my OPiZero, other than using different GPIO pin.
(I will probably try it eventually)
-
My OPiZero is in full duplex, either with last week's build or today's build.
-
Ah ! I didn't know ...
Of course, I'm run my board at normal frequency, so I didn't faced the issue.
-
@Radim, Where do you see in that link that is a kernel bug ?
-
Then, you need to decompile DTB into DTS, edit the DTS to change them to "okay", recompile DTB from DTS.
-
Yes, sorry for the typo ...
I means :
cat /proc/device-tree/soc/serial@01c28400/status cat /proc/device-tree/soc/serial@01c28800/status cat /proc/device-tree/soc/serial@01c28c00/status
it should not get empty, check carefully, because it doesn't do \r\n, so it is appearing just before shell prompt, it is "okay" or "disabled", no other values.
-
Well, there are several manual steps to accomplish that.
First, you need to make sure the SPIDEV is enabled in DT, either in main DTB or by using DT Overlay.
You need to grab "flashrom" sources, tweak the flashchip.c file for making sure the SPI transfer size ".page_size" is 64 for the chip you are using, then compile.
Then, you are ready for Flash upload (adjust the 4096 according to your flash size) :
dd if=/dev/zero count=4096 bs=1K | tr '\000' '\377' > spi.img dd if=/usr/lib/linux-u-boot-dev-orangepizero_5.24_armhf/u-boot-sunxi-with-spl.bin of=spi.img bs=1k conv=notrunc flashrom-0.9.9/flashrom -p linux_spi:dev=/dev/spidev0.0 -w spi.img
In the future, we will probably provide a script that does all the tasks automatically.
-
-
Just a suggestion : maybe it is better to add small PCA9685 board attached to an I2C bus, you will get 16 PWM 12bits channels for few bucks.
-
Your DTS looks Ok.
Did you recompile it into DTB and reboot ?
Still no new tty ?
Strange ...
What those commands showing ?
cat /proc/device-tree/soc/serial@01c28400 cat /proc/device-tree/soc/serial@01c28800 cat /proc/device-tree/soc/serial@01c28c00
it should print "okay" for each one ...
-
Can you shows us the DTS that you've edited ?
-
I would rather try with a MOSFET, 2N7000 for example, because when IN pin is HIGH at 3V it maybe still enough to keep the opto-coupler conducting.
If you don't have a MOSFET in stock, you can use a NPN transistor (2N3904 or 2N2222 for example) with resistor on its base.
EDIT : Oh ! googling for schematics, I found some boards that has the IN reversed compared to other boards, like this one http://www.elecfreaks.com/store/images/product_images/Breakout/Relay/BK_SRD_03.jpg
(this one is reverse compre to previous : https://forums.unrealengine.com/attachment.php?attachmentid=119903&d=1480742998)
When I've asked you to try IN pin to ground, was it really to GND that works ? because the link I've post here is the reverse, it is required 5V on the IN pin.
-
Oh ! I missed looked the picture in first place : Is it a 12V written on the relay ?
If it is the case, then, 5V is not enough for it ...
(... and I would still use a MOSFET ...)
-
Then, I presume you won't have choice to add MOSFET to drive the IN pin.
-
Maybe I misunderstood something : does a separate LED, without board attached, is flashing or stays always On ?
When board is attached, does it own LED flashing or stays always On ?
-
So, if the LED is flashing/working, then you need to figure out if the relay board is Ok.
Did you tried the board alone by grounding the IN pin ?
if it work, do you have a multimeter to measure how much current it takes ?
if more than 10mA, maybe your need to add a MOSFET between GPIO and the IN pin.
-
I don't see any thing wrong with the setup.
Did you tried connecting an LED directly on PA10 without the relay board attached ?
Using OPI pc + for Open Glider Project - unable to add user
in Allwinner sunxi
Posted
edit /etc/rc.local with your favorite editor and add your required commands the before the line showing "exit 0".
Maybe your commands will need to be inserted with full path of the application location, such as "/home/andrej/openglider/ogn-rf /home/andrej/openglider/LJNMT.conf" and "/home/andrej/openglider/ogn-decode /home/andrej/openglider/LJNMT.conf".
And if one of those commands are not starting in background process, add an ampersand "&" symbol at the end of the line.