All Activity

This stream auto-updates     

  1. Today
  2. While doing the kill, did you got the "got SIGTERM" ? If yes, you should add "gpio.output(REL, 0)" just after the print and before the "sys.exit(0)" ...
  3. I tried to add at the end of the script, these 4 lines : def signal_term_handler(signal, frame): print 'got SIGTERM' sys.exit(0) signal.signal(signal.SIGTERM, signal_term_handler) but the relays maintain the status, even after the kill command.
  4. @Igor Thanks! That seems to work fine. I only ran it for about 30 minutes though. root@espressobin:~# uname -a Linux espressobin 5.1.0-g72cf0b074 #1 SMP PREEMPT Sun May 19 18:21:04 CEST 2019 aarch64 GNU/Linux root@espressobin:~# 7za b 7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,2 CPUs LE) LE CPU Freq: 439 450 368 589 591 505 585 487 RAM size: 984 MB, # CPU hardware threads: 2 RAM usage: 441 MB, # Benchmark threads: 2 Compressing | Decompressing Dict Speed Usage R/U Rating | Speed Usage R/U Rating KiB/s % MIPS MIPS | KiB/s % MIPS MIPS 22: 438 122 349 427 | 13482 198 581 1151 23: 524 146 365 534 | 13276 198 580 1149 24: 520 147 381 560 | 12839 195 577 1127 25: 517 147 402 591 | 12862 198 580 1145 ---------------------------------- | ------------------------------ Avr: 141 374 528 | 197 580 1143 Tot: 169 477 835 I'm confused. I do not understand what this has to do with the U-Boot bootloader? 1000_800 worked fine with 4.4.8-armada-17.02-espressobin kernel. My board came with "U-Boot 2017.03-armada-17.10.2-g14aeedc" preinstalled, which on boot reported: CPU @ 1000 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 800 [MHz] Which is why I choose to flash "flash-image-ddr4-1g-1cs-1000_800.bin". Espressobin v7 should run at 1.2 GHz, so I just tried flashing "flash-image-ddr4-1g-1cs-1200_750.bin", but now my board does not boot: Marvell>> bubt flash-image-ddr4-1g-1cs-1200_750.bin spi usb Burning U-BOOT image "flash-image-ddr4-1g-1cs-1200_750.bin" from "usb" to "spi" USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found Image checksum...OK! SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB Erasing 917504 bytes (14 blocks) at offset 0 ...Done! Writing 889028 bytes from 0x8000000 to offset 0 ...Done! Marvell>> Marvell>> Marvell>> reset resetting ... TIM-1.0 WTMI-devel-18.12.0-a0a1cb8 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 0.898V It never gets any further than "SVC REV: 5, CPU VDD voltage: 0.898V" - any ideas?
  5. Starting from SDCard, but check my EDIT2 above : I've found why, it was still taking boot.ini from eMMC, although booting SDCard ... Unfortunately, my SPINOR seems to be stuffed with a U-Boot that doesn´t have keyboard check, I've tried <space>, <return> and <ctrl-c>, none of them worked. So, I went back pluging the eMMC, and try it there, but here is the execution : odroidn2#usb start (Re)start USB... USB0: USB3.0 XHCI init start Register 3000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found odroidn2#fatload usb 0 3000000 n2_autoscript reading n2_autoscript 1107 bytes read in 22 ms (48.8 KiB/s) odroidn2#autoscr 3000000 ## Executing script at 03000000 Start add multiboot Saving Environment to MMC... Writing to MMC(0)... done Stop add multiboot bl31 reboot reason: 0x108 bl31 reboot reason: 0x108 system cmd 0. bl30 get wakeup sources! process command 00000006 bl30 enter suspend! Little core clk suspend rate 1200000000 Big core clk suspend rate 1200000000 store restore gp0 pll suspend_counter: 1 Enter ddr suspend ddr suspend time: 17us alarm=0S process command 00000001 cec ver:2018/04/19 CEC cfg:0x0000 WAKEUP GPIO cfg:0x00000000 use vddee new table! WAKEUP GPIO FAIL - invalid key After that, I've rebooted, it seems to start booting from USB, but stuck without reaching login prompt again ... I've added "loglevel=7" in boot.ini, and also in boot.cmd I've created to redo boot.scr using mkimage. But no success : booting from USB stall before login prompt without clue ... EDIT: It has finally booted, but without verbosity, and this time, it was present in /proc/cmdline.
  6. no way, today i cannot even connect via ssh (timeout)
  7. I’m using the Pine64 2GB Kickstarter’s board with the official LCD, running Armbian 5.25 Pine64 Debian (Jessie) image. Everything works fine, display in terminal only and touch screen with the desktop. Now I would like to upgrade to the latest stable Armbian version (which on download page is 5.38). However now I can’t enable the LCD, although the download page says: It was a couple years back, I don’t remember exactly, but seems that was the same way I’ve used to enable the screen in old 5.25 Armbian. I’m no Linux kernel developer, but searching through the forum on the topic I found several mentions of “kernel recompile” - is there no other ways to enable the LCD in 5.38? Or I better stay with the old 5.25 Armbian? Just to clarify and rule out any hardware issues: I still have the uSD card with 5.25, swapping it back and everything shows up on the LCD. But booting the card with 5.38 and the LCD is blank, although everything works fine over ssh as well as on HDMI screen, if I connect it... Any help is very much appreciated. Thank you all very much in advance! Mac Ha
  8. Ok, the old one has been delete, everything works fine: root@nanopineo:/# cd boot root@nanopineo:/boot# ls armbianEnv.txt dtb-4.19.38-sunxi armbianEnv.txte initrd.img-4.19.38-sunxi armbian_first_run.txt.template overlay-user bin script.bin bin.old boot.bmp boot.cmd uInitrd boot-desktop.png uInitrd-4.19.38-sunxi boot.scr vmlinuz-3.4.113-sun8i config-3.4.113-sun8i vmlinuz-4.19.38-sunxi config-4.19.38-sunxi zImage dtb root@nanopineo:/boot# apt-get remove linux-image-3.4.113-sun8i Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'linux-image-sun8i' instead of 'linux-image-3.4.113-sun8i' 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. root@nanopineo:/boot# apt-get remove linux-image-sun8i Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-sun8i 0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded. After this operation, 48.6 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 66591 files and directories currently installed.) Removing linux-image-sun8i (5.85) ... update-initramfs: Deleting /boot/initrd.img-3.4.113-sun8i root@nanopineo:/boot# I noticed that the idle temperature has increased from around 39°C to 47°C from the old kernel/version to the new one. Could the heartbeat feature (blue led flashing) be causing that (this wasn't present in the last version)?
  9. Thanks @guidol, i solved this issue. Apparently for some unknown reason the sdcard bood image was corrupted. I reflashed it with the latest armbian and the boot log now is as expected. Cheers
  10. Is it when starting from SD card or when recording to eMMC ? I downloaded the scripts to activate the system startup from USB. The order of use (so far it is checked only with kernel 5). 1. Burn image to USB. 2. Download the files and add to the image. 3. Switch to start u-boot with SPI. 4. In the UART console, stop startup. (CTRL+C) 5. Execute the command. usb start fatload usb 0 3000000 n2_autoscript autoscr 3000000 At the end of the script, the system should shut down. Include, if correct, should begin loading and operation of the system with the USB.
  11. No, I didn't try to change anything yet ... Here is the ENV : The strange thing is that, althouth "loglevel=7" been added to /boot/boot.ini, here is the early boot output saying : [ 0.000000] Kernel command line: root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes net.ifnames=0 EDIT: Another weird thing : I've decided to use the workaround by adding chosen/bootargs node to the DT, as we are doing on other boards, recompile the DTB, and reboot ... Strangely, the "loglevel" is been discarded there too, and doing "cat /proc/device-tree/chosen/bootargs" revealed that it is discarded there too : cat /proc/device-tree/chosen/bootargs root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes net.ifnames=0 EDIT2: Ok ! I found my stupid error : I was leaving the eMMC plugged, and although booting from SDCard, U-Boot was taking the boot.ini as well as DTB from eMMC, which they were still at original states !
  12. I will check later on. Now busy with life. I added support for booting without having FAT partition so this is not the case. Legacy kernel boots fine.
  13. Show "printenv". Have you changed anything in ENV ? What's in the launch logs ? Perhaps not all items are correctly added (changed). I use necessarily two partitions for external media. This ensures that users can easily change the settings on any PC (including Windows), when using one ext4 - there will be problems with changing the settings (edit boot.ini, etc.)
  14. Although I didn't try it out, you will need some signal handler where you can turn off GPIO before "kill" been completed. Here is some example :
  15. Igor

    RK3399 Orange Pi

    He probably meant why this (mSATA) drive is not working on mPCI ... while the connector is compatible.
  16. Mainline also didn't work for me, but I only gave it one try. Ran out of time ...
  17. ok I corrected and added the lines to make the script a daemon, I noticed however that if I kill the script (kill 1234) or if I block the OPI0 the relays card remains in the last state in which it is, how could you do to reset it to off?
  18. Here it is : ODROIDN2-UBOOT-CONFIG setenv dtb_name "/dtb/meson-g12b-odroid-n2.dtb" setenv bootargs "root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 loglevel=7 no_console_suspend consoleblank=0 fsck.fix=yes net.ifnames=0" # Set load addresses setenv dtb_loadaddr "0x1000000" setenv k_addr "0x1100000" setenv loadaddr "0x1B00000" setenv initrd_loadaddr "0x3700000" # Load kernel, dtb fatload mmc ${devno}:1 ${k_addr} zImage fatload mmc ${devno}:1 ${initrd_loadaddr} uInitrd fatload mmc ${devno}:1 ${dtb_loadaddr} ${dtb_name} fdt addr ${dtb_loadaddr} # boot booti ${k_addr} ${initrd_loadaddr} ${dtb_loadaddr} and here is what /proc/cmdline is showing me : root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes net.ifnames=0 Maybe I should stop U-Boot and try "printenv" ? Maybe it is because it was previously saved and the modified /boot/boot.ini is ignored ?
  19. Checked at myself "loglevel=7" , the option works on both kernels. The image with the 5.1 kernel is written to a slow SD card, when set the level 7 , waited more than 20 minutes to start the system, but did not wait for the prompt to enter the login. In mode 5, "cat /proc/cmdline" shows the correct value in the arguments specified by "loglevel=5". You in what place to register this option ? Show the contents of "boot.ini"
  20. Anyone has tried kernel 5.2rc1? I think Cedrus driver support should be available by now. Even in 5.1.y kernel the VPU part was working, as sunxi said. Anyway, Has anybody tried desktop build? If I want to, is there a repository or something else I can download the image from instead of building it myself?
  21. This sleep(1) isn't indented properly, so not part of the while loop ...
  22. Of course, it will be appreciated ! This you figured out about the "loglevel" ?
  23. This cable is really for SATA, not MSATA, they don't even have the same size ...
  24. This is not the way Armbian implemented overlays. They are activated using parameters in /boot/armbianEnv.txt Take a look at But beware that current overlays for Rockchip are not as complete as for AllWinner SoC...
  25. Okay Martin I solved was just a tabulation problem as I could tell from your example. Now the rudimentary thermostat works, I would like to make sure that it remains in operation as a daemon, insert different temperatures at different times of the day, and finally make a decent GUI. But the road is uphill....
  26. That is what I said earlier, indentation is critical ... Did you take back my version ? It doesn't seems to, because the "if" in my version is located at line 29 ...
  1. Load more activity