Search found 74 matches
- Sun Jun 20, 2021 4:45 pm
- Forum: General Programming
- Topic: RC5 component not working
- Replies: 17
- Views: 23427
Re: RC5 component not working
Hey Guys, Let me hook up with this RC5 issue. I'm also working on implementing the RC5 receiver in a project. I started with the projects MCU (PIC24) on a high clock frequency. Got no results. This was in FC9. So I took out my e-Block kit with a simple MCU, PIC16F877A. At first test (FC9) no results...
- Mon Apr 12, 2021 9:09 pm
- Forum: Bug Reports
- Topic: PIC32MX with 24C32 EEProm
- Replies: 2
- Views: 4039
Re: PIC32MX with 24C32 EEProm
Hi Stefan, Sorry for the delay, lot to do.. I build the I2C read and write routine with the peripheral I2C macro from the Creation menu. This works great without any problems. Unfortunate only in software mode. Hardware ch1 and 2 do not work.. Now I switched to FC9 and recompiled my project. In this...
- Tue Dec 15, 2020 10:53 pm
- Forum: Bug Reports
- Topic: PIC32MX with 24C32 EEProm
- Replies: 2
- Views: 4039
PIC32MX with 24C32 EEProm
Hey Guys, My project with PIC32MX550 uses the 24C32 EEprom macro. My hardware uses the 24AA32 EEProm. Only in software mode the first address value can be written and read, sequencing values none. In hardware mode no data is read or written. Did several delay test to check but no results... Update?
- Thu Aug 20, 2020 8:14 pm
- Forum: Flowcode V8
- Topic: OLED with SPD0301 driver
- Replies: 17
- Views: 7877
Re: OLED with SPD0301 driver
Hi Ben,
Great, thanks.
Patrick
Great, thanks.
Patrick
- Sat Aug 15, 2020 12:21 pm
- Forum: Flowcode V8
- Topic: OLED with SPD0301 driver
- Replies: 17
- Views: 7877
OLED with SPD0301 driver
Hi All I have purchased some bigger 1,54" I2C OLED displays from Heltec (heltec.cn). This display uses a SPD0301 driver. In the Flowcode I2C Oled macro's dispays are used with SSD1306 and SH1106 drivers. I use these also... and these are working great. The SPD0301 controler is not supported yet. Any...
- Sat Jul 25, 2020 4:53 pm
- Forum: Flowcode V8
- Topic: WS2812B compilation problems.
- Replies: 25
- Views: 10673
Re: WS2812B compilation problems.
Hi Martin/Ben, I have been working at Martin's refresh code and tuned it to a working code for the PIC MCU. PIC WS2812B Test.fcfx Using an output as MOSI function gives to much delay in the loop. Changed it in C-code and did some measurements. Changed the amount of nops in Martin's Refresh macro and...
- Wed Jul 22, 2020 10:16 pm
- Forum: Flowcode V8
- Topic: WS2812B compilation problems.
- Replies: 25
- Views: 10673
Re: WS2812B compilation problems.
Hi Martin/Ben, Looking at Martin's solution in hard coding i started to check Martin's code on a PIC16F18877. Checking the timing on my scope I discovered that even with one NOP the timing delay is still 780ns with it's internal clock of 32MHz. Increasing the NOPS counts shows that it gets stable at...
- Mon Jul 20, 2020 10:17 pm
- Forum: Flowcode V8
- Topic: WS2812B compilation problems.
- Replies: 25
- Views: 10673
Re: WS2812B compilation problems.
Hi Martin, I checked the LightBoard example and this works great on the Arduino Uno baord. I also managed to let it work on a ATMega16 with 16MHz xtal. It does not work with a 8MHz xtal... Testing with a PIC16F18877 is still not working. I tested with 8 and 16MHz xtals. When starting up all leds lig...
- Sun Jul 19, 2020 7:42 pm
- Forum: Flowcode V8
- Topic: WS2812B compilation problems.
- Replies: 25
- Views: 10673
Re: WS2812B compilation problems.
Hi Ben, I also tested the macro on a AVR ATMega16 MCU, clock external 8MHz. Checking the Initialize macro: It gives in total 24 pulses. I assume all bits are set to zero. Analizing it on a scope the T0H and T0L are 480ns and 2.28ms. T0L is far out of range according to the datasheet. Selecting more ...
- Wed Jul 08, 2020 8:16 pm
- Forum: Flowcode V8
- Topic: WS2812B compilation problems.
- Replies: 25
- Views: 10673
Re: WS2812B compilation problems.
Hi Ben, I tested the macro more in a totaly clean project. If the MCU clock is not in range of the macro expected clock you get no data from the MOSI pin. If MCU clock is set right, tested in a software loop and by interupt macro, I get data from the mosi pin. I did put the initialize call in a dela...
- Mon Jul 06, 2020 9:35 pm
- Forum: Flowcode V8
- Topic: WS2812B compilation problems.
- Replies: 25
- Views: 10673
Re: WS2812B compilation problems.
Hi Ben, Yes, tested with a scope but no data. Made a test project with a different MCU. Also no Scope data and still the warning message from the compiler. Tested all LED_Controller variables. Employing 18F4550 errata work-arounds: * Corrupted fast interrupt shadow registers Test WS2812B.c: 136: #wa...
- Sat Jul 04, 2020 11:56 am
- Forum: Flowcode V8
- Topic: WS2812B compilation problems.
- Replies: 25
- Views: 10673
Re: WS2812B compilation problems.
Hey Guys, I like to hook up in this discussion with my little problem. I'm using the WS2812B on a PIC16F18857 MCU with use of the internal oscillator running on 32MHz. Using the WS1811 macro does not work in this setup. When running the compiler the first message is: (1273) Omniscient Code Generatio...
- Thu Jan 23, 2020 9:21 pm
- Forum: Bug Reports
- Topic: Bad mistake in FC8!
- Replies: 48
- Views: 40973
Re: Bad mistake in FC8!
Hi, Today i experianced a FC8 bad start again. (Win-7 Pro) I did leave my PC with running FC8 overnight without working on it. I only switched off my monitors.. After switching on my monitors a did a safety backup of my project and closed FC8, all was well. Then i had to update my Qnap Qsync and res...
- Sun Jan 19, 2020 5:09 pm
- Forum: Flowcode V8
- Topic: No internal EEProm with use of bootloader
- Replies: 8
- Views: 4213
Re: No internal EEProm with use of bootloader
Hi, I solved my issues with the epprom by using replacing the eeprom macro by two C- macro's. A read macro named NVMRead and a write macro named NVMWrite. NVMRead.fcm NVMWrite.fcm Both macro's do use the Address Hi byte (0xF0 for eeprom) as well. Advantage to this is that also the User, Revision and...
- Tue Jan 14, 2020 11:06 pm
- Forum: Flowcode V8
- Topic: No internal EEProm with use of bootloader
- Replies: 8
- Views: 4213
Re: No internal EEProm with use of bootloader
Hi Ben, For now I did a read test by adding an address read commando in C. Test.jpg This works and to my suprise all values read by the eeprom macro are read as well. To check why, i only put the "NVMADRH = 0x70" in the C-code at the beginning of the sequence and the eeprom read function does work. ...
- Mon Jan 13, 2020 11:53 am
- Forum: Flowcode V8
- Topic: No internal EEProm with use of bootloader
- Replies: 8
- Views: 4213
Re: No internal EEProm with use of bootloader
Hi Ben, I also checked the Microchip datasheets and Googled to find answers, but did not find satisfying answers. I programmed the eeprom for a few bytes with use of the MPlab IPE. Also these values are not read by the program. I made a LUT with the initial values for the eeprom. The eeprom is check...
- Sat Jan 11, 2020 2:13 pm
- Forum: Flowcode V8
- Topic: No internal EEProm with use of bootloader
- Replies: 8
- Views: 4213
Re: No internal EEProm with use of bootloader
Hi Christina, Thanks for your input. I'm aware of these data's. Hi Ben, I think this is the case. I compiled my project with compiler offset parameter "--codeoffset=0x700". Then i load my project with use of the bootloader into the project. Configuration bits are the same for bootloader and applicat...
- Wed Jan 08, 2020 9:14 pm
- Forum: Flowcode V8
- Topic: No internal EEProm with use of bootloader
- Replies: 8
- Views: 4213
No internal EEProm with use of bootloader
Hi, In my project (PIC16F18857) i use the internal eeprom for storing parameters. All is working fine. Now I added a bootloader, starting 0x00-0x6FF. I shifted the application starting from 0x700. This is working except for the internal eeprom. I did some tests but all results are "0" when readout t...
- Wed Jan 08, 2020 9:08 pm
- Forum: Flowcode V8
- Topic: Flowcode 8 crash
- Replies: 35
- Views: 16410
Re: Flowcode 8 crash
Hi, I have the same issue. As wel on Win7 as Win10. Just while working the software freeses and disapears. After restart of the pc and starting FC8 it popup and disapears the same time. Dead software A reinstall did not work.. Then deleted the FC8 in regedit and all words again. Settings gone.. Hope...
- Sat Dec 28, 2019 1:22 pm
- Forum: Flowcode V8
- Topic: XC Compiler Pro mode
- Replies: 10
- Views: 7193
Re: XC Compiler Pro mode
Hi Martin,
Yes I did change the batch file as suggested in the post link.
This is working in both cases. Old and new compiler.
If this works less well in V2.10 i can't say. I just don't have no experience in this field.
I can do some checks for you if you like..
Thanks.
PS
Yes I did change the batch file as suggested in the post link.
This is working in both cases. Old and new compiler.
If this works less well in V2.10 i can't say. I just don't have no experience in this field.
I can do some checks for you if you like..
Thanks.
PS
- Sat Dec 28, 2019 12:09 pm
- Forum: Flowcode V8
- Topic: XC Compiler Pro mode
- Replies: 10
- Views: 7193
Re: XC Compiler Pro mode
Hi Q,
I'm not into the options compilers do and don't have.
As a hardware engineer i only look at the results.
As you say, after installing the license the standard is going to a pro version. For me this does the job.
Thanks.
PS
I'm not into the options compilers do and don't have.
As a hardware engineer i only look at the results.
As you say, after installing the license the standard is going to a pro version. For me this does the job.
Thanks.
PS
- Sat Dec 28, 2019 11:35 am
- Forum: Flowcode V8
- Topic: XC Compiler Pro mode
- Replies: 10
- Views: 7193
Re: XC Compiler Pro mode
Hi Guys, Here some results from my experiences with using different XC8 compilers. At this moment i'm working on a small PIC project. At this moment it is using up to 95% of it's programm space with the standard Flowcode XC8 compiler. I also need to put in a bootloader, so i needed a compiler with m...
- Sat Oct 19, 2019 1:14 pm
- Forum: Bug Reports
- Topic: Cosmetic name of Component is Property Variable
- Replies: 0
- Views: 4709
Cosmetic name of Component is Property Variable
When editing the name of a Property in a component macro the Name in the component feet gets the property variable value and not the cosmetic name value..
- Mon May 27, 2019 8:50 pm
- Forum: Flowcode V8
- Topic: I2C problems with 16LF18857
- Replies: 4
- Views: 2947
Re: I2C problems with 16LF18857
Hi Jan, I had the simular issues with a project i use the same 16F18857 MCU. Only software channel was working. Hardware channel 1 and 2 did not. Now i have updated FC8 to V8.2.0.12 and YES hardware channels are working now. I directly tested both channels (SDA to B4, SCL to B5) and all is working w...
- Sun May 05, 2019 3:56 pm
- Forum: Bug Reports
- Topic: I2C 18F47K40
- Replies: 14
- Views: 7054
Re: I2C 18F47K40
Hi Guys,
I experiance the same problem with a PIC16F15356.
Software I2C is working but Ch1 and Ch2 are not.
FC8.1.1.11
Regards,
PS
I experiance the same problem with a PIC16F15356.
Software I2C is working but Ch1 and Ch2 are not.
FC8.1.1.11
Regards,
PS