Potential boot issue (related to uboot) with OMAP35x-PSP-SDK-02.01.03.11

We used " OMAP35x-PSP-SDK-02.01.03.11" for OMAP3530 boards(beagle board and OMAP35xx EVM board). The u-boot code was built and tested on the beagle board and EVM boards. We found that there was no exception dumps coming when there is any exception scenario encountered. When an illegal address was accessed from the u-boot prompt, the CPU just hangs, CPU is not resetting also. Ideally, an exception dump should be put on the console and CPU should reset on a non recoverable interrupt. This is not happening with the u-boot code that is being used. Same in the case of x-loader. - The same issue is seen with "OMAP35x-PSP-SDK-02.01.01.08" SDK code base too. - Further debugging showed that the exception handler pointers are not copied to the right locations in the onchip SRAM space in the 'start.S' file of u-boot/x-loader code. With the board running, at the u-boot prompt, manually copied(mw/mm commands) the exception handler pointers to the correct locations in the on-chip SRAM. Was now able to see the exception dumps when an illegal address was accessed and the CPU rebooted! We feel a a fix is required in the start.S code.