martinayotte
-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
As Zador said : SD (MMC0) > eMMC (MMC2) > SPI NOR > FEL
So, if you wish to boot from USB using SPI-NOR, you need to get rid of any u-boot sectors on both SDCard and eMMC.
-
... except, of course, if the u-boot sectors have been erased from sdcard and completely re-formatted ...
-
Then, I'm running out of ideas ...
In the mean time, I can only suggest to purchase some USB-TTL (3V compatible) dongles to compare behaviours.
-
This means that OPi TX is Ok, but RX isn't ...
How do you power the MAX3232 ?
If it is with 5V, you will need to add a voltage divider on RX output of the MAX, because OPi is 3.3V.
-
remove the gateway ...
-
11 hours ago, Luis Daniel said:
it uses MAX3232
Those are RS232-TTL converters. This means that your PC has a real RS232 DB9 port, and you're actually use it with a converter, right ?
If you're using a USB-TTL dongle, you don't need such converters, since they are already TTL level.
-
-
Your problem's description is not clear ...
Can you show us what your test.py contains ?
If you have utf-8 issues, you probably need to do a "export PYTHONIOENCODING=UTF-8" before starting your script.
-
Yes ! Your second card doesn't have u-boot !
You should do a 'dd' between cards but only the first 1M.
Then, with 'fdisk' on the new card, delete partition and re-create it to match size of the card, followed with 'mkfs.ext4' for reformatting.
After that, you can tar or rsync the rootfs filesystem.
-
Can you tell us what kind of crappy switch it is so that people won't struggle with same model.
-
Several computers from that time, although their CPU limited to 64K due to 16 bits address bus, use "memory bank switching".
One of the most known example was Apple III, but some others too in the unix word such as Cromemco with as much as 512K
-
1 hour ago, darethehair said:
e.g. turn off the serial output so that it would not interfere with a GPS attached on the UART.
That's because you used the debug serial. You should use another serial than that one, but unfortunately, it seems that the CHIP has only that one exposed on header.
-
11 hours ago, darethehair said:
but does an Orange Pi PC Plus *really* require separate heatsink?
Nonne of my OPiPC+ has one ...
-
OrangePiPC+ is way much better than CHIP. One of the reason is that CHIP doesn't use eMMC but plain NAND.
-
spidev0.1 means SPI0 with CS1
spidev1.0 means SPI1 with CS0
-
It looks like portrait orientation instead of landscape ...
-
3 hours ago, raschid said:
Thank you. That will certainly help people willing (and able) to compile their own kernels.
This commit should allow that : https://github.com/armbian/build/commit/cb48540d4a230e1ef0dfc507f0e4ac165d37ee18
(I've done quick try and it worked for me)
-
1 hour ago, TonyMac32 said:
There are a couple magic values, the U-boot SPL, and a device tree that get located before the main U-boot is loaded, but the maskrom uses hardware block device addressing, it does not use the partition table
Those that means that we can later have a 1 partition scheme instead of this ugly 7 one ?
-
Oh ! You're right ! Back in May, when I've done the job, and when we decided to remove that support, I've never committed the patch fix, it is sitting on my tree :
diff lib/patch/kernel/sun8i-dev/add-xradio-wireless-driver.patch.disabled lib/patch/kernel/sun8i-dev/add-xradio-wireless-driver.patch 1902c1902 < @@ -0,0 +1,880 @@ --- > @@ -0,0 +1,884 @@ 1922a1923,1926 > +struct sched_param { > + int sched_priority; > +}; > + 1948d1951 < + struct sched_param param = { .sched_priority = 1 }; 1963a1967 > + struct sched_param param = { .sched_priority = 1 }; 12076c12080 < @@ -0,0 +1,266 @@ --- > @@ -0,0 +1,267 @@ 12092a12097 > +#include <linux/module.h> 13601c13606 < + ieee80211_cqm_rssi_notify(priv->vif, cqm_evt, --- > + ieee80211_cqm_rssi_notify(priv->vif, cqm_evt, rcpiRssi,
I will probably commit it soon, but leaving it disabled ...
-
6 hours ago, raschid said:
Would you update the actual driver code to your build as well? It seems the driver code in the current add-xradio-wireless-driver.patch.disabled is still pre 4.11.
No needs, as I've done the changes already almost 2 months ago to match 4.11 API.
-
For the changes to DTS, maybe I can look to append them directly into the add-xradio-wireless-driver.patch.disabled when I will get chance.
-
If your SDCard is mounted as Read-Only because of some corruptions, then new password just entered is not save, therefore SDCard is unusable.
You have to re-write the SDCard with Etcher tool ...
-
1 minute ago, zador.blood.stained said:
My opinion here would be "definitely no"
Ok, then ... I will keep it as private build...
-
18 hours ago, zador.blood.stained said:
This type of crashes (aes-arm related) should have been fixed yesterday by this commit, so I would suggest to rebuild the kernel.
Yes, thanks Zador to have figured out ! I've tested it on my side too, and right, it fix the xradio perfectly !
Maybe we should re-enabled it in the nightlies ?
orange pi pc - which USB sata bridge
in Beginners
Posted
What "lsusb" is telling you ?
What kind of SATA Bridges do you have ?