The support for varies of resolution set (upto 10Mp)are documented in v3.0 datasheet, yet I failed to find any selections larger than 1080p in any stream combinations. I've tried both the full and low power using NAND and SD,is there something wrong with the web GUI app?
Meanwhile,the bootloader's env seems not changeable on SD card, regardless of lock state. Is there any further information about making the boot.scr?
We have the same problem. There is no option for 10mp streaming, and release notes for GA_3.0.0 said there should be. Can someone from TI tell us something more about this. When can we expect to get 10mp streaming?
Hi,
In low-power mode,in GUI select : Tri-stream ->H264+H264+MJPEG -> 10MP...
Regards.
GA_3.0.0 low power mode:
Single and Dual steam work properly.
Tri-stream only works with 1080p. For higher resolution (5MP, 8MP and 10MP) the displayed image is black. When you are in some of those modes and want to switch to another mode (single or dual stream which works properly at the first time), there is the message "login faled". Only camera reset solves this problem.
In any case, there is no video stream resolutions higher than 1080p. When you choose this higher resolution in the three-stream mode, there is not shown any pictures, ie. the image is black.
Does anyone have the same problem?
Regards,Jelena
Hi Jelena,
Can you delete old configuration files on camera. In console type : rm /mnt/nand/*Then restart camera.
Marko,
I tried that (deleting configuration files), but no help.Actually, in the meanwhile firmware was broken several times. I managed to solve that by flashing system from the beginning.
But, at the end the camera stopped to work completly, and I got message like this:
Starting kernel ...
Uncompressing Linux... done, booting the kernel.Trying to install type control for IRQ375Trying to set irq flags for IRQ375omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!_omap_mux_init_gpio: Could not set gpio79_omap_mux_init_gpio: Could not set gpio80omap_voltage_late_init: Voltage driver support not addedUBI error: ubi_io_read: error -74 (ECC error) while reading 131072 bytes from PEB 1479:0, read 131072 bytesUBI error: torture_peb: read problems on freshly erased PEB 1479, must be badUBI error: erase_worker: failed to erase PEB 1479, error -5UBI error: ubi_io_read: error -74 (ECC error) while reading 126976 bytes from PEB 327:4096, read 126976 bytesUBI error: ubi_io_read: error -74 (ECC error) while reading 131072 bytes from PEB 1478:0, read 131072 bytesUBI error: torture_peb: read problems on freshly erased PEB 1478, must be badUBI error: erase_worker: failed to erase PEB 1478, error -5UBI error: ubi_io_read: error -74 (ECC error) while reading 126976 bytes from PEB 295:4096, read 126976 bytesUBIFS error (pid 1): replay_log_leb: log error detected while replaying the log at LEB 3:0Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)Backtrace:[<c0046ba0>] (dump_backtrace+0x0/0x110) from [<c0356468>] (dump_stack+0x18/0x1c) r7:c4414000 r6:c006c550 r5:c002c754 r4:c04abbd0[<c0356450>] (dump_stack+0x0/0x1c) from [<c03564cc>] (panic+0x60/0x17c)[<c035646c>] (panic+0x0/0x17c) from [<c00092b4>] (mount_block_root+0x1e0/0x220) r3:00000000 r2:00000020 r1:c4425f78 r0:c0400e3c[<c00090d4>] (mount_block_root+0x0/0x220) from [<c0009454>] (prepare_namespace+0x94/0x1d4)[<c00093c0>] (prepare_namespace+0x0/0x1d4) from [<c00087c4>] (kernel_init+0x114/0x154) r5:c00086b0 r4:c04ab400[<c00086b0>] (kernel_init+0x0/0x154) from [<c006c550>] (do_exit+0x0/0x5e4) r5:c00086b0 r4:00000000
Jelena,
UBI errors has something to do with ECC errors when using UBIFS filesystem.Nand blocks get marked false bad over time, so you will have to fix this with "nand scrub".I hope TI, or someone will fix this issue in the next IPNC release, since almost everyone has this problem.Before reflashing, you need to do "nand scrub" from uboot, to fix incorrectly marked nand bad blocks.You can check bad blocks with "nand bad".If you don't want to reflash uboot, then do "nand scrub" only on that nand range where kernel and filesysem are flashed.e.g "nand scrub 0x280000 0xFD80000". Note that nand scrub will erase all data on the selected range. If you erase uboot, you will have to reflash it by CCS or SDCard.-------------------Anyway if you boot from NFS kernal + filesystem, you won't get UBI errors. And you can try 10MP from NFS.Or you can try SDCard boot. Look at: IPNC_RDK_InstallGuide_Version3.0.0.pdf : 1.6.6 Flashing images to NAND Using SD Boot, 3.1.2 Boot from SD-----------------
I might be able to help you out with UBIFS issues. Could you please send me the following files to renjith.thomas@pathpartnertech.com?
arch/arm/mach-omap2/board-ti8127evm.c or the relevant board file for your platform? arch/arm/mach-omap2/board-flash.c arch/arm/mach-omap2/gpmc.c drivers/mtd/nand/nand_base.c drivers/mtd/nand/omap2.c
Also send me the steps followed in creating/flashing the ubi image? Send the complete logs as well.
-Renjith | www.pathpartnertech.com | Verify the answer if you think your query is resolved
Thank you all for the help and advices.At the moment we need to do some tests with high resolutions, so we went back at old and more stablie release Ver2.8 low power mode which has support for resolutions up to 8MP.
Later we will come back to GA3.0.0. Maybe in meantime TI come up with some new and more stabile version.