Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Bootloader - Testers needed #573

Closed
EliasKotlyar opened this issue Jul 15, 2018 · 117 comments
Closed

New Bootloader - Testers needed #573

EliasKotlyar opened this issue Jul 15, 2018 · 117 comments

Comments

@EliasKotlyar
Copy link
Owner

EliasKotlyar commented Jul 15, 2018

Hello everyone,

I have completed work on a new u-boot bootloader. I need someone for testing it out on different devices. The list includes:
Xiaomi Dafang -> was tested from @hyteoo, @benleb
Xiaomi Xiaofang 1S (64Mb) -> was tested from @paumove
Wyzecam Pan(128Mb) -> was tested from @l0gik @hcgonzalezpr
Wyzecam V2(128Mb) -> was tested from @hcgonzalezpr

The benefit is, that you can use FullHD and / or boot a kernel from microsd.

Attention : Please consider, that it may result in a completely hardbrick of your device, which may only be fixxed by desoldering/soldering the nand-flash. There is a recovery tutorial here:
https://github.com/Dafang-Hacks/spiflasher
Prepare for recovery before flashing!

I suppose that it will only work on devices which are really similar to the original Dafang. The original Dafang has DDR2_M14D1G1664A Ram(according to u-boot) and 128MB in size. If your Camera has different type/size of Ram, do not try to flash it! It is very likely that it will brick your device or at least have some malfunctions. Instead, please report your RAM Type and your RAM size here.

So if you are brave enough, please use the following tutorial and report your results here:
https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks/blob/master/hacks/flashinguboot.md

@benleb
Copy link

benleb commented Jul 15, 2018

works without problems on my df3 👍

@jmtatsch
Copy link
Collaborator

From what I have seen in the issues Xiaomi Xiaofang 1S and Wyzecam V2 may have only 64 mb ram so double check before flashing those models.

@EliasKotlyar
Copy link
Owner Author

Can someone provide a bootlog from the u-boot of Xiaofang 1S and Wyzecam V2? It would help to identify the size of the ram.

On a Dafang its like:

U-Boot 2013.07 (Jul 28 2017 - 17:10:01)
Board: ISVP (Ingenic XBurst T20 SoC)
DRAM:  128 MiB

Also a teardown would help to identify the RAM which is being used.

@EliasKotlyar
Copy link
Owner Author

Okey, found another way to find out how much Ram your camera have:
Run:

[root@DafangHacks:~]# cat /proc/cmdline 
console=ttyS1,115200n8 mem=104M@0x0 ispmem=8M@0x6800000 rmem=16M@0x7000000 init=/linuxrc root=/dev/mmcblk0p2 rootwait rootfstype=ext4 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)

Then just count all the mem variables together. mem + ispmem + rmem = Its 128Mb

@EliasKotlyar
Copy link
Owner Author

Okey, another update(last for today).
I was able to compile a 64Mb Version of the bootloader. I flashed it to my 128Mb Dafang, and it was able to boot. I suppose that it wont work the other way round, but if you are really unsure sure which one to take - take the 64mb Version.

So if someone with a 64Mb Device want to give it a try:
https://github.com/Dafang-Hacks/kernel_release/tree/master/uboot

Flash it using:

flash_eraseall /dev/mtd0
dd if=opensource-T20-V1.3-64MB.bin of=/dev/mtd0

@hcgonzalezpr
Copy link
Contributor

hcgonzalezpr commented Jul 17, 2018

I have a couple of Wyzecam V2 and a Wyzecam Pan:

All my Wyzecam V2 have 128mb and I had already manually hex-mod the original uboot fw to support 1080p. Here's teardown pics / cmd / uboot output.

Teardown:
https://imgur.com/a/XDkFqOZ

Cmdline:

[root@cam1:~]# cat /proc/cmdline
console=ttyS1,115200n8 mem=87M@0x0 ispmem=9M@0x5700000 rmem=32M@0x6000000  init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)

Uboot log:
https://pastebin.com/WkHZS2sJ

Edit :
I risk it and flashed the opensource uboot and it worked :)
Heres the output:

https://pastebin.com/inswKjLz

Edit 2:
I forgot to enable the uEnv.txt

@hcgonzalezpr
Copy link
Contributor

