-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
They should add some "apt-mark hold <packages>" into their images, that would prevent bad upgrades ...
-
It seems that you took the image from there : https://archive.outernet.is/images/Dreamcatcher Armbian/
They probably didn't do their own testing properly according to the log you've provided : "File not found"
-
Do you have any USB-Serial dongle connected to debug ?
-
Thanks, Zador ! :-)
-
28 minutes ago, Igor said:
If you switch to Theme -> Default ?
Excuse-me my ignorance, but where can I switch theme ?
-
Yes, you can disable peripherals in an overlay by changing their status to "disabled".
But you won't be able to change SPI pins ...
-
1 hour ago, mantouboji said:
It seems the usb0_vbus pin (PL2) not active to open the power.
Good catch !
It was there when we were under 4.10 !
I will prepare a patch ...
-
I not seeing old quotes too, even if I'm logged in ...
-
There is no real PMIC on OPiZero, this means the power supply still plugged on the SoC, even after shutdown command.
-
You're lucky that you didn't destroyed those GPIOs ...
You're better use some MOSFET or other circuit to drive this relay board.
-
The way you are reading the serial port is ugly since you try to read(1000) without even checking if there is something to read, and yes 0.1ms is waste of time, especially if serial is empty, you should make it longer.
You should is serial.inWaiting() > 0 to check if at least one char has come in...
-
Do you have any USB Serial to connect and capture log during your Mainline boot ?
-
Their isn't much diffs bewtween H2+ and H3.
But as I stated above "If your wish is to have a LED reflecting the fact that the chip is been resetted but no single byte read from SDCard, your only solution is to connect that LED to reset, but that doesn't mean much since a reboot won't make that LED turned on." , I don't think your wishes can be achieve ...
-
Personally, I don't feel that Armbian PC2 development is stalled !
If you have any enhancement to provide to Armbian, please, submit a PR !
-
Although I didn't raad the whole thread and links, why are you trying to do ssh on port 2222 while standard port is 22 ?
-
I'm glad to see that it every thing worked out !
I have some of those MCP2515 modules on my desk since more than a month, but never got chance/time try them out ...
-
Normally, any GPIO Inputs use internal PullUps and the switches are pulling them to GND.
But, about ACPI, I doubt the driver is included in a Legacy build.
As a workaround, you can have an application that scan the button and then call "halt" when button is pressed.
-
The UU at 0x48 looks strange, because I don't have that on my OPiZero with Mainline.
UU means that it is in use by a kernel driver ...
-
I'm not understanding your last post ...
Your screenshot maybe only confused me where to look at ...
-
Why don't you choose another GPIO for IRQ ? You don't have any left ?
According to Documentation/devicetree/bindings/net/can/microchip,mcp251x.txt, the driver requires it :
* Microchip MCP251X stand-alone CAN controller device tree bindings
Required properties:
- compatible: Should be one of the following:
- "microchip,mcp2510" for MCP2510.
- "microchip,mcp2515" for MCP2515.
- reg: SPI chip select.
- clocks: The clock feeding the CAN controller.
- interrupt-parent: The parent interrupt controller.
- interrupts: Should contain IRQ line for the CAN controller.
Optional properties:
- vdd-supply: Regulator that powers the CAN controller.
- xceiver-supply: Regulator that powers the CAN transceiver.
Example:
can0: can@1 {
compatible = "microchip,mcp2515";
reg = <1>;
clocks = <&clk24m>;
interrupt-parent = <&gpio4>;
interrupts = <13 0x2>;
vdd-supply = <®5v0>;
xceiver-supply = <®5v0>;
};
EDIT : @zador.blood.stained bet me, time to do copy/paste last to long ... ;-)
-
46 minutes ago, Pop Andrei Lucian said:
Under official website: http://linux-sunxi.org/images/4/4b/Allwinner_H3_Datasheet_V1.2.pdf
At page 68 it is stated that GPIOs PC3 and PC4 are "Default pulled up" (at reset time).
Ok ! I see, it is not the OPiLite schematic, but the SoC H3 Datasheet.
Looking atthis page 68, you can see that all GPIOs are at "Z" Reset State (during Reset been asserted), this means high-impedance like I mentioned.
Also, further on page 74, even those 4 GPIOs with PullUps (which probably mean internal pullups on the pins itself, I didn't verify with a scope), have their "Default IO State" all to "DIS", means "disabled", and they stay like that until been initialized.
That is why you still seeing them with value of zero...
If your wish is to have a LED reflecting the fact that the chip is been resetted but no single byte read from SDCard, your only solution is to connect that LED to reset, but that doesn't mean much since a reboot won't make that LED turned on.
EDIT : BTW, the reason those 4 pins have internal pullups is now clear, it is because there function2 is to attached a NAND, NAND_CE1/NAND_CE0/NAND_RB1/NAND_RB0, and having those floating to unknown state would means that NAND could be corrupted, so that is why they added those special pullups directly on the pin to prevent that. This means also the "Z" on page 68 for those pins is biased.
EDIT2 : I've verified with my scope, and PullUps are effectively permanently there, while other GPIOs needs to be configured to get them.
-
Although I've never tried it myself, for U-Boot, there is the CONFIG_SILENT_CONSOLE compile config.
-
Leave the PA13 as SPI_CS, and choose any other free GPIO for the IRQ, could be the original PA7.
-
PA13 : single pin cannot be IRQ and SPI_CS at the same time ...
How to replace OrangePi PC Plus firmware
in Allwinner sunxi
Posted
After having booted Armbian from SD, you can use nand_sata_install.sh to copy the Armbian over the current Android image present in the eMMC.
Then, shutdown, remove the SD, and re-power the board, it will boot Armbian from eMMC.