+- iomixer forums (https://iomixer.com/forums)
+-- Forum: General (https://iomixer.com/forums/forumdisplay.php?fid=1)
+--- Forum: General questions about usage (https://iomixer.com/forums/forumdisplay.php?fid=2)
+--- Thread: Cant tick Com port (/showthread.php?tid=2)
Pages:
1
2
RE: Cant tick Com port - iforce2d - 11-21-2024
Did you do "Upload and save" after the time you got the flashing red LED? If you don't overwrite the old nodes configuration, nothing will change.
To explain this a bit further, the nodes configuration is stored on the SPI flash memory (the 8 legged 'Winbond' chip near pin 36). When the firmware starts up, it reads the stored configuration file from the SPI flash and tries to run it. Many years ago, the file format was different and incompatible with the current format, so the current firmware will basically crash when reading in the old format. Holding pin 40 high will skip reading the SPI flash and start with an empty configuration. You then need to "Upload and save" to write a configuration into the SPI flash with the new format.
If the red LED doesn't flash when you're holding pin 40 high on power-up, I can only assume it wasn't contacting very well? The pin labels are not related to the MCU pin numberings btw, they are just numbers I made up for iomixer.
RE: Cant tick Com port - Kermets - 11-21-2024
Yes but the Yellow sending button just hang and never finished,
Im not able to get the flashing red led up again
but the blue is on which surely means we have 3.3v to that side on the led on power up
RE: Cant tick Com port - iforce2d - 11-21-2024
Yes good point, if the blue LED lights then your 3.3V is contacting ok. In that case, if the flashing red LED still doesn't light, it means the firmware is just not there.
Are you using the ST-Link dongle to change these firmwares, or the bootloader? In your latest screenshot you have the Firmware panel open and a firmware selected, makes me wonder if you're using that... in which case you should not be flashing the 'both' file. The 'both' file includes both bootloader and firmware, but if you're already using the bootloader to flash it then you would be flashing the bootloader into where the firmware should be, which would result in it looping around in the bootloader forever. That might explain a few things... it would also explain why you're having more success with the v0.1.0 firmware because I didn't provide a 'both' file for that.
Perhaps I should have made it a bit clearer, but:
- using ST-Link dongle ---> use the 'both' file
- using the bootloader inside the configurator ---> use the firmware only file, eg. "iomixer-0.1.3.bin"
Also keep in mind that after flashing anything you'll need to power cycle the board to have it start with the new firmware - it doesn't get automatically rebooted after flashing.