I haven't open my Wyzecam Pan yet, but heres the Cmdline:

[root@testcam:~]# cat /proc/cmdline
console=ttyS1,115200n8 mem=104M@0x0 ispmem=8M@0x6800000 rmem=16M@0x7000000 init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)

@EliasKotlyar
Copy link
Owner Author

@hcgonzalezpr : Many thanks! I suppose that its now proven, that its working on 128Mb Devices. There is still testing needed on 64Mb Devices.

@jpbarraca
Copy link

Xiaomi Xiaofang 1S (64MB): Seems to have failed (boots, enables/disables ircut, seems to reboot after some time), but had no time for further debug.

@EliasKotlyar
Copy link
Owner Author

@jpbarraca Can you try to remove the SDCard and check if it still boots? If so, remove uEnv.txt from your SDCard.

@jpbarraca
Copy link

Will try later tonight

@hcgonzalezpr
Copy link
Contributor

hcgonzalezpr commented Jul 17, 2018

@EliasKotlyar I flashed the openfirmware on the Wyzecam Pan, booted up fine.

But when I enabled the UEnv.txt on a later test it hung.
I'll remove the uEnv.txt from the sdcard when I get home.

It did boot with a blue light, meaning it it was trying to load the uEnv.txt file.

@cjsm74
Copy link

cjsm74 commented Jul 17, 2018

Hmm, my Dafang (DF3) seems to only have 64MB. 😞
So you should ALWAYS! check the amount of memory available before flashing.

[root@DAFANG4:~]# cat /proc/cmdline
console=ttyS1,115200n8 mem=41700K@0x0 ispmem=8M@0x28B9000 rmem=15644K@0x30B9000                                init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(bo                               ot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(back                               upd),2048k(backupa),256k(config),256k(para),-(flag)

@jpbarraca
Copy link

It boots but goes into the original firmware. With a uenv file, its stuck at Waiting for root device /dev/mmcblk0p2...

Card has 2 partitions (fat and ext3)

@EliasKotlyar
Copy link
Owner Author

@jpbarraca :
That sounds great that it boots in your original firmware without problems.

Can you try to modify your bootargs in your uEnv.txt? I suppose that its a memory related issue. You should change it to:

mem=32M@0x0 ispmem=8M@0x2000000 rmem=24M@0x2800000

@paumove
Copy link

paumove commented Jul 18, 2018

I have a Xiaomi Xiaofang 1S (64MB). The chip says T20. I'm now prepared to test the uboot. Some questions before...

The sdcard needs to have 2 partitions (fat+ext3)? ext3 or ext4? whats sizes?
I will modify the uEnv.txt to use 64MB, but which one should I use: "bootfromnand" or "bootfromsdcard"?
The uboot version to flash is v1.2 included in the "firmware_mod/uboot_flash" folder?

Thanks

@EliasKotlyar
Copy link
Owner Author

Hello @paumove ,

Thanks for your efforts.

  1. You dont need to have any special "partitions" for testing the u-boot. Just the normal Dafanghacks will work. I suppose that the other comments are about Completely Open Source Firmware - Testers needed #575.
  2. You dont need a uEnv.txt for testing the uboot. Its also refering to Completely Open Source Firmware - Testers needed #575.
  3. You will need to flash the "opensource-T20-V1.3-64MB.bin" from here https://github.com/Dafang-Hacks/kernel_release/tree/master/uboot

Flash it using:
flash_eraseall /dev/mtd0
dd if=opensource-T20-V1.3-64MB.bin of=/dev/mtd0

Greatings
Elias

@paumove
Copy link

paumove commented Jul 18, 2018

U-Boot 2013.07 DafangHacksV1.3-g96a42d5-dirty (Jul 16 2018 - 22:15:12)

Board: ISVP (Ingenic XBurst T20 SoC)
DRAM: 64 MiB
Top of RAM usable for U-Boot at: 84000000
Reserving 419k for U-Boot at: 83f94000
Reserving 32784k for malloc() at: 81f90000
Reserving 32 Bytes for Board Info at: 81f8ffe0
Reserving 124 Bytes for Global Data at: 81f8ff64
Reserving 128k for boot params() at: 81f6ff64
Stack Pointer at: 81f6ff48
Now running in RAM - U-Boot at: 83f94000
MMC: msc: 0
the manufacturer c8
SF: Detected GD25Q128

*** Warning - bad CRC, using default environment

You need somthing more? What can I do now to use normally as RTSP?

@EliasKotlyar
Copy link
Owner Author

@paumove : That looks really good! I suppose that there is no issue here.
Just continue working normal on your system. There are no features in this bootloader, except that you can now change the bootoptions via uEnv.txt. Also you can try to enable FULLHD-Stream, but i dont think that its possible on 64MB devices due to the lack of ram.

You can try to flash #575 - this will enable more options for your camera

@paumove
Copy link

paumove commented Jul 18, 2018

I can't run it on normal functioning (as I have done previously). I attach the serial log.
uboot_v1.3_64MB.log

Meanwhile I will try #575
Thanks

@EliasKotlyar
Copy link
Owner Author

@paumove : Ok i know whats happening. I have opened up a new issue for that:
#581

@hcgonzalezpr
Copy link
Contributor

@EliasKotlyar The Wyzecam Pan works perfectly with opensource-T20-V1.2.bin

Before:

[root@testcam:~]# cat /proc/cmdline
console=ttyS1,115200n8 mem=104M@0x0 ispmem=8M@0x6800000 rmem=16M@0x7000000 init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)

