DLPC350: Followup question on issue: After update of DLPR350PROM from 3.1.0 to 4.0.3 we observe glitch on trigger out 1 for all settings of rising edge delay except 0x00

Hello Anders,

Please allow us to look into this and we'll get back to you.

Thanks,

Kyle

Hi Anders, 

The FW is in final testing stage and will be released shortly. If this is blocking your development progress we can work to provide a test build to continue your development. 

Thanks & Regards,

Hirak.

Hi again Kyle!

Any update on this? Can you please provide a test build while we are waiting for an official build? This is going to stop our production very soon.

I've read the changelog from 3.1.0 to 4.0.3 fw, and it mentions the following:

1. Video sequences updated to support DLP4500AFQE, DLP4500AFQD and DLP4500NIRAFQD devices
2. Standby command (I2C: 0x07; USB: CMD2:0x02, CMD3:0x00) modified to support DLP4500AFQE, DLP4500AFQD and DLP4500NIRAFQD devices

If we are not using video-mode/pixel interface, only internal structured light pattern, does 1 affect us?
If we are not using standby command (only mirror park), does 2 affect us?

What would happen if we started using the new revision dmd's with the older 3.1.0 firmware? 
Any other things we should be aware of?

-Anders

Hi Anders, 

The new version of FW is in the final stage of release pipeline and we expect the new version to go live within a week. Do you still need a test build meantime? Kindly find the answers to your questions below:

If we are not using video-mode/pixel interface, only internal structured light pattern, does 1 affect us?

A> No, this does not affect your usage if you are not using video mode.

If we are not using standby command (only mirror park), does 2 affect us?

A> This affects you, because the new requirement is to always send a standby command before powering down the system. You need to send a standby

command before removing power from the system and use FW v4.0+

What would happen if we started using the new revision dmd's with the older 3.1.0 firmware? 

A> The new FW implements certain changes in operation required by the DMD process change in  DLP4500AFQE, DLP4500AFQD and DLP4500NIRAFQD devices. If the older FW is used with the new version of DMD, it significantly reduces the DMD longevity. I.e., the DMD mirrors may become non-functional sooner.

Thanks & Regards,

Hirak.

Hi again Hirak,

Thanks, if the new firmware is ready in a week, we do not need test build.

I have followup question for #2, standby command:

In the design we have today, we are using the "Proj_on_off" pin to set the projector in standby before power-loss. In our application, power can be suddenly lost, so we do not have time to send I2C command before powering down. Is this still sufficient and optimal, or are there any changes in the new firmware related to this? Timing changes maybe, anything?

Best
Anders

Hi again Hirak!

Thanks for your help so far. We have downloaded the latest 4.1.0 release, and it seems to work ok, it doesn't have the trigger-glitch we observed before. 

I do have one more questions though.

Comparing the binaries, I notice that the first part with bootloader is different between 3.1.0 and 4.1.0, What are the changes in the bootloader itself? We plan to upgrade units in the field, but we cannot update this bootloader in the field, as there is no safe way to do that. So we need to understand exactly why the bootloader binaries are different.

thanks

Anders 

Hi Anders,

The FW does not contain any change in bootloader binary from v4.0.3. Although, some of the application data in the beginning of the flash image (AFTER the bootloader binary) have been modified. This is necessary to support the new I2C_BUSY_GPIO feature.

Thanks & Regards,

Hirak.

Hi again,

I agree that there are no changes in bootloader binary from 4.0.3 to 4.1.0. But from 3.1.0 to 4.0.3/4.1.0 there are changes. The changelog between 3.1.0 and 4.0.3 versions does not mention anything about bootloader changes. Can you please find out what has changed between ? (could it be same source-code, but different compiler settings or something?)

Hi Anders, 

In the FW v4.0.3 readme you can find one bugfix mentioned as "Fixed I2C flash programming issue". This fix required changes in the bootloader section. That is why the bootloaders are different from v3.1.0 to v4.0.3. 

Thanks & Regards,

Hirak.

Hi again Hirak!

We already have units in the field with 3.1.0 bootloader that we want to update in the field without touching the bootloader (since it is not safe if powerloss occurs). Can you elaborate on exactly what the "I2C flash programming issue" is, and how to work around it for field upgrades? We need to updgrade main firmware over I2C in the field. Is there an errata describing the issue in detail?

Thanks

Anders