FPGA Central - World's 1st FPGA / CPLD Portal

FPGA Central

World's 1st FPGA Portal

 

Go Back   FPGA Groups > NewsGroup > FPGA

FPGA comp.arch.fpga newsgroup (usenet)

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 11-15-2007, 05:01 PM
Matthew Hicks
Guest
 
Posts: n/a
Default EDK 9.1 Issues

When working with custom peripherals in EDK, is there a better way to make
sure changes to the hardware design take effect than trying to re-import
the peripheral? I spent several hours last night debugging a design that
was failing because EDK wasn't loading the updated hardware design (just
logic, no change in external ports). I made sure it did a fresh synth+impl
run every time, but somehow the functionality never changed even though the
hw design did. Even after removing the instance and re-importing and re-connecting
it. I finally got it to work by creating a completely new hw design (in
name only) with the same logical functionality and using it in place of the
previous block.


---Matthew Hicks


Reply With Quote
  #2 (permalink)  
Old 11-15-2007, 05:10 PM
Philip Potter
Guest
 
Posts: n/a
Default Re: EDK 9.1 Issues

Matthew Hicks wrote:
> When working with custom peripherals in EDK, is there a better way to
> make sure changes to the hardware design take effect than trying to
> re-import the peripheral? I spent several hours last night debugging a
> design that was failing because EDK wasn't loading the updated hardware
> design (just logic, no change in external ports). I made sure it did a
> fresh synth+impl run every time, but somehow the functionality never
> changed even though the hw design did. Even after removing the instance
> and re-importing and re-connecting it. I finally got it to work by
> creating a completely new hw design (in name only) with the same logical
> functionality and using it in place of the previous block.


I think Project->Rescan User Repositories will solve your problem.

--
Philip Potter pgp <at> doc.ic.ac.uk
Reply With Quote
  #3 (permalink)  
Old 11-15-2007, 06:41 PM
Matthew Hicks
Guest
 
Posts: n/a
Default Re: EDK 9.1 Issues

Thanks for trying to help, but it didn't work. I updated a simple piece
of hardware to use a different bit to drive an LED (1/2 as fast blinking),
saved, hit the refresh repositories button, after implementation... same
old results.


---Matthew Hicks


> Matthew Hicks wrote:
>
>> When working with custom peripherals in EDK, is there a better way to
>> make sure changes to the hardware design take effect than trying to
>> re-import the peripheral? I spent several hours last night debugging
>> a design that was failing because EDK wasn't loading the updated
>> hardware design (just logic, no change in external ports). I made
>> sure it did a fresh synth+impl run every time, but somehow the
>> functionality never changed even though the hw design did. Even
>> after removing the instance and re-importing and re-connecting it. I
>> finally got it to work by creating a completely new hw design (in
>> name only) with the same logical functionality and using it in place
>> of the previous block.
>>

> I think Project->Rescan User Repositories will solve your problem.
>



Reply With Quote
  #4 (permalink)  
Old 11-15-2007, 08:02 PM
Daniel Koethe
Guest
 
Posts: n/a
Default Re: EDK 9.1 Issues

Matthew Hicks schrieb:
> When working with custom peripherals in EDK, is there a better way to
> make sure changes to the hardware design take effect than trying to
> re-import the peripheral? I spent several hours last night debugging a
> design that was failing because EDK wasn't loading the updated hardware
> design (just logic, no change in external ports). I made sure it did a
> fresh synth+impl run every time, but somehow the functionality never
> changed even though the hw design did. Even after removing the instance
> and re-importing and re-connecting it. I finally got it to work by
> creating a completely new hw design (in name only) with the same logical
> functionality and using it in place of the previous block.
>
>
> ---Matthew Hicks
>
>

hello Matthew,
you can for development of IP-Cores set in the .mpd file the OPTION
CORE_STATE to "DEVELOPMENT".

OPTION CORE_STATE = DEVELOPMENT

See also in the EDK doc directory the Manual Platform Specification
Format Reference Manual (psf_rm.pdf) Page 42 (EDK 8.2 Version).


The core will every time synthesized if you change any bit.

Best regards,
Daniel



Reply With Quote
  #5 (permalink)  
Old 11-15-2007, 08:12 PM
Duane Clark
Guest
 
Posts: n/a
Default Re: EDK 9.1 Issues

