Messages

the top of flash range problem is now gone w/4.21, thanks again.  I've tried to reinstall/re-reg RICHED20.dll and I still get my errors. For the record, here is the error msg as you requested (I missed that request earlier):

ah - good idea. I'll see if that fixes anything.

sorry, forgot another:
I make sure the sector/mem range drop-down is in focus and use the scroll button on the mouse to move through sectors quickly and I also get the exceptions too.

I think I've found another way to break it ... I slow it down to 19.2k and then while it's downloading the sector (before it finished) I grab the slider on the right and scroll it - I get an instant exception.

We have kept small count value ( count = FF ) and not feeding the feed sequence
again so that Watch Dog Timer should reset our controller. Is it a
good way to reset the controller using Watch dog Timer or is there
any better way to achieve this...?

giving an incorrect feed sequence will also cause a reset

everytime at 57.6k, backing down 38.4 works.  xp v5.1.2600

I'll grab some screenshots if it helps any. I also have the problem of using 'save as..' and it thinks that 0x2ffff is the top of mem, so I have to use lpc2368 to read out that last 64k.

same here. 4.18.1224 production

i'm using an lpc2366, and whenever I try to read the larger sectors (32k) it happens. I slow the speed down and it goes away.

I get a lot of null reference msgbox's before I have to kill it.