View Single Post
  #12   Spotlight this post!  
Unread 08-06-2016, 08:41 AM
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Problem running C samples for roboRio

The roboRIO and other NI RIO products are used for more than FRC, and that includes loading your own FPGA bit file like the original poster is attempting to accomplish. The setting in question on the web page is useful for folks who have built a startup FPGA bitfile and no longer want it to be loaded at startup. It is confusing because there is no feedback as to how the FPGA is being loaded, so this option sounds good, and works in the right situation, but it isn't the option you are looking for.

For FRC, the bit file is loaded by the comms process, so the for nonFRC experimentation, I'd probably turn off the FRCNetComm daemon, reboot, and you'll be able to load your own FPGA for offseason, non robot, safe experiments. You can turn it back on or reimage to get things ready for FRC use.

Greg McKaskle
Reply With Quote