Jump to content

CryBaby

Members
  • Posts

    110
  • Joined

  • Last visited

Posts posted by CryBaby

  1. Yes, assuming /boot is a separate partition. I do this with my Raspberry Pis as I have very unreliable power. I also set them to check filesystems on boot by adding fsck.mode=force to the kernel command line. On OSMC that is in /boot/cmdline.txt, on armbian it might be in /boot/uBoot.env, on a grub machine in /etc/default/grub (then run update-grub).

  2. #!/bin/bash
    
    TOP=/home/share/video/music
    
    if [ -n "$1" ];
    then
        TOP=$1
    fi
    
    OLDIFS=$IFS
    IFS=$'\n'
    
    find $TOP -name "*.[maowf][povgklm][gvim]" -print | shuf -n 100 > randomplaylist
    mpv -fs -vf=pp=de --playlist=randomplaylist
    rm randomplaylist
    
    IFS=$OLDIFS

    This will play 100 randomly selected files from /home/share/video/music and subdirectories or whatever directory you pass on the command line.

  3. Take the SD card out and put it into another machine. Copy the whole card as an image. To restore you just copy it back. On Linux I would use dd for this:

    sudo dd if=/dev/mmcblk0 of=backup.img bs=1M status=progress

    making sure you have the right dev. It should not be mounted while you do this.

    On Windows... Balena Etcher?

  4. If you are using WPA then you probably don't have RADIUS as that is for central auth in enterprise environments, usually they use PEAP.

    That doesn't necessarily rule out OpenSSL as the culprit though.

    I get the same error as you at work but have no problem at home where my router runs OpenWRT.

    Perhaps there is a menu option in your router for firmware updates.

     

    You could try the workaround suggested in the link I posted:

    > > adding this to /usr/lib/ssl/openssl.cnf fixes the issue.
    > >
    > > [system_default_sect]
    > > Options = UnsafeLegacyRenegotiation

    It may not be quite that simple, it didn't work for me.

     

    Alternatively, you could get hold of another router (gl-inet.com) that you can connect to and hook it up to your main router with a cable from WAN to LAN ports.

  5. I have tried the clearing of eMMC option. Unsurprisingly it cleared the eMMC and I can no longer boot to Station OS. I can still boot to Balbes' UPDATE_UBOOT image from SD card.

     

    The other option is 'Delete bootloader'. I have not tried this but I think it must clear the SPI. You would definitely want a working uboot in eMMC before doing that. The question I have is if you do that and have an empty SPI will the bootrom go to the eMMC or will it hang?

     

    Firefly have RK356x_NorFlash2eMMCLoader_20211209.img which suggests you need something in SPI (aka NorFlash) to redirect to the eMMCThis page goes into it. I don't have Windows, no longer have Station OS (so no ADB) and have so far failed to enter MaskROM mode so I'm a bit stuck.

  6. root@station-p2:~# sudo /vendor/p2-station-update-uboot 
    16384+0 records in
    16384+0 records out
    8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.378473 s, 22.2 MB/s
    8192+0 records in
    8192+0 records out
    4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.159035 s, 26.4 MB/s

     

    I have had this P2 for a year and have updated to the latest Station OS, and enabled/disabled the OS Bootloader several times.

     

    I have of course studied that thread. I was hoping your fix was in the latest Station OS update but I guess not.

     

    It is not clear to me how to erase the SPI as you suggest. There are some advanced options that might do it in the OS Bootloader. I worry that I may end up unable to boot anything.

  7. I vaguely remember having trouble with this myself. The 2mm pins were a problem too so I switched to a different board.

     

    Are you absolutely sure you have shorted the right two pins?

     

    One of those $10 USB logic analysers from eBay can be handy to see if the TX is actually TXing. They work with Pulseview from Sigrok.

  8. 2 hours ago, Dominik said:

    Can I plug the sd card into my PC and edit the files there?

    This will be the easiest approach, provided you have linux on your PC. If you don't then you could make another working sd card, boot your SBC with that and plug in the broken one using an adapter. Then you mount the broken card and undo whatever you did to break it.

     

    None of this is specific to a particular board.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines