copy file to F: drive and OALStall

DavidVescovi

BSP A8_01.01.00

There are several makefile.inc's in the bootloader subdirectory that copy the output file to an "F:" drive.

This is bad practice. My "F:" drive is not used for this stuff.

Also, you might want to check the timing delays in the bootloader. According to my viewing on an o'scope all the delays are exactly half of what the comment says:

For example:

// wait for at least 1000us

OALStall(1000);

ends up being ~500us.

over 14 years ago

0 Madhvi over 14 years ago

TI__Expert 5320 points

David

We had also noticed the F:\ and have already removed it in our source tree. The change should be there in the next release.

Regarding timing, we will review it on our end.

Thanks
Madhvi

0 Gary Tominovich over 14 years ago in reply to Madhvi

TI__Genius 10960 points

The 1st issue was caught/fixed in our EC7 drop and should be addressed in our next WinCE 6 maintenance release (01.02.00, being tracked as SDOCM00079743).

The 2nd issue is being investigated in our EC7 BSP and depending on the outcome, may also be fixed the 01.02.00 release.

Processors

Processors forum

copy file to F: drive and OALStall