imx290用3559a自带的驱动跑着没问题，mipi 1080p30的，现在想改个1080p60的，按照手册改了寄存器结果出来是黑红蓝的竖纹，请教下哪位大神遇到过这个问题么？ sensor配置是在1080p30的基础上改的 [code]     imx290_write_register(ViPipe, 0x3000, 0x01);  // standby     imx290_write_register(ViPipe, 0x3002, 0x01);  // XTMSTA     imx290_write_register(ViPipe, 0x3005, 0x01);  // ADBIT     imx290_write_register(ViPipe, 0x3129, 0x00);  // ADBIT1     imx290_write_register(ViPipe, 0x317c, 0x00);  // ADBIT2     imx290_write_register(ViPipe, 0x31ec, 0x0e);  // ADBIT3     imx290_write_register(ViPipe, 0x3441, 0x0c);  // CSI_DT_FMT 0x0c0c: raw12 0x0a0a: raw10     imx290_write_register(ViPipe, 0x3442, 0x0c);  // CSI_DT_FMT     imx290_write_register(ViPipe, 0x3007, 0x40);  // 0x00: all pixels 0x04: cropping     imx290_write_register(ViPipe, 0x3009, 0x01);  // 0x02: 30fps 0x01: 60fps 0x00: 120fps     imx290_write_register(ViPipe, 0x300c, 0x00);     imx290_write_register(ViPipe, 0x300f, 0x00);     imx290_write_register(ViPipe, 0x3010, 0x21);     imx290_write_register(ViPipe, 0x3012, 0x64);     imx290_write_register(ViPipe, 0x3016, 0x09);     imx290_write_register(ViPipe, 0x3017, 0x00);     imx290_write_register(ViPipe, 0x301c, 0x98);  //0x1130: 30fps 0x898: 60fps     imx290_write_register(ViPipe, 0x301d, 0x08); #if 1     imx290_write_register(ViPipe, 0x3020, 0x01);  // SHS1     imx290_write_register(ViPipe, 0x3021, 0x00);     imx290_write_register(ViPipe, 0x3024, 0x00);  // SHS2     imx290_write_register(ViPipe, 0x3025, 0x00);     imx290_write_register(ViPipe, 0x3028, 0x00);  // SHS3     imx290_write_register(ViPipe, 0x3029, 0x00);     imx290_write_register(ViPipe, 0x3030, 0x00);  // RHS1     imx290_write_register(ViPipe, 0x3031, 0x00);     imx290_write_register(ViPipe, 0x3034, 0x00);  // RHS2     imx290_write_register(ViPipe, 0x3035, 0x00); #else     imx290_write_register(ViPipe, 0x3020, 0x02); #endif     imx290_write_register(ViPipe, 0x305c, 0x18);     imx290_write_register(ViPipe, 0x305d, 0x03);     imx290_write_register(ViPipe, 0x305e, 0x20);     imx290_write_register(ViPipe, 0x305f, 0x01);     imx290_write_register(ViPipe, 0x3070, 0x02);     imx290_write_register(ViPipe, 0x3071, 0x11);     imx290_write_register(ViPipe, 0x309b, 0x10);     imx290_write_register(ViPipe, 0x309c, 0x22);     imx290_write_register(ViPipe, 0x30a2, 0x02);     imx290_write_register(ViPipe, 0x30a6, 0x20);     imx290_write_register(ViPipe, 0x30a8, 0x20);     imx290_write_register(ViPipe, 0x30aa, 0x20);     imx290_write_register(ViPipe, 0x30ac, 0x20);     imx290_write_register(ViPipe, 0x30b0, 0x43);     imx290_write_register(ViPipe, 0x3119, 0x9e);     imx290_write_register(ViPipe, 0x311c, 0x1e);     imx290_write_register(ViPipe, 0x311e, 0x08);     imx290_write_register(ViPipe, 0x3128, 0x05);     imx290_write_register(ViPipe, 0x313d, 0x83);     imx290_write_register(ViPipe, 0x3150, 0x03);     imx290_write_register(ViPipe, 0x317e, 0x00);     imx290_write_register(ViPipe, 0x315e, 0x1a);     imx290_write_register(ViPipe, 0x3164, 0x1a);     imx290_write_register(ViPipe, 0x32b8, 0x50);     imx290_write_register(ViPipe, 0x32b9, 0x10);     imx290_write_register(ViPipe, 0x32ba, 0x00);     imx290_write_register(ViPipe, 0x32bb, 0x04);     imx290_write_register(ViPipe, 0x32c8, 0x50);     imx290_write_register(ViPipe, 0x32c9, 0x10);     imx290_write_register(ViPipe, 0x32ca, 0x00);     imx290_write_register(ViPipe, 0x32cb, 0x04);     imx290_write_register(ViPipe, 0x332c, 0xd3);     imx290_write_register(ViPipe, 0x332d, 0x10);     imx290_write_register(ViPipe, 0x332e, 0x0d);     imx290_write_register(ViPipe, 0x3358, 0x06);     imx290_write_register(ViPipe, 0x3359, 0xe1);     imx290_write_register(ViPipe, 0x335a, 0x11);     imx290_write_register(ViPipe, 0x3360, 0x1e);     imx290_write_register(ViPipe, 0x3361, 0x61);     imx290_write_register(ViPipe, 0x3362, 0x10);     imx290_write_register(ViPipe, 0x33b0, 0x50);     imx290_write_register(ViPipe, 0x33b2, 0x1a);     imx290_write_register(ViPipe, 0x33b3, 0x04);     imx290_write_register(ViPipe, 0x3405, 0x10);  //0x20: 30fps 0x10: 60fps 0x00: 120fps     imx290_write_register(ViPipe, 0x3414, 0x0a);     imx290_write_register(ViPipe, 0x3418, 0x49);     imx290_write_register(ViPipe, 0x3419, 0x04);     imx290_write_register(ViPipe, 0x3444, 0x20);     imx290_write_register(ViPipe, 0x3445, 0x25);     imx290_write_register(ViPipe, 0x3446, 0x57);     imx290_write_register(ViPipe, 0x3447, 0x00);     imx290_write_register(ViPipe, 0x3448, 0x37);     imx290_write_register(ViPipe, 0x3449, 0x00);     imx290_write_register(ViPipe, 0x344a, 0x1f);     imx290_write_register(ViPipe, 0x344b, 0x00);     imx290_write_register(ViPipe, 0x344c, 0x1f);     imx290_write_register(ViPipe, 0x344d, 0x00);     imx290_write_register(ViPipe, 0x344e, 0x1f);     imx290_write_register(ViPipe, 0x344f, 0x00);     imx290_write_register(ViPipe, 0x3450, 0x77);     imx290_write_register(ViPipe, 0x3451, 0x00);     imx290_write_register(ViPipe, 0x3452, 0x1f);     imx290_write_register(ViPipe, 0x3453, 0x00);     imx290_write_register(ViPipe, 0x3454, 0x17);     imx290_write_register(ViPipe, 0x3455, 0x00);     imx290_write_register(ViPipe, 0x3480, 0x49);     imx290_default_reg_init(ViPipe);     imx290_write_register(ViPipe, 0x3000, 0x00);  // standby     delay_ms(20);     imx290_write_register(ViPipe, 0x3002, 0x00);  // master mode start     imx290_write_register(ViPipe, 0x304b, 0x0a);  // XVSOUTSEL XHSOUTSEL[/code]

