Announcement

Collapse
No announcement yet.

Allwinner V316

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Click image for larger version

Name:	images (1).jpeg
Views:	308
Size:	27.1 KB
ID:	15296

    Comment


    • petesimon
      petesimon commented
      Editing a comment
      nutty guy! oh wait. i do the same your FB group. haha

  • #17
    petesimon In the post (№6) backup is not firmware. On the box or in the user manual there is an http link to the brand or support

    Comment


  • #18

    Was grepping through the binary sdvcam when I noticed the 123456/admin strings, could that be some default username/password?
    Code:
    TutkLoginThread
    
    123456
    
    admin
    
    /home/dv002/workspace/v316/eyesee/IPCLinuxPlatform/custom_aw/apps/ts_sdv_x16_lcd320x240_imx386_xr819_ft6x/source/bll_presenter/remote/tutk/wrapper/av_server.cpp
    
    LoginThread exit!
    
    I can be connected via Internet
    
    I am be banned by IOTC Server because UID multi-login
    Also interesting to see the full path of their dev environment. They seem to base their project name on the hardware BOM of the camera (sensor/lcd size/power supply/etc.).

    UPDATE: I managed to trigger some kind of update mode when I renamed the full_img.fex to full_img.img. It failed the update though, need to find out what format it expects. It seems to invoke the /etc/chroot_ota.sh script which then runs the /usr/bin/ota_update binary. After the failed update attempt it does a factory reset.
    Last edited by vzzbx; 08-23-2019, 10:10 PM.

    Comment


    • petesimon
      petesimon commented
      Editing a comment
      neat findings. what if you make a big Phoenixsuit IMG file by using the 'makeimg' tool? and put the IMG file on your SD card? or shove the IMG file down the camera's throat through PhoenixSuit / PhoenixUSBPro ?

      https://www.dropbox.com/s/tothsp7rgv...prawn.zip?dl=0
      read the 'howto.txt' file inside makeimg zip
      Last edited by petesimon; 08-26-2019, 04:45 AM.

    • petesimon
      petesimon commented
      Editing a comment
      for the bold, brave and daring. here is a Phoenixsuit IMG style file 27552768 bytes in size. I don't yet have any v316 camera. So I wonder what would happen.... https://www.dropbox.com/s/1qr8rftf6z...x-IMG.rar?dl=0

      what do you think?
      Last edited by petesimon; 08-29-2019, 01:44 PM.

    • vzzbx
      vzzbx commented
      Editing a comment
      @petesimon: well, that did not work. It did recognize it as a proper image and started to flash, at around 11% it suddenly decided that flashing was done 100% and asked to reboot. Now it is bricked. I need to reattach the UART to see how far U-boot comes, if it reaches U-boot at all...

      For now, don't flash it.

    • vzzbx
      vzzbx commented
      Editing a comment
      Console output:


      [174]HELLO! BOOT0 is starting!
      [177]boot0 commit : 216fe8da00b2558a7d836be05109904b37ddcefd

      MESSAGE: [0x0] TEE-CORE: arisc commit: 76186687bf7ac0730aa4127a5f3a25670a699c34
      DRAM:
      sunxi spinor is initing...OK

      sunxi#

    • petesimon
      petesimon commented
      Editing a comment
      oh shit. I didn't recommend this to be done. But hey, I guess it's like Star Trek, "to boldly go where no one has gone before".

      Your BOOT0 sunxi# prompt reminds me of recovering my bricked old Linksys router through the USB-UART CP2102 (or similar?) adapter. I loaded a too fat bloated firmware, whopping 16 MB, but the router could take only 8 MB max.

    • vzzbx
      vzzbx commented
      Editing a comment
      No worries, was in for an experiment :-P

      It seems the chip can be put into a recovery mode (FEL). Need to read about that how that is going to work.

      Funny thing: when it was dead I started to play with pushing buttons while powering the device on. The up button seems to trigger different behaviour as in the blue LED won't turn on and only the HELLO! BOOT0! message would appear. I need to look into that, maybe some recovery mode....

      Also pressing the 2 button on the keyboard while connected to the console seems to trigger different boot behaviour...

      I hope the IMG_FULL.fex I pulled off the device is complete enough though to restore a working system.

    • petesimon
      petesimon commented
      Editing a comment
      vzzbx
      It seems the chip can be put into a recovery mode (FEL). Need to read about that how that is going to work.
      1. remove battery, remove sd card
      2. press and hold UP button
      3. connect USB cable to camera and to computer, still holding UP button
      4. press and release the power/mode button 3 times
      - or use another method as written in this page - https://linux-sunxi.org/FEL
      USB device ID 1f3a:efe8 will show up - https://usb-ids.gowdy.us/read/UD/1f3a/efe8

      the 'sunxi-tools' namely the 'sunxi-fel' command might help you.
      https://linux-sunxi.org/Sunxi-tools
      https://github.com/linux-sunxi/sunxi-tools
      https://linux-sunxi.org/FEL
      https://linux-sunxi.org/FEL/USBBoot
      https://whycan.cn/t_1635.html
      https://whycan.cn/t_444.html
      files for windows - https://www.dropbox.com/s/ha650qb95t...win32.rar?dl=0
      package for linux - https://packages.ubuntu.com/search?keywords=sunxi-tools

      *some other FW tools for Linux(?) - https://github.com/Ithamar/awutils

      may need to install some magical USB software thingies in Windows for 'sunxi-fel' to work correctly. Not sure about Linux yet ...
      https://github.com/libusb/libusb/wik...usb_on_Windows
      https://zadig.akeo.ie/

      I'm reluctant to send any binary data over USB to the camera when it's in FEL (recovery) mode because I have only _one_ V316 camera and I would like for it to record video, hehe
      Last edited by petesimon; 10-08-2019, 07:34 AM.

    • vzzbx
      vzzbx commented
      Editing a comment
      @petesimon: thanks for the information, I have been reading up on the FEL mode, but a holiday came first so the project went on hold for a while :-).

      I am planning to give the FEL recovery mode a look in the coming weeks when I have some time. Would be nice to geet the thing working again. I use linux so no need to use Zadig.
      Ah, so you have one as well, does it use the same software version as mine?

  • #19
    vzzbx So the update (firmware) occurs through the application (App) on the phone. Password and login for wi-fi connection with the application (App).

    Comment


    • vzzbx
      vzzbx commented
      Editing a comment
      No, OTA means in this case it will read in a file from the flash card. It should not be called OTA in this case though.

  • #20
    https://www.banggood.com/4K-60fps-Wi...r_warehouse=CN

    link:: https://i.ibb.co/vzJC9px/1.jpg

    With this app usually downloaded firmware

    2/-
    http://www.hdking8.com/hdking-real-4...rizontalTab022

    link: https://i.ibb.co/kHtR9YR/2.jpg
    Last edited by Dav; 09-05-2019, 04:43 PM.

    Comment


    • #21
      apps
      xdv
      https://play.google.com/store/apps/d...idewin.x1.view

      DVKing ????

      https://play.google.com/store/apps/d...vking4k.xdvpro

      https://play.google.com/store/apps/d...ewin.king.view
      ---- > "DV KING is a streaming video surveillance software, iPhone through sport DV hotspot, connecting Zhuhai allwinner technology based on the movement of the main chip DV, real-time monitoring."
      Last edited by nutsey; 09-06-2019, 06:28 AM.

      Comment


    • #22
      Hi..a benchmarking tool that adds to CPU utilization on a real server in a negligible fashion might max out CPU ressources on a weak ARM SoC so the tool used for benchmarking might bastardize performance numbers itself. Also when acting single-threaded it might in reality test CPU and not network -- true for iperf in most operation modes.

      pcb assembly usa
      Last edited by DotTumin; 10-23-2019, 09:32 PM.

      Comment


      • petesimon
        petesimon commented
        Editing a comment
        hmm? are you talking about benchmarking the SoC (cpu) of these V316 cameras?

    • #23
      Yesterday I received this https://www.aliexpress.com/item/33021398874.html for about $47 USD in the post/mail. Sometimes the touch response is finicky or stop working, but otherwise the cam seems to work normally. I will post video samples later...

      Download the firmware backup here - https://my.pcloud.com/publink/show?c...lA7V4emuHlEC3X

      Here's a backup script for Linux that I used - https://www.dropbox.com/s/njttfc9c3j...press.zip?dl=0

      and here's another for Windows, with RAR compression - https://www.dropbox.com/s/1c9r63yxxy...-V316.zip?dl=0

      *Update - UNFEX, REFEX, FWINFO scripts to use in Windows for V316 firmware, is here - https://www.dropbox.com/s/12xljkf9pb..._V316.zip?dl=0

      Click image for larger version  Name:	VOQQBVGLp-wxSDC6LSYmKJ06CBI7eKBFzduTheWj2mfUJkpqYsiVTPH3JbcdxQHIJoZ4LpWkq8nl1aQm116K9QceyXPh1dFb6opMcsWb-UkgGFLoQFvzxcoAPT5YId8JwTWw-oICTJ6ZsgMr4gPOSLd4DqZY3PnrivDK-f2uLXpyFQuzicaPANRa_8xZGxx_1vOOv_S-hsL1G3wl6dOloTOxa6_riA1RM8Fu1ZPXTtjriZPtomd8xX0DRQ1y4K6 Views:	25 Size:	42.4 KB ID:	15543Click image for larger version  Name:	Oo-JA2SOqKeLatJVgSNVC6ZTDRp_I6kLWIHRCxqBNhFErKrlCN5LwuXzC_rHNQQYjBjMCWKSjGpFDW_2i8dXamtGYISBZVwDf5orZlNF_Uxd9sZ8AZlxVEAlEj9YD-PeQMN75ofVKiX3RHir_eqiF3SwKEoeSTxLWWwpxZM5EXntTqCSdyl8P-_kMzJKjPdDMaGBXTF827tIz0XfUPIAR0Dr5quQoRIFP0wURSKgTbc-0V6-6aSOfhGSF2R-ep1 Views:	18 Size:	45.2 KB ID:	15544Click image for larger version  Name:	XcOvwTAb3Ij4rMENEu4tjMeVdpb-3yPBNnu8TmTMaLWeM-k9FTyA0-3qslK2Fx_LggSpbh_m21Rst5RveNECo1K4Uwrin0zLqFcht_x50QV2wv38UOx7qYbhpQSL8Uuj2v1NZVec861Lm5DrsERhWOufgbZWkYhKIBDKrM_sWBmtSRyfj0Gjvyhh3IeOBipeqE_Iu4nrOZcfJuKnmBqX5Lykn0665jfWH3Q6kVf87M85YCl-bF8OrsFQcsp2FnC Views:	19 Size:	31.7 KB ID:	15545Click image for larger version  Name:	nLC48J3dpSeQlDUWqafhzQYFNINhKjTzYstdvYDbwI2arMQg45pUaYxoeboFO4Zk79fZdtatZOGQ8WnZeh_95zTD925obv1l33Zgz4iUp4nnZR8XUvUY7CM4ERVqVmM20yiW0ddkrImzV8zr0ZUy_6ULHqefK6YhVy3ZLL7_ddjKIdPfY2SZ1IEFXxsqoMEE5CVDuS_hFHW8Hi5lpE15k8tuOEqoBdWTFBmXxXxcY0yACVMgHi1id3vLiH5CDE3 Views:	18 Size:	39.7 KB ID:	15546

      Code:
      V316 FWINFO
      
      Built by:
      jingmanzhao
      
      Manufacturer:
      Sunchip
      
      LCD resolution:
      320 x 240
      
      LCD model:
      st7789v
      
      Product type:
      V316
      
      Software version:
      V3.0
      
      Build time:
      2019-03-27 16:51:51
      
      Updated time:
      20190219
      
      Sensor:
      Imx386
      
      Sensor modules (drivers):
      imx278_mipi , imx386 , imx317
      
      Wifi:
      xradio
      Last edited by petesimon; 10-01-2019, 10:26 AM.

      Comment


      • Dav
        Dav commented
        Editing a comment
        Hi petersimon! SD Card will come, I will lay out too. Nice camera. I bought the lens for 90 degree aliexpress.com/item/32866191547.html. Wanted this lens .aliexpress.com/item/32465183583.html But shipping to my country costs more than the cost of the camera.

      • petesimon
        petesimon commented
        Editing a comment

    • #24
      The image quality is actually satisfactory in 4k30, 2.7k30 and 1080p30. There is 60fps in 1080p and 720p, but no 60fps in 2.7k or 5k, and Allwinner makes odd looking 60fps footage -- it sometimes looks like "fast forward" 1.20x speed. The "low speed card, please replace" message can be ignored for most sd cards. A U3 or V30 speed sd card would be best. There is a "distortion correction" setting for 1080p30 and 1080p60 and it reduces the barrel curve effect. A "Quality" and "Sharpness" setting for video mode and photo mode can be set to low, medium and high. For general/everyday use, medium quality is good enough for all video and photo resolutions. Otherwise, set the quality to high to ensure the best possible image. As user vzzbx said, the exposure (EV) is to much at 0.0 setting, so in bright places, set the EV to down to -1.0.

      Filename scheme: MP4 are normal videos, SEC are 640x360 preview videos, THM are 640x360 thumbnails for each MP4 video, JPG are normal photos. There are no separate small thumbnails for JPG photos. Also, ANMRxxxx.mp4 are normal speed videos in which the xxxx are numbers, but ASMRxxxx.mp4 are slow motion videos. ALMRxxxx.mp4 are videos from Loop mode. Basically, just keep the MP4 and JPG files and don't use the other files. All video is MPEG4 AVC h264 but not HEVC h265.

      Unprocessed video samples - http://pc.cd/XJDctalK

      Unprocessed photo samples - https://extraimage.net/album/jZS

      *Update - more unprocessed video samples - https://my.pcloud.com/publink/show?c...S6KGDHdSXHnokV

      Youtube 4k 30fps clip. Uploaded as unprocessed mp4, at 50 Mb/s bit rate - https://youtu.be/NE64oAIEV2o

      Camera album - https://imgur.com/a/GZ7fqoI


      click the links above
      Last edited by petesimon; 10-01-2019, 10:11 AM.

      Comment


    • #25
      vzzbx
      I managed to trigger some kind of update mode when I renamed the full_img.fex to full_img.img. It failed the update though, need to find out what format it expects. It seems to invoke the /etc/chroot_ota.sh script which then runs the /usr/bin/ota_update binary. After the failed update attempt it does a factory reset.
      My FW doesn't have /etc/chroot_ota.sh or anything else like that in '/etc' directory. But /usr/bin/ota_update is there. So connected the cam to my Linux computer by USB cable and I ran adb shell ota_update and a lot of text spat out. The good part showed me what the firmware file name should be:
      Code:
      ota progress: 0.0%, total spend time: 0sec
      ota begin......
      firmware name /mnt/extsd/sun8iw12p1_linux_v5s_pro_lpddr3_uart0.img
      .
      Then, I disconnected USB, copied my 'full_img.fex' file to the sdcard as 'sun8iw12p1_linux_v5s_pro_lpddr3_uart0.img', powered OFF and then ON the camera and got the OTA upgrade screen. Nothing happened... and the cam was frozen -- no touch screen, no physical buttons worked either. I had to remove the battery and power OFF the camera completely. The process deleted the 'sun8iw12p1_linux_v5s_pro_lpddr3_uart0.img' file from the sd card.

      click this small photo
      Click image for larger versionName:	OpIHCRkNRqFcfVGxu4A3-XHd9jbl5z5ZZW6JGWr25HAuOurA7U9M3GKGoGxCtwqTzYaEx-cHLFfRohJkhebgNx1xlhbd93qPoL9fMNXY-YZjqnrtro1Fn691BARdsXi_U1sOAoCDXgFoT7kAnX4XQbV0WxZD-zizC7mYrYfu8uIpsIdCX6UUHpi_axmu0qyJrryjSyJ8jZ3TKVTp7-avMvP-_j2wIjvyLAT4J0xgeJOr1q5laMvV96yi4ULrpAzViews:	0Size:	26.8 KBID:	15597

      Another go ... removed sd card, powered OFF the camera, power ON the camera without a sd card, and after boot Iinserted the sd card. Connected the cam to my Linux computer by USB cable and ran adb push full_img.fex /mnt/extsd/sun8iw12p1_linux_v5s_pro_lpddr3_uart0.img and ran adb shell ota_update and the red-white FW update progress bar showed for 3 seconds and the camera crashed and rebooted. The output on my computer said something is wrong with the firmware file, ("iamge" should be "image" in the message). If you google the error message in the code box, you'll find allwinner source code on github. 🤓 . The process deleted the 'sun8iw12p1_linux_v5s_pro_lpddr3_uart0.img' file from the sd card.
      Code:
      sunxi sprite error: iamge magic is bad
      .
      What "magic" data is needed in the firmware file to be compatible with the camera?
      Last edited by petesimon; 09-28-2019, 05:30 PM.

      Comment


      • nutsey
        nutsey commented
        Editing a comment
        The magic bytes are: IMAGEWTY

      • petesimon
        petesimon commented
        Editing a comment
        to clarify ... I did NOT brick my camera when I did those actions on 28th of September ... So I had used the camera for a few days after 28th of September.

        but now I'm "in the same boat" as vzzbx . I recently bricked 🧱 my camera 😭 on the 7th of October when I made a PhoenixSuit IMG file using a imgrepacker tool from the 'makeimg' zip file and copied the IMG file as 'sun8iw12p1_linux_v5s_pro_lpddr3_uart0.img' file onto the sd card and ran the adb shell ota_update command. Be advised ... DO NOT update or flash firmware into this camera

      • vzzbx
        vzzbx commented
        Editing a comment
        @petesimon: bummer to hear you have bricked yours as well. It seems there are enough differences between the old v3s and this v316 that the backup scripts and the Phoenixsuite are not working well with the new processor (yet). When I compared the boards from a v3s cam and the new v316 cam a few weeks ago I noticed it was really very different. The V316 seems much more integrated.

    • #26
      rem Chinese this website -- post "Unapproved"

      Click image for larger version

