This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

uVision4 Beta 3 Bugs

Hello,
I've got serious problems with the uVision4 starting a debug session.

1. I hit the debug button in the toolbar.
2. uVision4 starts to upload the programmcode.
3. After successfull upload it says Window Layout in the statusbar and here the trouble start: Sometimes it takes uVision several seconds to get the windows setup. Sometimes it takes way over 30 seconds until uVision4 is ready to debug and sometimes uVision just crashes or freezes.

I must say this is quite an annoying problem with the uVision4 IDE. I like what I've seen so far except this serious problem!

Will this get fixed and is anyone else having similar problems?

Greetings
Jan

Parents
  • I have just started to use UV4 via MDK 4.01 and I have both problems.

    Sometimes debug in UV4 takes a long time to start, although sometimes its as quick as it is UV3. Initial I thought UV4 had crashed but it just stalls for 30+ seconds. The stalling seems to happen for no apparent reason to me.

    I also have the problem with the flash programming. UV3 and UV4 stall and look crashed until program erase/flashing has completed. This has happened to me ever since I upgraded to MDK 3.80. It coincided with an update to our Unlink2 devices caused by the upgrade to MDK 3.80, not sure if this is related?

    I think I will have to use UV3 until the first problem is resolved. The second one I can live with but would obviously like fixed.

    Stuart

Reply
  • I have just started to use UV4 via MDK 4.01 and I have both problems.

    Sometimes debug in UV4 takes a long time to start, although sometimes its as quick as it is UV3. Initial I thought UV4 had crashed but it just stalls for 30+ seconds. The stalling seems to happen for no apparent reason to me.

    I also have the problem with the flash programming. UV3 and UV4 stall and look crashed until program erase/flashing has completed. This has happened to me ever since I upgraded to MDK 3.80. It coincided with an update to our Unlink2 devices caused by the upgrade to MDK 3.80, not sure if this is related?

    I think I will have to use UV3 until the first problem is resolved. The second one I can live with but would obviously like fixed.

    Stuart

Children