sunxi-tools icon indicating copy to clipboard operation
sunxi-tools copied to clipboard

A collection of command line tools for ARM devices with Allwinner SoCs.

Results 41 sunxi-tools issues
Sort by recently updated
recently updated
newest added

Hi, I'm able to compile and run sunxi-fel on 32bit windows including commit #5541673db88f7a0182738e514665eb908738387a After that, with the fit image support merge i cant compile anymore. Compiler has issues with...

Is there a way to write SP-NOR packed image with sunxi-fel or other source available tool? We tried to build it for ARM armv7l (A20) armbian and when try to...

``` 07:42 < qdk0901> sunxi-fel can speed up simply by just re-enumerate as high speed usb device 07:44 < qdk0901> sunxi-fel writel 0x01c19040 0x29860 07:46 < qdk0901> writel((readl(MUSB_POWER) & ~MUSB_DEVCTL_SESSION)...

The device i have isn't using the fex format. (i think) (somehow) I keep getting this error for some reason and I am wondering why. I really need this to...

When trying to boot from FEL mode on a perfectly working setup (cable and board) from a Raspberry PI 3B+ board, timeout happen: ``` pi@raspberrypi:~/sunxi-tools-1 $ ./sunxi-fel ver AWUSBFEX soc=00001667(A33)...

[https://github.com/xboot/xfel](https://github.com/xboot/xfel) The supported chip lists. ``` extern struct chip_t a10; extern struct chip_t a13_a10s_r8; extern struct chip_t a20; extern struct chip_t a23; extern struct chip_t a31; extern struct chip_t a33_r16;...

I'm trying to recover an A33 tablet (Logicom M BOT TAB 100) that's stuck with a broken recovery. It boots into TWRP which can't do anything (no touch screen or...

Hello, I'm trying to boot new custom board with A64 via USB-OTG with this script (sunxi-fel v1.4.2-110-g7a6a222 compiled from source). New board uses LPDDR3, the previous board uses normal DDR3,...

I've been poking at the X96 with the H313 processor, but when looking at the soc_id it seems to be identical to the H616: 0x1823. I'm not sure what to...

See Thore-Krug/Flash-CHIP#21 for more details, at the end of the thread they confirm `1.4.1` fixes the issue.