The problem may have been found. I have used the debug version of Offscreen Test on my FireBee and sent the logs to Daroou. His analysis is:Orion_ wrote:This is what I get on my Firebee (FireTos or mint) running the program from A: (sdcard)
it starts with a little black screen in the upper left corner (during "chargement image...")
same result in both 16bits or 32bits
- EdDI cookie is not involved in the issue
- the bad behavior still is located in the Offscreen VDI.
See the v_opnbm() documentation : "If bitmap->fd_addr is zero, the VDI will allocate memory for the bitmap and will clear it [...] To open a bitmap in device-specific format, bitmap->fd_nplanes should be zero, or the number of planes of the screen (work_out[4] from vq_extnd). [...] If bitmap->fd_addr is not zero, it will be used as pointer to a bitmap. "
Choice is proposed to use a coder's filled MFDB or a zero-filled MFDB that the VDI is supposed to modify.
Daroou's prefered to use a zero-filled MFBD, for the VDI to fill it. NVDI is doing its job, but the internal FireTOS VDI (fVDI) does not. Thus explaining the writings on the screen. Seems wiser to fill oneself the MFDB.
He's working on this fix, among other things, for the next release.
?