Jump to content


  • Posts

  • Joined

  • Last visited

  1. Hi all, I have an application running on an orange pi pc plus 2 over the emmc 8gb memory. Everything is in there (os, db sw) and what it does is acquiring data from some sensors and then pushing it over mqtt to a server. Now, due to frequent internet connection issues, the board is able to store up to ~ 1 month of data in a local db but this means quite a lot of writes per seconds (plus all the logs). I would like to have an idea of how much the emmc can keep up with this rates and thus I am trying to understand how to calculate the life span in years (hopefully nothing less). Can anyone help me on how to do that? I am using right now iostat to get an estimate of the kB_wrtn/s and I get something around 50. Any help would be really appreciated. p.s.: obviously I am trying to explore solutions, like ramdisk, wear leveling and simply storing stuff if the connection is actually out, but I would like anyway to get a feeling of the life span of the memory.
  2. Just adding some more info for this issue that is haunting me. After seeing that "rmmod" doesn't provide me any help so far, I tried to directly bind and unbind bus drivers (both usb hub and ftdio) without any success. The only thing worth mentioning is that I got this error with one of the hub: [221495.711378] hub 8-0:1.0: USB hub found [221495.711399] hub 8-0:1.0: config failed, can't read hub descriptor (err -22)
  3. Hi all, I am using an Orange Pi PC PLUS2 with everything in the emmc for controlling another device through a serial connection (rs485) with a serial converter using FTDI chips. I am using docker containers to embed my application and easily deploy/share it. using uname -a gives me: Linux host-test 4.14.15-sunxi #28 SMP Mon Jan 29 07:24:48 CET 2018 armv7l GNU/Linux The problem is that randomly I get the following error: [135431.500807] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [137213.011801] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [138650.664850] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [140559.020691] ohci-platform 1c1b400.usb: frame counter not updating; disabled [140559.020972] ohci-platform 1c1b400.usb: HC died; cleaning up [140559.025797] usb 6-1: USB disconnect, device number 2 [140560.099001] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [140560.099018] ftdi_sio ttyUSB0: urb failed to clear flow control [140560.099652] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [140560.099738] ftdi_sio 6-1:1.0: device disconnected After that I can't use the serial converter anymore. It does not appear on ttyUSB0 and I don't manage to make it work again. I tried to rmmod both "ftdi_sio" and "usbserial" and modprobe them again, but nothing changes. The only way to fix it is to reboot the system. I am experimenting a lot with modules like pylibftdi, vpc drivers vs d2xx ones, etc...without results. I am really struggling a lot with this and I can't find any real or clear help online. Unfortunately this is a big issue since it makes my SW unusable and I can't really deliver it like this. It is worth noting that I never saw this issue without using docker. My questions are: - Does anyone have any clue how to solve this or can provide any help (it is really a big issue for me)? - At least, does anyone have any idea how to restore the serial line without rebooting? Thanks a lot in advance.
  4. Thanks for the quick replies! Irreversible HW modifications are not a big issue in my case...I just need to understand what we are talking about and how to disable SD booting. Could you expand a bit on this? How would it work and what should I do? Yeah, I know that unsoldering is not a huge move, but it is somehow more bothering and problematic to standard users compared to SW measures. I am really trying to add as many layer of "boring protections" as possible...any idea is very welcome! Thanks for the boot info, it helps understanding the sequence.
  5. Hi all, I recently purchased an orange pi after developing on the raspberry pi (just for convenience). I got it mainly because the integrated memory could be a real asset both because SD are faulty when making lots of memory accesses and emmc can provide a nice layer of code protection when giving the board to somebody else. I set-up everything without issue and I used the nand-sata-install to move everything to emmc...it worked like a charm. I then placed all my proprietary code on emmc and executed without issues. Problem is, I can obviously still insert an SD card and then mount the emmc and access my code since the SD is booted before the emmc. 1. Is it possible to change this boot order or to just completely disable SD boot and thus deliver an emmc only device to a client? 2. How does the boot for H3 works? I read about u-boot and similar but it is not very clear to me what is the boot sequence and where it starts from. 3. As an alternative, should I just unsolder the SD tray or is there any other HW mod I could do to block sd cards? I considered (and I will probably use it for some other layers of protection) using some encryption, but in general that uses lots of resources. Any help would be really appreciated, thanks in advance.
  • Create New...