After: (with 1080p applied via uEnv.txt)

[root@testcam:~]# cat /proc/cmdline
console=ttyS1,115200n8 mem=87M@0x0 ispmem=9M@0x5700000 rmem=32M@0x6000000 init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)

@l0gik
Copy link

l0gik commented Jul 20, 2018

WyzeCam Pan (128Mb) flashed successfully here without issues, and FullHD is working great now -- hooray!

/proc/cmdline before flash:
console=ttyS1,115200n8 mem=104M@0x0 ispmem=8M@0x6800000 rmem=16M@0x7000000 init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)
And after flash:
console=ttyS1,115200n8 mem=87M@0x0 ispmem=9M@0x5700000 rmem=32M@0x6000000 init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)

@Daylights
Copy link

Hello, I have two Xiaofang S1's (64MB) which do not cope very well (not at all) with 720P/1080P RSTP streams. So far only 640x320 seems to be stable. I am willing to sacrifice 1 S1 to see if this new bootloader helps?

@jpbarraca
Copy link

It will not boot correctly due to an error detecting the sdcard but it should not become a paperweight. See #581

@th0ma5w
Copy link

th0ma5w commented Jul 20, 2018

I followed the tutorial with a Dafang and got a brick. I haven't opened the thing yet, and I have a couple of others to play with so I'm not put out, plus I always wanted to learn how to reprogram an eeprom, so that'll be fun, I have a flashing usb stick thing on order. Not sure I did anything wrong as far as the procedure? I didn't check the versions of the chips, though. The md5 sum of the binary I flashed matched and everything.

@th0ma5w
Copy link

th0ma5w commented Jul 20, 2018

Figured out what I did. I right clicked and copied the link to the binaries in the instructions, and flashed that. That turns out to be the GitHub repo listing where you would then find a link to download the raw file. I did this again when I went to flash my 2nd camera and noticed it wasn't updating and that is when I went back and checked what file I had downloaded.

I did this with the first camera as well I remember. Perhaps put a disclaimer. Maybe it is my method of working but I guess I always assume if someone points to a link that is supposed to be a binary I copy that link and use wget or curl and download it somewhere specific. But I guess I assumed too much!

@EliasKotlyar
Copy link
Owner Author

EliasKotlyar commented Jul 20, 2018

@Daylights : Please wait a little until we figure out a solution for a Xiaofang 1S. For now its booting, but there are still some problems with WIFI and sensor

@th0ma5w : Sorry for my mistake if i wrote some stupid link - but can you please point out which tutorial you mean? Are you meaning this one:
https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks/blob/master/hacks/flashinguboot.md

@jmtatsch
Copy link
Collaborator

@stve-a that doesn't sound good. I think you should invest in a serial bridge and/or spi flasher.

@EliasKotlyar
Copy link
Owner Author

