Bug #17
closedNTSC crashing on some builds
0%
Description
Investigate why... On the v1 core this occurred when running the PLL at very high fVCO. However we already fixed that in v1, so not sure why.
Updated by foft almost 7 years ago
Ijor recommended I try registering the input directly from SDRAM. I've done this and see if it helps.
He is also kindly helping me write some correct timequest rules, really appreciated:)
Updated by foft almost 7 years ago
I've still had bad builds since registering the sdram input directly.
I tried to specify an externally switchable input clock for timequest as a proxy for ntsc/pal clocks. However it doesn't make it past derive_pll_clocks, so I guess I need to define multiple pll outputs. I'm not sure of the impact here in terms of clock grouping definitions etc.
Updated by foft almost 7 years ago
Interesting when I build on AWS I get completely screwed up builds with the registered sdram input. Seemingly every time.
Updated by ndary almost 7 years ago
changed the Core to v8 and when chancing the video mode to NTSC the screen crashes
Nir
Updated by sadosp almost 7 years ago
ndary wrote:
changed the Core to v8 and when chancing the video mode to NTSC the screen crashes
Nir
I remember that this was ok in mine board. Are you use the prototype 2 area to get the firmware?
Updated by foft almost 7 years ago
- Related to Bug #34: Problem booting with Core 9 added
Updated by foft about 6 years ago
- Priority changed from High to Normal
Not seen this for months, think it was an issue around this time that has been fixed. Marking as normal priority for now.
Updated by foft about 6 years ago
- Status changed from New to Closed
On second thoughts... closing until we see it again.