On 7/26/2019 5:08 PM, justin White wrote: > >> >> Ok well I cannot cope with the stress of starting up my workstation this >> week and I didn't catch any quartus log in your former post? >> MiB >> > > Lol, rough week eh? > > Post directly after has the quartus snippet with the error, re-ran it,full > terminal print attached. Again, only happens if in pinfile: > > (SSerialTag, x"00", ClockMedTag, x"01", SSerialCommandAddr&PadT, > SSerialNumRegs, x"10", SSerialMPBitMask), > > if: > > (SSerialTag, x"00", ClockLowTag, x"01", SSerialCommandAddr&PadT, > SSerialNumRegs, x"10", SSerialMPBitMask), > > it will build fine, but SS does not work.
The problem is it doesn't look like ClockMedTag is declared in the IDROMConst.vhd file, just ClockLowTag and ClockHighTag: https://github.com/machinekit/mksocfpga/blob/master/HW/hm2/config/IDROMConst.vhd#L402-L404 ...causing the Quartus error: Error (10482): VHDL error at PIN_st_fpga_soc_dc1f.vhd(80): object "ClockMedTag" is used but not declared File: /work/HW/hm2/config/DExx_Nano_xxx_Cramps/PIN_st_fpga_soc_dc1f.vhd Line: 80 The configs I have that use SSerial are using ClockLowTag and IIRC they worked OK. You might check and see if Peter has updated the IDROMConst.vhd file, the one in the Machinekit repo might be fairly dated. But I think it ought to work when using ClockLowTag, so there may be some other weirdness going on. -- Charles Steinkuehler char...@steinkuehler.net -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/160aeed4-bc30-0351-57c0-a033f55d2d5a%40steinkuehler.net.
