Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
12600 Discussions

cyclone III: after update dead

Altera_Forum
Honored Contributor II
1,065 Views

Hello 

 

I'm triying to configure my device over ethernet (tftp) like described in AN-429. On a cyclone II (EP2C20F) the code is working well. I now try to do the same on a cyclone III (EP3C25). I don't use the "remote_update IP" neither reconfig-pin. 

The update seems to run fine because on the consol I can see the same messages like on page 14 from the AppNote. After a power off and on the system does not start anymore. To get the system running again I have to flash via JTAG. 

Any idea? Is there a way to read the epcs flash in the case, when the system does not start anymore. 

 

Thanks for any help 

Regards 

brunjak
0 Kudos
4 Replies
Altera_Forum
Honored Contributor II
352 Views

 

--- Quote Start ---  

After a power off and on the system does not start anymore. To get the system running again I have to flash via JTAG. 

Any idea?  

--- Quote End ---  

 

Did you test if the fpga completes configuration? Maybe fpga configures correctly but then it can't bootload the Nios processor. 

This would be a common problem and is usually related to a wrong bootloader file or misplacement of Nios code in epcs image. 

 

 

--- Quote Start ---  

Is there a way to read the epcs flash in the case, when the system does not start anymore. 

 

--- Quote End ---  

 

Configure with jtag (without flashing it) any design capable of reading epcs. 

Then you can download data and compare with your remote update image.
0 Kudos
Altera_Forum
Honored Contributor II
352 Views

Thank you for the fast response. 

 

 

--- Quote Start ---  

Did you test if the fpga completes configuration? Maybe fpga configures correctly but then it can't bootload the Nios processor. 

This would be a common problem and is usually related to a wrong bootloader file or misplacement of Nios code in epcs image. 

 

Configure with jtag (without flashing it) any design capable of reading epcs. 

Then you can download data and compare with your remote update image. 

--- Quote End ---  

 

 

I have measured CONF_DONE Pin and nSTATUS. In real it seems that the fpga completes configuration but after that can't bootload the nios. I now will check if my remote update images matches with the loaded onw. 

 

Thank you 

brunjak
0 Kudos
Altera_Forum
Honored Contributor II
352 Views

I suggest you implement in the fpga configuration a simple monitor signal (e.g. a blinking led or a switching signal connected to a counter) on a spare fpga output. 

If the signal starts just after CONF_DONE is active, then you are sure the fpga correctly configures with the updated image, thus the problem is only with Nios boot. 

In the latter case, I don't think you have a mismatch in the image. From my experience is more probable your build the updated image with a bad bootloader. 

Do you overwrite the factory programmed image or do you save the image at different epcs addresses? In the first case you can use the standard bootloader while if Nios code is not just after fpga configuration data, you need a special bootloader.
0 Kudos
Altera_Forum
Honored Contributor II
352 Views

I could find the error :-). 

 

The bad news. I was the error. I was not able to crate a correct batch-file which generates my .srec file. My batch-file took a wrong .flash file. 

 

Thank you for your help 

 

brunjak
0 Kudos
Reply