Hello,I have an interesting situation. When I start my app on the F303RE Nucleo I initialize all the peripherals. When CAN is initialized it returns a HAL_TIMEOUT error. If I call the same initialization code a second time it initialized correctly...
Hello. I have a project that runs fine on F303RE Nucleo board. I loaded it on the F303ZE Nucleo board and I get no banner displayed on the Virtual Comm port. The device manager sees the port fine. Are there any solder bridges or jumpers needed...
Hello,I have a project working on the F303-re Nucleo board. I want to run it now on the F303-ze Nucleo board. Apparently virtual com port doesn't work the same on the ZE as it does on the RE. I can take a new RE board, copy the binary file to th...
Hello Imen,I'm not sure what you mean by mode. Yes, I have a transceiver (max13053a). As I said the CAN bus is working fine after the SECOND initialization. I don't think LOOPBACK will help me since, I assume, that LOOPBACK won't work if initial...
I guess the basic question is should code that runs on the f303re run on the f303ze? Can I load the same binary on both boards and expect the same operation? If the answer is yes, I've got a bad ZE board. If the answer is no, I need to track dow...
Yes Imen, It does show up as a serial interface (Comm 5). And the file exloper shows the device as Nod-f303ze. That looks the same as a F722ze board that I have where the virtual comm port works correctly (comm 7 and a different device name in fil...