@stve-a : Try to remove the sdcard. If its still not boots, you need to investigate that using a serial-bridge and/or a SPI flasher.

@stve-a
Copy link

stve-a commented Sep 25, 2018

Thanks @EliasKotlyar and @jmtatsch for your feedback.

The removal of the SD card was the first thing I tried to check out, but alas to no use.

It's a pitty because I think I did everything right, so I don't understand why other people were able to flash it succesfully.

On the sticker it mentions 1S and iSC5 between the chinese text under the foot of the cam.

cmdline output prior to the flash looked like:

[root@CAM02:~]# cat /proc/cmdline
console=ttyS1,115200n8 mem=41700K@0x0 ispmem=8M@0x28B9000 rmem=15644K@0x30B9000 init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)

Have others been succesfull with the 1S 64mb v2 flash ? Or is only the v1 flash confirmed ?

I don't have any problem getting some extra hardware to get access to the console (it's part of the tinkering) but I'm not all that savvy with soldering and/or electricity in general so the chip clip hardware gets my preference.

So could you guys validate the hardware before I buy it ?

I am looking at a CH341 like this:
https://ae01.alicdn.com/kf/HTB1kBCQcGzB9uJjSZFMq6xq4XXaL/1pcs-Smart-Electronics-CH340-CH340G-CH341-CH341A-24-25-Series-EEPROM-Flash-BIOS-USB-Programmer-with.jpg_640x640.jpg

And a chip clip like this:
https://images-na.ssl-images-amazon.com/images/I/618gvbpiTNL._SL1024_.jpg

Thanks for all the feedback and support, and thanks to all the people that help in the development of these hacks!

Regards
S

@reichley
Copy link
Contributor

reichley commented Oct 8, 2018

So I bricked my camera, pulled the flash chip and flashed new bootloader...ONLY to break a leg off the chip when attempting to solder back on. Ordered new chips and flashed bootloader. Confirmed it works (see in serial output) but realized I don’t have any other firmware on the chip...Would I get the 11-12MB demo.bin from Wyzecam (have Wyzecam v2) and flash using rom.layout? Just trying to figure out how to get all the right bin files on using flashrom. I know the cams aren’t much $$$ but I’m trying to get enough experience under my belt so I can start contributing to this awesome project.

@jmtatsch
Copy link
Collaborator

jmtatsch commented Oct 8, 2018

If you have flashed the custom uboot, you can also try the new rootfs (my pull request) or openfang rootfs directly. No need to flash the rom...

@reichley
Copy link
Contributor

reichley commented Oct 8, 2018

If you have flashed the custom uboot, you can also try the new rootfs (my pull request) or openfang rootfs directly. No need to flash the rom...

So below is my serial readout...I have my card as Ext3, cloned rootfs and it's not booting. Root of sd card has uEnv.txt (no changes from git clone). Any ideas? I asked about flashing the original firmware of the wyzecam v2 as if that was successful I'd simply do the micro bootloader and flash mtd0 after ssh (like with my other wyzecam v2s).

U-Boot SPL 2013.07-gc78f10c-dirty (Jul 21 2018 - 20:20:37)
pll_init:365
l2cache_clk = 375000000
pll_cfg.pdiv = 8, pll_cfg.h2div = 4, pll_cfg.h0div = 4, pll_cfg.cdiv = 1, pll_cfg.l2div = 3
nf=36 nr = 1 od0 = 1 od1 = 1
cppcr is 02404900
CPM_CPAPCR 0470890d
nf=42 nr = 1 od0 = 1 od1 = 1
cppcr is 02a04900
CPM_CPMPCR 07d0c90d
nf=50 nr = 1 od0 = 1 od1 = 1
cppcr is 03204900
CPM_CPVPCR 0320490d
cppcr 0x9a794410
apll_freq 860160000 
mpll_freq 1000000000 
vpll_freq = 1200000000
ddr sel mpll, cpu sel apll
ddrfreq 500000000
cclk  860160000
l2clk 286720000
h0clk 250000000
h2clk 250000000
pclk  125000000
DDRC_DLP:0000f003


U-Boot 2013.07-gc78f10c-dirty (Jul 21 2018 - 20:20:37)

