• Content Count

  • Joined

  • Last visited

About Evgeny

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Evgeny

    FEL eMMC

    Hi people, I need your help, I have been struggling to make this method work (https://github.com/zador-blood-stained/fel-mass-storage or https://github.com/ThomasKaiser/sunxi-armbian-flasher-osx) on the A20 processor for several days, but nothing works, I use Einstein-A20 (https://mega.nz/#F!ZtwxCCJC!AIYHcTqz-ucjuzKnE9qD7A?5xZ3iT4J) and enter the FEL mode using the special button UBOOT_SELECT. I made my own support for this board for uboot (_defconfig, .dts) and compiled u-boot-sunxi-with-spl.bin (Scroll down). script.bin took from cubietruck. That is, I use the h3 folder, only: zImage, uInitrd, boot.scr Сonnect the board in FEL mode to a virtual machine on VMvare Worstation 12.5.9. Ubuntu Bionic (armbian build system). j @ ubuntu: ~ / fel-mass-storage $ sudo ./start.sh [sudo] password for j: Connect device in FEL mode and press <Enter> 100% [=============================================== =] 4575 kB, 545.8 kB / s 100% [=============================================== =] 47 kB, 478.2 kB / s 100% [=============================================== =] 2230 kB, 548.6 kB / s 100% [=============================================== =] 0 kB, 15.3 kB / s U-boot log: After that, in Windows 10, a device appears with an error in getting the descriptor (USB\VID_0000&PID_0002\5&330350CB&0&5). I have already reread all the topics on the forum related to uploading an image to eMMC, but as a rule, they are addressed to the H3 board. The goal I’m following is to download a previously compiled armbian image to eMMc. With the preliminary partitioning of the file system using LUKS. Perhaps there are some other ways to work with eMMC (without preloading and subsequent transfer from sd card)? Please check files on my Git: https://github.com/evgenyhawk/einstein-a20
  2. Thanks for your reply! It was very useful for me and I will definitely apply it in the future.
  3. Friends, tell me is it possible to get the SID on the device itself? With the article, read: http://linux-sunxi.org/SID_Register_Guide In my sun50i-h5.dtsi: soc { sid: eeprom @ 1c14000 { compatible = "allwinner, sun50i-h5-sid"; reg = <0x1c14000 0x400>; } } #: sunxi-fel sid > ERROR: Allwinner USB FEL device not found! As I understand it, this utility retrieves from a remote device connected in FEL mode. But is it possible to somehow get the SID directly on the summit device?
  4. Thank you. Yes, overheating and error messages eliminated. Not tested on H3 (sunxi), since this fix covers mainly A64, H5, H6 (sunxi64). "Hot finger" test was performed on sun50i-h5-orangepi-zero-plus.
  5. https://github.com/armbian/build/pull/1176 Glad to help people who have encountered this problem. P.S. For the tip, thanks to Andre Przywara.
  6. As I understand it, this is my case - https://github.com/crust-firmware/crust/tree/master Did I try to figure it out myself, maybe I used this repository? P.S. Thanks for the tip.
  7. Hello Community, Now I encountered the following problem when testing my "orange pi zero plus": I tested the processor load (stress-ng) at a working frequency of 624mhz for 25 minutes. Settings: mainline sunxi64-next (4.14.y) "ERROR: PSCI system shutdown: still alive ..." The development scenario is predictable, but an error at the end prevents the device from rebooting. How to fix it? Update.1: Or should a reboot not occur, but only a shutdown? Update.2: Still, the device did not turn off and did not restart (just hung), since the processor temperature is still high and the Ethernet LED flashes.
  8. But how did you determine that the problem in loading wireless drivers? (for own development)
  9. Thank you for a hint about a spoiler (corrected) HEX-error migrated from the mainline 4.14.y
  10. Orange Pi Zero Plus (H5) http://ix.io/1ujE I can not understand what kind of error or what is it connected with? (present since version 4.14.y) [ 6.888226] 29 [ 6.888237] 81 [ 6.888239] 03 [ 6.888241] CC [ 6.888243] 00 [ 6.888245] 00 [ 6.888247] 50 [ 6.888249] 00 [ 6.888251] 00 [ 6.888253] 00 [ 6.888255] 04 [ 6.888257] CC [ 6.888259] 0A [ 6.888262] 0C [ 6.888264] 00 [ 6.888266] 00 [ 6.888268] FF and other errors: platform regulatory.0 (error) - appeared in the dev branch, there is none in the mainline branch CPU temp, without heatsink:
  11. Hello community! I use in my project "Orange Pi Zero Plus (Alwinner H5 - 512mb)". When using the image downloaded from the official site (https://www.armbian.com/orange-pi-zero-plus/ - Armbian Stretch mainline kernel 4.14.y), I get a set of errors when I boot and when I use the working OS, which I'm straining. The same mistakes I get if I build the kernel and the OS myself through "build" (linux-sunxi64-next). My equipment: Memory: SanDisk Ultra microSDHC Class 10 UHS-I 48MB/s 16GB Power supply: Raspberry Pi 3b+ Power Adapter (STONTRONICS) - 5.1V @ 2.5A Boot: full log - https://pastebin.com/M9g6ipUp Loading Environment from EXT4 ... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0: 1 ** Failed (-5) dmesg: full log - https://pastebin.com/GyeUTQem [0.668711] sun4i-usb-phy 1c19400.phy: Could not request ID GPIO [0.670578] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver [0.674095] sun50i-h5-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver [0.680561] NOHZ: local_softirq_pending 80 [0.703353] cacheinfo: Unable to detect cache hierarchy for CPU 0 [0.776991] core: _opp_supported_by_regulators: OPP minuV: 1120000 maxuV: 1300000, not supported by regulator [0.776999] cpu cpu0: _opp_add: OPP not supported by regulators (912000000) [0.777077] core: _opp_supported_by_regulators: OPP minuV: 1160000 maxuV: 1300000, not supported by regulator [0.777084] cpu cpu0: _opp_add: OPP not supported by regulators (960000000) [0.777134] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator [0.777140] cpu cpu0: _opp_add: OPP not supported by regulators (1008000000) [0.777218] core: _opp_supported_by_regulators: OPP minuV: 1240000 maxuV: 1300000, not supported by regulator [0.777224] cpu cpu0: _opp_add: OPP not supported by regulators (1056000000) [0.777274] core: _opp_supported_by_regulators: OPP minuV: 1260000 maxuV: 1300000, not supported by regulator [0.777280] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [0.777357] core: _opp_supported_by_regulators: OPP minuV: 1300000 maxuV: 1300000, not supported by regulator [0.777363] cpu cpu0: _opp_add: OPP is not supported by regulators (1152000000) [0.777627] thermal thermal_zone0: binding zone cpu-thermal with cdev thermal-cpufreq-0 failed: -22 [0.862337] mmc0: host does not support reading read-only switch, assuming write-enable [0.862561] NOHZ: local_softirq_pending 80 [1.265962] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found using dummy regulator [11.340617] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit = 600, errors = remount-ro [11.473725] 29 [11.473733] 81 [11.473738] 03 [11.473740] CC [11.473742] 00 [11.473745] 00 [11.473747] 50 [11.473749] 00 [11.473752] 00 [11.473754] 00 [11.473756] 04 [11.473758] CC [11.473760] 0A [11.473762] 0C [11.473765] 00 [11.473769] 00 [11.473770] FF [11.473772] FF [11.473775] FF ... [11.474899] FF [11.474901] FF [11.474904] FF [11.564425] g_serial gadget: Gadget Serial v2.4 It is difficult for me to estimate how much these errors are critical for stable use of the OS, since I am not an expert in this field. Ready for tight interaction to eliminate these problems, if they are. Thank you for your attention and your answers - any information on this issue will be useful.