Name:	image_2577.jpg
Views:	135
Size:	52.1 KB
ID:	15601

      Comment


      • petesimon
        petesimon commented
        Editing a comment
        LoL 🤣 I don't understand "rem Chinese" but it's so funny and coincidentally ironic because I'm staying in Taiwan and people here actually speak Chinese! 😆

        Dav - bu seriously, what are you trying to write in your message?

      • Dav
        Dav commented
        Editing a comment
        [urlhttps://www.goprawn.com/forum/allwinner-cams/14697-allwinner-v316?p=15598#post15598[/url]

        this link 26 post

        this post No. 27 a real post No. 26 turns invisible.

        @ petesimon
        I think I solved the problem
        there link on archive zip. I made a backup using your script for allwinner v5 (backup.com)

        https://www.goprawn.com/forum/allwin...5614#post15614
        Last edited by Dav; 09-28-2019, 10:32 PM.

    • #27
      petesimon need to to know and try to do update as this is done on phone nexus 4

      Click image for larger version  Name:	1.jpg Views:	1 Size:	28.3 KB ID:	15607

      "adb devices -l"

      rem

      https://mdforum.su/showthread.php?t=548

      Click image for larger version  Name:	3.jpg Views:	0 Size:	47.6 KB ID:	15606
      https://www.droid-life.com/2013/02/1...r-the-nexus-4/
      Last edited by Dav; 09-28-2019, 09:46 PM.

      Comment


      • #28
        repeat post 26 ((accounts individually to write - if all to join this site says -> "Unapproved"))

        Windows 10 x64. ADB connects only when Q6H is power off:
        1-Q6H power off.
        2-sticking the usb wire.
        3-Q6H turns on.
        4-select "charge battery".
        in the terminal (cmd.exe) to type
        "adb devices"
        if you pull out usb from PC then you need again to turn off the power to the camera and the new ...look №1..and etc.

        https://www.goprawn.com/forum/allwin...5598#post15598

        http:// yadi.sk/d/XEwkaYUYY2zg0Q

        Comment


      • #29
        petesimon

        after that, run the fastboot command

        "fastboot flash partition_name filename.img"
        example (look mtd.txt and partition.txt)

        1-fastboot flash uboot mtdblock0.img
        2-fastboot flash boot mtdblock1.img
        and etc
        Last edited by Dav; 11-10-2019, 09:57 PM.

        Comment


        • petesimon
          petesimon commented
          Editing a comment
          fastboot command may not work for Chinese cameras
          'mtdblock0' to 'mtdblock6' device files should be in the '/dev/' directory but not in the '/dev/block' directory

      • #30
        Uploaded V316 stuff that we see here in Goprawn to my Github account - https://github.com/petesimon/allwinner-V316

        You also can upload your new V316 stuff to this repository. Contact me. I would appreciate it very much. Instructions are here - https://help.github.com/en/articles/...nal-repository

        click on this small picture
        Click image for larger version  Name:	Github V316, Screenshot from 2019-10-01 00-00-45.jpg Views:	0 Size:	73.2 KB ID:	15658

        Comment

        Working...
        X