Bootloader-Version: Dafanghacks v1
Board: Dafang 128MB (Ingenic XBurst T20 SoC)
DRAM:  128 MiB
Top of RAM usable for U-Boot at: 84000000
Reserving 419k for U-Boot at: 83f94000
Reserving 32784k for malloc() at: 81f90000
Reserving 32 Bytes for Board Info at: 81f8ffe0
Reserving 124 Bytes for Global Data at: 81f8ff64
Reserving 128k for boot params() at: 81f6ff64
Stack Pointer at: 81f6ff48
Now running in RAM - U-Boot at: 83f94000
MMC:   msc: 0
the manufacturer c8
SF: Detected GD25Q128

*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Setting yellow_gpio to off:
gpio_request lable = cmd_gpio gpio = 38
gpio: pin 38 (gpio 38) value is 1
Setting blue_gpio to off:
gpio_request lable = cmd_gpio gpio = 39
gpio: pin 39 (gpio 39) value is 1
Setting night_gpios:
gpio_request lable = cmd_gpio gpio = 81
gpio: pin 81 (gpio 81) value is 0
gpio_request lable = cmd_gpio gpio = 49
gpio: pin 49 (gpio 49) value is 0
gpio_request lable = cmd_gpio gpio = 25
gpio: pin 25 (gpio 25) value is 0
Setting USB enable:
gpio_request lable = cmd_gpio gpio = 47
gpio: pin 47 (gpio 47) value is 1
Setting Speaker enable:
gpio_request lable = cmd_gpio gpio = 63
gpio: pin 63 (gpio 63) value is 1
Setting Enable SDCARD:
gpio_request lable = cmd_gpio gpio = 43
gpio: pin 43 (gpio 43) value is 1
gpio_request lable = cmd_gpio gpio = 48
gpio: pin 48 (gpio 48) value is 0
Running SDupdate....
sdupdate - auto upgrade file from mmc to flash

Usage:
sdupdate LOAD_ID ADDR_START ADDR_END
LOAD_ID: 0-->u-boot
	 1-->kernel
	 2-->rootfs
	 3-->demo.bin
ex:
	sdupdate   (update all)
or 
	sdupdate 0 0x0 0x40000
Hit any key to stop autoboot:  0 
U-Boot> 

@ghost
Copy link

ghost commented Jan 24, 2019

I'm seeing intermittent video losses, as in, RTSP feed goes offline, then after a while it comes back up. This happens with a Dafang camera, flashed today, with the current u-boot. It's also ignoring uEnv.txt.

@woody4165
Copy link

Hi
I have a Dafang 128MB, how can I check if it's V1 or V2?

Thanks

@jmtatsch
Copy link
Collaborator

jmtatsch commented Feb 8, 2019

@woody4165 V2 Just means its the second version in that case. Fits all 128 MB Dafangs.

@jmturner
Copy link

So below is my serial readout...I have my card as Ext3, cloned rootfs and it's not booting. Root of sd card has uEnv.txt (no changes from git clone). Any ideas?

I have the same setup and same issue. My V2 never boots. My next step is to hook up the serial console but I am guessing it will match @reichley 's.

@Rocketboy235
Copy link

Rocketboy235 commented Feb 17, 2019

Hello, I am curious if it is possible if we can flash the custom bootloader onto our Wyzecams (v2) and then possibly revert back to the original Wyzecam firmware while on the custom boot loader or would it not be compatible? Currently my understanding is that the firmware that controls the Camera's main functionality (recording, etc), is separate from the bootloader firmware. Trying to understand if the original Wyzecam firmware requires the original bootloader to work normally. Thanks!

Also, does anyone know how to dump the current bootloader so I can back it up just in case? I assume the bootloader dumps will probably be the exact same between the same cameras (Wyzecam V2) right?
I saw some commands earlier above but not sure if I should do them for backing up the original bootloader.

@EliasKotlyar
Copy link
Owner Author

Hello @Rocketboy235

Yes, you can still use your original wyzecam firmware with the custom bootloader. Your understanding is correct. You can dump everything of your firmware with the following commands:
https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks/blob/master/hacks/firmware-dump.md

@InstigatorX
Copy link

@EliasKotlyar ... How would I restore original Wyze V2 software after loading this customer bootloader?

