Multiple Functional Issues with PIC16F18444 in Flowcode 10

[medelec35]

After adding the fcdx file, you will need to reload your fcfx project file then recompile.
If it does not work after reloading, can you please attach .c and .hex files.

[medelec35]

I'm also looking into the EEPROM issue

[CamargoF]

I'm also looking into the EEPROM issue

Can you please try to fix the UART before EEPROM?

It will allow me to print debug information that is very important at this moment.

Best regards,

Fernando

[medelec35]

The simulator is showing the UART as working
Is your hardware running at the correct speed?
What are you using to capture UART, a USB to UART bridge or logic analyser?
If applicable, make sure your wires transmitting UART are not too long.
Can you check with a scope or logic analyser by toggling a pin at 50ms for example.
Or if not got either, with LED connected to a pin just toggle the pin every couple of seconds, and check the result with a stopwatch

I have attached an alternative UART to see if that works for you.

[medelec35]

I can now confirm that both Read and write of EEPROM has been fixed.
I will let you know when the update is available on the component database.

[CamargoF]

The simulator is showing the UART as working
Is your hardware running at the correct speed?
What are you using to capture UART, a USB to UART bridge or logic analyser?
If applicable, make sure your wires transmitting UART are not too long.
Can you check with a scope or logic analyser by toggling a pin at 50ms for example.
Or if not got either, with LED connected to a pin just toggle the pin every couple of seconds, and check the result with a stopwatch

I have attached an alternative UART to see if that works for you.

I must admit I haven't fully understood how the UartSoftwareTimer works yet, but I will continue investigating it.

Regarding my use of the UART: it worked correctly with the PIC16F18345 — transmitting data directly and receiving data via interrupt. However, after switching to the PIC16F18444, UART send data functions stopped working.

As previously mentioned, the UART interrupt issue was resolved by correcting the register address, which indicates that incorrect register mappings may be the root cause.

It's important to note that all peripherals I reported as problematic — interrupts, ADC, EEPROM, and UART — function correctly in simulation but fail on actual hardware when using the PIC16F18444.

Given this pattern, I kindly request that the UART component be reviewed and corrected with this in mind, particularly regarding interrupt handling and register mappings for this device.

Thank you once again for your attention and support.

Best regards,

Fernando

[CamargoF]

After adding the fcdx file, you will need to reload your fcfx project file then recompile.
If it does not work after reloading, can you please attach .c and .hex files.

Unfortunately, the official ADC fix seems to have introduced a new issue. After accepting the update, the ADC stopped reading altogether.

Here are the 16F18444.fcdx file versions I have:

• The version you sent directly: this one worked for ADC

Code: Select all

<!-- CRC: 90CF26913586BBA787FE92D553771933B2BECC5EA2D3003609AE2EE90C7D3CBADA6183FD7E79AA9B6577EF8789F001E82199345CB81F199F08EB499B5700206FABB24D739BCDFCC30C3CAEE8E7DA6987B678648A35DED1DC394CD0A8E7E870F3C12376B2536502A10294774877944992C19BD19A7F72FE12A2C59BAF674D3D127DBB39C6A70F77ACD8B937FECF905438E3F5FA80E7010969233FBE92E49B97AEDB3084B52383ABAA086944AE325796A6E12CF4674B1156F72604535FBCEB74C043A1300EB085C421EC447A7A7C3AA69E9E27863BF8B478B1 -->
<!-- REVISION: 3.0 -->
<!-- GUID: 6FD9FD89-EF7E-4004-BE11-99FA58D170EC -->
<!-- DATE: 06\05\2025 -->
<!-- DIR: FCD\PIC\16F18444.fcdx -->
    ::::::::::::
    <adc type='36' bits='12' >
    ::::::::::::

• The version received through the Library Updates system: this one broke ADC functionality.

Code: Select all

<!-- CRC: 90CF26913586BBA787FE92D553771933B2BECC5EA2D3003609AE2EE90C7D3CBADA6183FD7E79AA9B6577EF8789F001E82199345CB81F199F08EB499B5700206FABB24D739BCDFCC30C3CAEE8E7DA6987B678648A35DED1DC394CD0A8E7E870F3C12376B2536502A10294774877944992C19BD19A7F72FE12A2C59BAF674D3D127DBB39C6A70F77ACD8B937FECF905438E3F5FA80E7010969233FBE92E49B97AEDB3084B52383ABAA086944AE325796A6E12CF4674B1156F72604535FBCEB74C043A1300EB085C421EC447A7A7C3AA69E9E27863BF8B478B1 -->
<!-- REVISION: 3.0 -->
<!-- GUID: 6FD9FD89-EF7E-4004-BE11-99FA58D170EC -->
<!-- DATE: 06\05\2025 -->
<!-- DIR: FCD\PIC\16F18444.fcdx -->
    ::::::::::::
    <adc type='33' bits='12' >
    ::::::::::::

So... it looks like the fix needs a fix.

Also, I’m still waiting for the correction to the internal EEPROM functionality, which continues to fail on real hardware despite working in simulation.

Thanks again for your continued support, and please let me know when the updated files are available.

Best regards,

Fernando

[medelec35]

hello. I did state in the post that had the fcdx attachment

If you run any component updates, then the fcdx you added will be overwritten.

That is exactly what happed.
I edited version 3 and added it to my post.
By updating component library before the fcdx has been added to the component data base, you have reverted back to the version which does not work!
That is why you see two revision 3 files!
If you want ADC to work again you need to used the version that is added to this post.
The new version when available will be revision 4.
There is no point in adding the updated fcdx to the database until all issues are sorted.
I will let you know when that happens.
Sorry, it looks like your posts should no longer be approved, so hopefully I have sorted that as for you as well.

[CamargoF]

I can now confirm that both Read and write of EEPROM has been fixed.
I will let you know when the update is available on the component database.

Since (as you mentioned) the PIC16F18444 is not currently available on your end for hardware testing, would it be possible for you to send me the updated fix so I can validate it directly here?

I'm happy to assist by running real hardware tests and providing feedback to help confirm whether the issue is resolved.

Please let me know if you can send the latest patch for testing.

[medelec35]

Browse to this location using file explorer, it's hidden by default so just paste the link into your address bar.

Code: Select all

%ProgramData%\MatrixTSL\FlowcodeV10\CAL\PIC

Place the attached C file.
you will need to reload your project file for the fix to take place.
If you run any library updates, then the PIC_CAL_EEPROM.c you added will be overwritten, so it will stop working again (unless the PIC_CAL_EEPROM.c update has been pushed).

Note. the PIC_CAL_EEPROM.c will not be pushed with the latest update for the Q series yet as there are issue outstanding with EEPROM for those devices