- Отметить как новое
- Закладка
- Подписаться
- Отключить
- Подписка на RSS-канал
- Выделить
- Печать
- Сообщить о недопустимом содержимом
Hello, I recently ported my project from Standard to Pro.
Now I am getting the following message for some of my state machines-
"Can't Recognize finite state machine "statemachine.current_state" because it has a complex reset state 13246
The problem is that I use a standard structure for all my state machines, which means they are all called "statemachine" and have "current_state".
Quartus does not give any further indication as to which state machine its having problems with or which file its processing. How can I figure out which one is causing the problem?
Thanks!
Ссылка скопирована
- Отметить как новое
- Закладка
- Подписаться
- Отключить
- Подписка на RSS-канал
- Выделить
- Печать
- Сообщить о недопустимом содержимом
You have multiple state machines throughout your design hierarchy all called statemachine?
The compilation report or messages are not showing any deeper hierarchical path to point to the machine in question? It must be somewhere. Something like "|top|second_level|statemachine".
Or just put some code here to show what you are trying to do that is failing.
- Отметить как новое
- Закладка
- Подписаться
- Отключить
- Подписка на RSS-канал
- Выделить
- Печать
- Сообщить о недопустимом содержимом
Hi,
Possible to give unique name to each statemachine and see?
Thanks,
Regards,
Sheng
- Отметить как новое
- Закладка
- Подписаться
- Отключить
- Подписка на RSS-канал
- Выделить
- Печать
- Сообщить о недопустимом содержимом
Yes, all my state machines are called statemachine. There are hundreds of them throughout the design and the message give me no hierarchical information. Only a handful have this problem.
yes I could go through and change the name of each one, but that would take a while. I was hoping Quartus would have a way to point me to the file it was using.
Also, this exact code was used in Quartus Standard and only recently migrated to Pro. These errors did not occur with Quartus Standard. What is different about Pro that it now has a problem with these reset states?
Thanks
- Отметить как новое
- Закладка
- Подписаться
- Отключить
- Подписка на RSS-канал
- Выделить
- Печать
- Сообщить о недопустимом содержимом
This problem has been solved. I discovered what structure was causing problems, then I could search for that.
Thanks.

- Подписка на RSS-канал
- Отметить тему как новую
- Отметить тему как прочитанную
- Выполнить отслеживание данной Тема для текущего пользователя
- Закладка
- Подписаться
- Страница в формате печати