@EsEnZeT
Copy link

EsEnZeT commented Mar 3, 2019

@jpbarraca @rfenouil @EliasKotlyar

console=ttyS1,115200n8 mem=32M@0x0 ispmem=8M@0x2000000 rmem=24M@0x2800000

when you change cmdline parameters, how do you calculate the hex value after memory size?

  • ispmem=8M@0x2000000 rmem=24M@0x2800000
  • ispmem=4M@0x??? rmem=28M@0x???

@EliasKotlyar
Copy link
Owner Author

@InstigatorX You basically dont need to restore any software after you have installed this new bootloader. The bootloader is compatible with the original wyzecam software. However, if you really feel that you need to restore it, you can flash the original bootloader from wyze with the same method. Just replace the binary with the one from wyze.

@EsEnZeT
You start with the first parameter(mem) which starts at 0. You define the size of this parameter(for example) 32MB. This means, the next parameter(ispmem) should start after this 32MB. You need to convert this 32MB to bytes, and then convert them in a hexadecimal. So 32MB = 33554432 bytes = 0x2000000(hexadecimal).

@EsEnZeT
Copy link

EsEnZeT commented Mar 4, 2019

You start with the first parameter(mem) which starts at 0. You define the size of this parameter(for example) 32MB. This means, the next parameter(ispmem) should start after this 32MB. You need to convert this 32MB to bytes, and then convert them in a hexadecimal. So 32MB = 33554432 bytes = 0x2000000(hexadecimal).

@EliasKotlyar thank you very much!

@stale
Copy link

stale bot commented May 19, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label May 19, 2019
@stale stale bot closed this as completed May 26, 2019
@OrislavK
Copy link

OrislavK commented Sep 2, 2019

flashed Xiaofang 1S 64mb v2

Bootloader MD5:
3319029f732aa79df1377d613a8ad8e8

Bootloader Version:
U-Boot 2013.07-g4401361-dirty (Jul 24 2018 - 00:13:48)

Your CMDline is:
console=ttyS1,115200n8 mem=39M@0x0 ispmem=5M@0x2700000 rmem=20M@0x2C00000 init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)

with this parameters
mem=39M@0x0 ispmem=5M@0x2700000 rmem=20M@0x2C00000
the Xiaomi Xiaofang 1S 64Mb can do rtsp h264 stream FullHD 1920x1080 with 15fps
bitrate: 2000
video format: SMART
audio: mp3
in sample rate: 8000 / out: 44100

@spattinson
Copy link

I have Xiaofang 1s 64MB with T20L (well i think its an L not sure though)
I did the same as @KAA76 I cannot get FullHD. the md5 quoted by @KAA76 is not correct for Xiaofang 1S 64mb v2 unless i missed something, I have 1b3fcafab119afd36bf4270c1d3c4da1 ? Is there another repository somewhere?
here is memory info, stock vs the settings @KAA76 has, also the clock speed increases with this bootloader:

mem=41700K@0x0 ispmem=8M@0x28B9000 rmem=15644K@0x30B9000
mem=39M@0x0 ispmem=5M@0x2700000 rmem=20M@0x2C00000
CCLK:712MHz L2CLK:356Mhz H0CLK:200MHz H2CLK:200Mhz PCLK:100Mhz
CCLK:860MHz L2CLK:430Mhz H0CLK:200MHz H2CLK:200Mhz PCLK:100Mhz

@BiatuAutMiahn
Copy link

On the wayzecam v2, it seems that the camera will occasionally lock up, and a power cycle is the only way to recover

@Crap-Mayur
Copy link

guys can anyone provide me a full dump of spi flash coz i fucked it up and i dont know how to flash all partitions back in eeprom so if anyone have full backup please provide me i have rt809f and ch3412a both flasher

@BiatuAutMiahn
Copy link

what camera?

@Crap-Mayur
Copy link

what camera?

Wyze v2 i flashed it back using serial and spi now how to reconnect it with app coz it wont sound or shows it is in pairing mode

@Crap-Mayur
Copy link

image

@Crap-Mayur
Copy link

what camera?

U there bro??

@BiatuAutMiahn
Copy link

what camera?

U there bro??

Discord, biatu.aut.miahn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests