Hello Andreas
yes it is slightly different, but main parts are same.
You need two debug configurations: one for CA5 and one for CM4:
Click at button DTSL and check Start secondary core .....
Then you should connect to both cores separately.
/Jiri
Finally I could make it work, but only after commenting out the printf() calls in the funtions main() and hello_M4() in M4 project. (see code snippet at bottom)
Otherwise the while(1) statement is never reached.
I have no idea what could be the reason for this behaviour.
Unfortunately I can even not check the terminal output of printf(). I tried to use the terminal of DS-5 with following settings, but get no output, neither from M4 nor A5
(even though changing the UART_PORT to UART2 according to Rev G Tower Board Changes)
// dual_core_m4.c
...
int main()
{
/* Enable IO for LED operation */
ENABLE_LEDS;
// printf("Hello World from M4 Core!\n"); // NEEDS TO BE COMMENTED OUT
while(1)
{
/* Blink Tower LEDs */
led_blink_tower(1);
/* Say Hello */
hello_M4();
}
return 0;
}
...
void hello_M4()
{
/* Lock gate to write UART, then unlock */
SEMA4->GATE[1] = CORE1_LOCK;
if(SEMA4->GATE[1] == CORE1_LOCK)
{
/* Output message from M4 */
// printf("Hello M4!\n"); // NEEDS TO BE COMMENTED OUT
/* Unlock Semaphore */
SEMA4->GATE[1] = UNLOCK;
}
}
Hi Andreas,
please check which serial channel is available on your machine i device manager:
then use puTTy, TerraTerm, Hercules or any other application and set communication parameters to 115200 b/s, no parity, 1 stop bit and no flow control.
Not sure what happens in your code, but maybe you can start new DS5 worspace and import project from Vybrid sample code (from Vybrid web pages) and then you can go back to your code.
/Jiri
