TommyK

Digilent Staff
  • Content Count

    165
  • Joined

  • Last visited

1 Follower

About TommyK

  • Rank
    Prolific Poster
  • Birthday 02/10/1991

Profile Information

  • Gender
    Male
  • Location
    Pullman, WA

Recent Profile Visitors

3083 profile views
  1. TommyK

    Eclypse-Z7 FPGA Fan

    @zygot, I pushed the fixes an hour ago. The fixed code was tested on hardware and works. The initial commit was somewhat rushed to get you something to work with as soon as possible. I apologize for the inconvenience it may have caused.
  2. Have you tried simulating your design? You can download the MT41K128M16JT-125 verilog memory model from Micron's website under simulation models (direct link). Place the model files into your sim sources and connect the DDR pins in the top level of your test bench code to the ddr module included in the memory model files. This will make debugging much faster for you. -Tommy
  3. Hey @asmi, Thanks for notifying us on this. While the settings before worked, they weren't optimal. I've changed the mig.prj in the Genesys2 board file to your recommendations. I'm not sure why VccAuxIO was set to 1.8V, the setting is not changeable in the MIG and must default to that value. Either way it's fixed now. Thanks, Tommy
  4. TommyK

    iic setup failure

    Glad it worked!
  5. TommyK

    iic setup failure

    Its sounds to me like a memory issue as well. It looks to me like you are accessing the correct memory location. This isn't a problem with the cache. I think I've had issues with the Smart Connect IP before. Try recreating the block design without the Smart Connect IP. Try running connection automation and unchecking the object (MIG?) that wants to add a SmartConnect IP. -Tommy
  6. TommyK

    DMC60c CAN Bus

    Yes I think so. As long as the controller ACKs the messages coming from the DMC60C it will continue to send the messages.
  7. TommyK

    DMC60c CAN Bus

    DMC60C is 1MBps. No, those green and yellow wires are connected together, either CAN or PWM, not both. The DMC60C must be connected to a CAN bus controller to send out the periodic messages. Otherwise it will flash red. When it detects a CAN bus controller the LEDs will flash Yellow (by default). -Tommy
  8. Default Device ID is 0, Current limit is disabled, continuous current limit 40A, peak current limit is 60A, current duration is 500ms. There is no voltage limit? All parameters and their defaults can be found in the DMC60C CAN Protocol Guide.
  9. TommyK

    DMC60c CAN Bus

    Hi opethmc, The current and voltage information is reported by the DMC60C every 100ms (by default) in the STSANALOG (0x020614C0) frame. This info can be found on page 28-30 of the CAN protocol guide. Fault status can be found in byte 4 (fs2) in the STSGENERAL(0x02061400) frame that is sent every 10ms (by default). You can find the fault counts by reading parameters 51 through 57. This can be done by sending PARAMREQ (0x02061800) frames containing the parameter you want to read, then scanning for a PARAMRESP(0x02061840) packet. This info can be found on page 12-28. Hope t
  10. Hi Brian, Unfortunately there is no easy way to slow down the packets transmitted by the vcmdGetDescriptors command without changing the firmware. It sounds like this is more an issue with the CANable device. I don't think there is much we can do for you here. -Tommy
  11. Hi Kabron, I just tried installing both Digilent and ESP8266 board support packages and it seems like mine installed just fine. In your post on the VM forums, it sounds like they both work in Arduino, but not in Visual Micro. Is that the case? I do not think it has anything to do with the Digilent core. What happens is Arduino reads the json file from the URL you give it. It then downloads each component as .zip files into %localappdata%/Arduino15/staging/packages/ . These are then unzipped and placed in %localappdata%/Arduino15/packages/Digilent. That is all it does. I'm guessing Vi
  12. Hi Gaston, It looks like your CAN receiver doesn't have interrupts enabled. Try adding the following to the RX code, just above the readRegisters function in main() mcp25625_setRegister(MCP_CANINTE, 0x3);//Enable read buffer full interrupts mcp25625_setRegister(MCP_CANINTF, 0);//Clear interrupt flags Hope this helps! -Tommy
  13. Hi @victory460, James was correct, it is an issue in the source code for the SoftwareSerial library. The PIC32MZEFG100 does not have an SIDL bit in the CNCON register like the older chips. You can get around this by commenting out those lines in SoftwareSerial.cpp for now. I have added an ifndef line to fix this in the Digilent Core v1.0.4 which i just uploaded. Hope this helps! Tommy
  14. Check out this project on Instructables. It's doing exactly what you're talking about.
  15. Hi Philip, Thanks for pointing that out. It must have slipped past when I was transferring files over OSes. The checksum and file have been updated and should work now. If you still get the CRC error, delete the old xc32-tools found in /users/[name]/Library/Arduino15/staging/packages and try again. Thanks, Tommy