From: Carsten S. <c.s...@ko...> - 2007-05-23 11:01:25
|
Hi Dominik, > You could run into problems when using a working_area, as I > barely tested this with XScale, but it could very well work > just as it is. Unfortunatelly it doesn't. First it didn't work at all. After switching off MMU and I/D CACHES previously enabled by the RedBoot code, I can now do (protection|erase)_check runs. Anway, writing data with "flash write ..." always fails. First I got messages about "insufficient workspace". I increased workspace size to about 0x40000, and the flash binary is uploaded and a HW BP is set. After that some data is uploaded and the flash code is called - but never returns. So flashing writes end with a timeout. I will create some log output for this, and sent it directly to you later. If will help fixing the problem, just point out how to 'debug' the flash code the best way... The other features of OpenOCD seem to work. There are some other cosmetical issues, e.g. I would like to see a progress bar, "spinning staff" or other indicator on load_image to indicate that OpenOCD is indeed still working and transfers are going on. At the moment I have to use debug level 3 to get some feedback, but also some big slow-down... Regards Carsten ____________ Virus checked by G DATA AntiVirusKit Version: AVK 17.4853 from 23.05.2007 ____________ Virus checked by G DATA AntiVirus Version: AVK 17.4854 from 23.05.2007 Virus news: www.antiviruslab.com |