Hi Thomas,
It is only the last couple of weeks that have seen me getting the system this far, if you remember I stalled moving forward whilst waiting for a real time clock facility.
Anyway, looks like it may be software and not hardware,
For your own interest see the screenshot below
from the issuing of the command pip a:test.com=a:get.com we can see the following sectors accessed
1) LBA 41H is read (directory) to locate the program pip.com (first green box) - CORRECT
2) pip.com is read into memory LBA 1F0H to 200H - CORRECT
3) pip.com then issues a directory read LBA 40H to find the sectors relating to get.com - CORRECT
4) get.com read into buffer LBA 148H to 154H -CORRECT
5) pip.com reads the directory sector 44H into memory to add a directory entry, this is correct , last sector with entries in.
6) look like pip.com then writes the direcotry back to sector 44H (note write command) - CORRECT
7) then pip.com proceeds to write the buffer containing get.com into sector 44H to 47H - WRONG!!!
in fact with an emptier CF card image you can see that the directory entry is created but it allocates the first AU as 01H so based on that it writing to the correct location, question is why is it writing to AU 01H at all ??
8) the following green boxed area is where CCP.COM is loaded back in before the command prompt returns.
Good Eh.... I'll let you know what it is when I track it down.
regards
David Fry
On Wednesday, June 25, 2014 5:51:31 PM UTC+1, Thomas Owen wrote:
Hello a David,
I wish I could help you but my system serial I/O is run from a Compupro system support 1 at 0D and 0C and I am not familiar with the propeller board at all.
I do tend to agree, it sounds like a hardware issue, but with all the work you did leading up to this with other images, did you ever see a 'write' go like this?
Good luck and let me know if I can help in any way.
Thomas