本帖最后由 antoniofay 于 2019-4-19 14:29 编辑 cat /dev/logmpp一直是这个错误请问有人知道什么原因么 补充下,程序在开发板上跑的是没有问题的,在自己做的板子上有一块是这个现象,两个摄像头只有0号是正常的,1号就会出现上面的错误.另外一块是两个摄像头都会出现这样的问题.

请问有谁用3559a的GPU做过实时渲染的么？性能能达到4K60么？

海思的h265裸流用ffmpeg打包成ts文件，能正常工作，但是发现pts最大只有33位，也就是26.5小时左右，录像超过这个时间戳就归零只会播放最后一段视频。有大神遇到过这个问题吗？有解决方法么？感恩

跟着手册做的系统，u-boot下mmc read 0 0x50000000 0x800 0x4800;bootm 0x50000000启动linux big_little，然后load_liteos 0 0x45000000 ./sample_vio.bin启动的liteos，虚拟串口进去后sample 1启动程序，发现输出的是蓝屏，cat_logmpp也正常的，输出 <3>[   isp] [Func]:cmos_set_wdr_mode [Line]:1090 [Info]:linear mode <3>[   isp] [Func]:cmos_set_wdr_mode [Line]:1090 [Info]:linear mode 同样的程序在linux多核系统下就能正常运行，请教各位大牛有什么地方有问题么？或者有谁成功跑过3559a的liteos么？

看HDMI开发参考手册写着b3DEnable默认为0，35XX不支持该项使能。u83DParam默认为9，暂不支持其他值。海思也没公开hdmi驱动的源码，有什么其他方法实现么。

看手册说mipi 2lane的模式lane ID是0,2 1,3 4,6 5,7这样的组合，但是看sensor2lane输出又是0,1，是不是说用2lane模式的时候要求sensor的data要交叉，也就是说不是4lane模式下的sensor0对主板0,sensor1对主板1，sensor2对主板2，sensor3对主板3.而是sensor0对主板0，sensor1对主板2