Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17268 Discussions

1-Port ROM only outputting one byte

Altera_Forum
Honored Contributor II
1,236 Views

Hello all, 

 

I used the Mega-Wizard in Quartus to instantiate a single clocked 1-Port ROM block, 64-bit wide, 256 words deep. 

It's for a Cyclone II FPGA. 

I created a Memory Initialization File to give it starting values. 

Here's the beginning of it below: 

 

 

DEPTH = 256; -- The size of memory in words 

WIDTH = 64; -- The size of data in bits 

ADDRESS_RADIX = HEX; -- The radix for address values 

DATA_RADIX = HEX; -- The radix for data values 

CONTENT -- start of (address : data pairs) 

BEGIN 

0 : 14 21 A1 4B 68 00 CA 9F; 

1 : 19 D8 83 23 2B 90 28 4E; 

 

 

I place the 64-bit output into a register, and send it out serially to another device, MSB first. 

But when I check the serial stream, I see 00s except for the least significant byte. 

So for Address 0 I see 0000000000000014 stream out, and for Address 1 I see 0000000000000019. 

 

I don't see any warnings or errors associated with the memory after compilation. 

 

 

Has anyone seen something like this before?
0 Kudos
3 Replies
Altera_Forum
Honored Contributor II
568 Views

How do you know its the rom and not the logic that drives the serial interface?

0 Kudos
Altera_Forum
Honored Contributor II
568 Views

Hi Awann, 

 

this happens if you uses spaces between the bytes. try to write all hex without spaces.
0 Kudos
Altera_Forum
Honored Contributor II
568 Views

 

--- Quote Start ---  

Hi Awann, 

 

this happens if you uses spaces between the bytes. try to write all hex without spaces. 

--- Quote End ---  

 

 

 

Thanks Duesterberg! Problem solved. 

 

I swear I had seen a .mif example with spaces in between the bytes, but obviously I was incorrect.
0 Kudos
Reply