Matthew Hicks wrote:
> When working with custom peripherals in EDK, is there a better way to make
> sure changes to the hardware design take effect than trying to re-import
> the peripheral? I spent several hours last night debugging a design that
> was failing because EDK wasn't loading the updated hardware design (just
> logic, no change in external ports). I made sure it did a fresh synth+impl
> run every time, but somehow the functionality never changed even though the
> hw design did. Even after removing the instance and re-importing and re-connecting
> it. I finally got it to work by creating a completely new hw design (in
> name only) with the same logical functionality and using it in place of the
> previous block.


Remove the corresponding generated .ngc files, including the ones in the
cache directory:
rm implementation/my_wrapper.ngc
rm implementation/cache/my_wrapper.ngc
(rm is a Linux command, in case you are on Windows)
When you rerun the synthesis, it will rebuild the files from the new code.
Reply With Quote
  #6 (permalink)  
Old 11-15-2007, 08:52 PM
Matthew Hicks
Guest
 
Posts: n/a
Default Re: EDK 9.1 Issues

Following your advice, I edited the .mpd file for the core to include the
"CORE_STATE" option. After going back into EDK and refreshing repositories,
the .mpd change was reflected in EDK. After going through the complete implementation
process, everything works as it should. Thanks for this tip (I wish it would
be default behavior, or more evident that this option exists during import),
you saved me many more hours of uneeded hassel. Also, thanks for the reference
where I can read-up more on other options.


---Matthew Hicks


> Matthew Hicks schrieb:
>
>> When working with custom peripherals in EDK, is there a better way to
>> make sure changes to the hardware design take effect than trying to
>> re-import the peripheral? I spent several hours last night debugging
>> a design that was failing because EDK wasn't loading the updated
>> hardware design (just logic, no change in external ports). I made
>> sure it did a fresh synth+impl run every time, but somehow the
>> functionality never changed even though the hw design did. Even
>> after removing the instance and re-importing and re-connecting it. I
>> finally got it to work by creating a completely new hw design (in
>> name only) with the same logical functionality and using it in place
>> of the previous block.
>>
>> ---Matthew Hicks
>>

> hello Matthew,
> you can for development of IP-Cores set in the .mpd file the OPTION
> CORE_STATE to "DEVELOPMENT".
> OPTION CORE_STATE = DEVELOPMENT
>
> See also in the EDK doc directory the Manual Platform Specification
> Format Reference Manual (psf_rm.pdf) Page 42 (EDK 8.2 Version).
>
> The core will every time synthesized if you change any bit.
>
> Best regards,
> Daniel



Reply With Quote
  #7 (permalink)  
Old 11-15-2007, 09:05 PM
Matthew Hicks
Guest
 
Posts: n/a
Default Re: EDK 9.1 Issues

Thanks, this also works.


---Matthew Hicks


> Matthew Hicks wrote:
>
>> When working with custom peripherals in EDK, is there a better way to
>> make sure changes to the hardware design take effect than trying to
>> re-import the peripheral? I spent several hours last night debugging
>> a design that was failing because EDK wasn't loading the updated
>> hardware design (just logic, no change in external ports). I made
>> sure it did a fresh synth+impl run every time, but somehow the
>> functionality never changed even though the hw design did. Even
>> after removing the instance and re-importing and re-connecting it. I
>> finally got it to work by creating a completely new hw design (in
>> name only) with the same logical functionality and using it in place
>> of the previous block.
>>

> Remove the corresponding generated .ngc files, including the ones in
> the
> cache directory:
> rm implementation/my_wrapper.ngc
> rm implementation/cache/my_wrapper.ngc
> (rm is a Linux command, in case you are on Windows)
> When you rerun the synthesis, it will rebuild the files from the new
> code.
>



Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
OCM BRAM and PCC issues... xenix FPGA 0 08-24-2007 09:59 AM
Max Plus II and Synthesis issues MikeD FPGA 0 09-27-2006 05:29 PM
MPMC2 : npi issues #2 ivo FPGA 1 09-18-2006 08:08 PM
MPMC2 : npi issues ivo FPGA 2 08-31-2006 11:19 PM
DMA issues with IPIF on V2P el_boricua FPGA 0 08-25-2005 09:38 PM


All times are GMT +1. The time now is 08:00 AM.


Powered by vBulletin® Version 3.8.0
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Copyright 2008 @ FPGA Central. All rights reserved