Trudie - The Next IDE Board

[tzok]

So I guess the ancient WinCUPL? If so, then my hint is - when you finish writing code, save it and close WinCUPL, then start it again, load your project, don't touch it, and then compile it. You can also use a Prochip Designer, for writing and compiling CUPL code for ATF15xx. Third option is to generate the POF file for EPM7128SLC84 (MAX7000) in Quartus II and convert it to JED with POF2JED tool, and then program the ATF with this file (but no CUPL there, only VHDL and Verilog).

[exxos]

So I guess the ancient WinCUPL? If so, then my hint is - when you finish writing code, save it and close WinCUPL, then start it again, load your project, don't touch it, and then compile it. You can also use a Prochip Designer, for writing and compiling CUPL code for ATF15xx. Third option is to generate the POF file for EPM7128SLC84 (MAX7000) in Quartus II and convert it to JED with POF2JED tool, and then program the ATF with this file (but no CUPL there, only VHDL and Verilog).

It be whatever the latest version is to download. I know it hasn't been supported for a long time and know its got some bizarre bugs, but how did you find out that changing code causes issues ? (have you used cupl then ?)

[tzok]

WinCUPL has a huge memory leaks, in my case the first symptom of this is that syntax highlighting crashes when I use the editor... it also produces unpredictable output files (part of the code may be missing), after working in GUI/Editor for a while. I have used it only a few times... but more or less I learnt how to use it. I have rewritten PP's ACSI2CF GAL listing to CUPL. For such small GALs I was working with, the output JED file is human readable, so I could easily see, that "something went wrong" during compilation. Also - the project filename should be the same as the Name declaration in the PLD source file.

[exxos]

There is screwyness with the location of the code in the editor as well. That threw me for a bit until Atmel debugged it. I will try a re-compile later from freshly loading cupl and see if it helps.

[exxos]

I tried opening CUPL and compiling without making any changes and compiled, I checked the jed files and the only thing which seems to have changed is the time and date which seems to be in the file. I programmed the firmware just to make sure, and it is still malfunctioning.

So will just have to wait until Atmel reply about the issue


EDIT:

I think I figured out the problem... #bobslaw

[exxos]

Decided to give the byte swapping a try....

IMG_4503.JPG (54.51 KiB) Viewed 3788 times

I guess it worked



EDIT:

so partitioning on the ST resulted in it saying it could not write to root sector But placing the card in the PC did recognise a 100MB partition which I just created on the ST... Now card is back in the ST and it recognises the card which I formatted on the PC... But currently cannot access it

IMG_4504.JPG (78.91 KiB) Viewed 3784 times

I tried partitioning as Windows only, but did not seem to help so there must be a little bit more to byte swapping than I originally thought


EDIT2:

*scratches head*

I put TOS & windows back again and do recognise the C drive this time... But it still complained about not being able to access the root sector...

IMG_4505.JPG (96.66 KiB) Viewed 3776 times

EDIT3:

I put the card back in the PC, and copied a file to it.... Put the card back in the ST , I get the C drive will bought I do not get the file

So I created a folder on the ST, and I do not see it on the PC... my brain hurts...

[exxos]

So on my PC I have this folder...

pc1.JPG (15.55 KiB) Viewed 3763 times

pc2.jpg (14.9 KiB) Viewed 3763 times

And on the ST I have this..

st.jpg (52.98 KiB) Viewed 3763 times

So the card works on ST and PC, but it seems to be using somehow different partition or something

[PhilC]

And I know how you enjoy a puzzle. Looks like the card is possessed

[exxos]

And I know how you enjoy a puzzle. Looks like the card is possessed

It must be using the "B-side" of the CF card.. that's my theory

[exxos]

So the windoze partition is at the start of the drive which disk manager states....

But the file name "11111111" which is on the ST only seems to appear in the un-partitioned space..

666.jpg (59.66 KiB) Viewed 3744 times