Other Parts Discussed in Thread: TMDSDOCK28379D, C2000WARE
Hi,
just moved to 28379D from 28335 and have several questions...I am trying to achieve similar functionalities in F28379D as I had in F28335.
- What is the function of the connector J8 on TMDSCNCD28379D? Instead of J8, I use TMDSDOCK28379D +5V power supply and I can load the code, regardless of the position of the jumpers J2-J7. J2 and J3 are for GPIO-42 and 43 coming from the docking station, but in my case jumper position does not make any difference. Is J8 used for something else apart for ControlCARD power supply?
- For A:J1 equivalent 180 connector pins 76 and 78 (GPIO-28 and GPIO-29, respectively). Is there something similar to jumpers J2-J7 to select between serial connection coming from the docking station or the ControlCARD?
- How to enable stand-alone execution? When loading the code (from MATLAB) I connect A:J1 and set A:SW1 to Position 1: ON (up) and SW1 Position 1: OFF (up), Position 2: ON (down). In MATLBA Simulink I tick Boot from Flash option. Turning off and on the power supply does not boot from Flash. If I set A:SW1 to Position 1: OFF (down) as in Table 1, I am not able to load the code at all and get following MATLAB error. Turning OFF the switch A:SW1 before powering on the board does not boot from Flash either. In F28335, it was only necessary to tick MATLAB Simulink Boot from Flash option and code would resume after a power cycle!
- I am not sure I understand the two CPU concept and how it should work. Are there any references to start with?
- Does each CPU have 1024KB of flash memory?
- What if each CPU tries to access the same GPIO?
- Are there any limitations for each CPU?
- In MATLAB I can select which CPU to load in... Am I able to exchange signals between CPUs, for example, run control on one CPU and protection (faster task) on another CPU where ADC signals are shared between CPUs and protection healthy enables the control?
*** Starting debug session... SEVERE: IcePick_C_0: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.2.1.00046) SEVERE: emulation failure occurred SEVERE: Error connecting to the target: emulation failure occurred *** Cannot create a valid debug session for Board/CPU=*/C28xx_CPU1. Make sure this matches only one board and one CPU. Exiting...