RTSP client connection causes segmentation fault on XM530 about majestic HOT 7 OPEN

I have the same problem only other sensor.

OpenIPC/firmware#1425

the two issues are related

will there be a fix?
no one has responded to the error :(

from majestic.

will there be a fix?
no one has responded to the error :(

The fix is to throw XM chips in the trash xD
Openipc is not a miracle and it cant make it work any better.

from majestic.

Good afternoon
For quick answers, we have chats, where there is an intensive exchange of information.
https://openipc.org/our-channels

You can install firmware from the Dev channel in Telegram released before January 1, 2024 and it should work.
The problem is related to Buildroot toolchain updates.

from majestic.

I tried lots 2023 version. Not working :(

from majestic.

Good afternoon For quick answers, we have chats, where there is an intensive exchange of information. https://openipc.org/our-channels

You can install firmware from the Dev channel in Telegram released before January 1, 2024 and it should work. The problem is related to Buildroot toolchain updates.

The problem is with majestic. I have XM SDK and I can operate the camera with openipc. I can create jpg from command line. Without majestic source code I cannot do further tests.
Possible bug that majestic is detecting the resolution of the senzor wrong. My sensor is 1280x720 (OV9732) but majestic tries to encode in 1920x1080. If I change the resolution from the command line the image appears in RTSP but I get a segmentation error.

wrong majestic encode init enSize is 14:

DEBUG: libfvideo: OV9732!
DEBUG: isp_sample end!
DEBUG: imageStyle XM!
12:04:59 < majestic> [ sdk] ViChnConfig@164 ViChn = 0, enSize = 14
12:04:59 < majestic> [ sdk] COMM_VENC_Start@249 VencChn = 0, enType = 96, enSize = 14 (1920x1080), enRcMode = 1

correct init form command line test code with SDK enSize is 11:

DEBUG: Init over ~~~~~~~~
DEBUG: ProductType: 0x0
DEBUG: libfvideo: OV9732!
DEBUG: isp_sample end!
DEBUG: imageStyle XM!
[ViChnConfig]-85: ViChn = 0,enNorm = 0,enSize = 11
[COMM_VENC_Start]-167: VencChn = 0,enType = 96,enNorm = 0,enSize = 11,enRcMode = 0
[COMM_SYS_GetPicSize]-152: enNorm = 0,enPicSize = 11
XM_MPI_ISP_MemInit OK...

It would be nice to be able to override the encoding resolution in the majestic config file but unfortunately I can't.

from majestic.

Possible bug that majestic is detecting the resolution of the senzor wrong

No, it's not the case. My sensor is detected correctly. The issue is with rtsp implementation (you can watch the video with HLS streamer, for example). And yes, I've tried several 2023 versions as well and they act exactly the same.

from majestic.

Possible bug that majestic is detecting the resolution of the senzor wrong

No, it's not the case. My sensor is detected correctly. The issue is with rtsp implementation (you can watch the video with HLS streamer, for example). And yes, I've tried several 2023 versions as well and they act exactly the same.

In your case the error may be a bit different than mine but they are still related. i have a double error :(

from majestic.