Initial source code release

SA0BUX
Posts: 584
Joined: Tue Jul 05, 2022 8:50 am
Location: JO99ah, Stockholm, Sweden
Contact:

Re: Initial source code release

Post by SA0BUX » Wed Aug 09, 2023 9:57 am

Got same errors after upgrade to 1.13.1 , was on 1.12.1 before, stupid me didn't tried a clean build before upgrade.

I'm a happy amateur with this build software so I hope that you find the cause.

VK3KYY
Posts: 7590
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Initial source code release

Post by VK3KYY » Wed Aug 09, 2023 10:01 am

SA0BUX wrote:
Wed Aug 09, 2023 9:57 am
Got same errors after upgrade to 1.13.1 , was on 1.12.1 before, stupid me didn't tried a clean build before upgrade.

I'm a happy amateur with this build software so I hope that you find the cause.
I was going to suggest that they do a clean build, but this didn't seem necessary if it was their first build

I always do a clean build after making any significant change because I don't trust the IDE to build correcly otherwise

SA0BUX
Posts: 584
Joined: Tue Jul 05, 2022 8:50 am
Location: JO99ah, Stockholm, Sweden
Contact:

Re: Initial source code release

Post by SA0BUX » Wed Aug 09, 2023 10:16 am

I wonder what mess I create now :)
I deleted the project and tried to make a project from existing IOC file and IDE wanted to have my ST.com login and started to download some large files.
Don't remember how I did it the first time when I compiled.
Capture.PNG
Capture.PNG (154.51 KiB) Viewed 2006 times

VK3KYY
Posts: 7590
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Initial source code release

Post by VK3KYY » Wed Aug 09, 2023 10:31 am

Do not use the .ioc file , we no longer use it becuase TYT now use a clone STM32 MCU which is not compatible with the limitations of the clone chip

Definietly do not regenerate code from the IOC.

Just import the project from file system

G4EML
Posts: 930
Joined: Sat Nov 16, 2019 10:01 am

Re: Initial source code release

Post by G4EML » Wed Aug 09, 2023 10:32 am

It looks like it is a know and reported issue.
https://community.st.com/t5/embedded-so ... d-p/578622

The work around is to replace all occurrences of caddr_t with void* in system.c

Colin.

VK3KYY
Posts: 7590
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Initial source code release

Post by VK3KYY » Wed Aug 09, 2023 10:44 am

G4EML wrote:
Wed Aug 09, 2023 10:32 am
It looks like it is a know and reported issue.
https://community.st.com/t5/embedded-so ... d-p/578622

The work around is to replace all occurrences of caddr_t with void* in system.c

Colin.
You could add this to one of the headers

Code: Select all

#ifndef __daddr_t_defined
typedef	long	daddr_t;
#define __daddr_t_defined
#endif
#ifndef __caddr_t_defined
typedef	char *	caddr_t;
#define __caddr_t_defined
#endif
Strange that even though I did a full install of the lates CUBE and also checked for the version of the F4 plugins etc that it didnt update the folder tree
with types.h in it

SA0BUX
Posts: 584
Joined: Tue Jul 05, 2022 8:50 am
Location: JO99ah, Stockholm, Sweden
Contact:

Re: Initial source code release

Post by SA0BUX » Wed Aug 09, 2023 11:17 am

Thanks, I also tested and added "#include <sys/types.h>" to sysmem.c and at least it made a bin file.

VK3KYY
Posts: 7590
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Initial source code release

Post by VK3KYY » Wed Aug 09, 2023 11:45 am

SA0BUX wrote:
Wed Aug 09, 2023 11:17 am
Thanks, I also tested and added "#include <sys/types.h>" to sysmem.c and at least it made a bin file.
OK.

Seems like a big mistake from STM

BTW. I also found another big mistake from STM with the DFU drivers. They have a completely new set of DFU drivers which are only compatible with their new STM32CubeProgrammer application.
I installed this new programming tool and I was no longer able to upload to any radio.

Considering there must be many programs that upload using STM DFU devices, it seems crazy to replace the drivers with incompatible versions to support their new programming application.

Luckily I was able to uninstall their new drivers and delete them, and Windows reverted to the older driver.
However for a while I thought I may need to reinstall Windows to remove the new drivers

User avatar
F1RMB
Posts: 2626
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France

Re: Initial source code release

Post by F1RMB » Wed Aug 09, 2023 5:47 pm

I just upgraded to 1.13.1 on my Linux machine, and I get the caddr_t unknown type error.

VK3KYY
Posts: 7590
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Initial source code release

Post by VK3KYY » Wed Aug 09, 2023 8:49 pm

F1RMB wrote:
Wed Aug 09, 2023 5:47 pm
I just upgraded to 1.13.1 on my Linux machine, and I get the caddr_t unknown type error.
Strange

My PC failed to update, so downloaded the latest version and installed and it was still ok

Post Reply