Compiling Pixy 1.0.0 and 1.0.1 - IR Lock

[Michael A]

Hello, I'm trying to compile IR Lock's pixy firmware and running into trouble.

I've tried using Kiel but get over 500 build artifact errors.

I also tried LPCxpresso, it builds a hex but the hex can't be flashed on the Pixy. Pixymon outputs missing version number and memory errors.

Any help will be appreciated, thanks!

The firmware for source:

https://irlock.com/pages/archived-files

[Rich LeGrand]

Hey Michael, 

Hmm, those are some weird errors, having to do with floating-point support-- some files have one type of fp support and some files have another type of fp support.  Combing through these errors might taked time, but It looks to me like the project configuration is somehow inconsistent.  Are you using uvision 5 or 4?  I'd use 4 because I think that's what they're using.   

Have you asked the IR lock folks?  The IR lock firmware is being maintained by them. 

 

--
You received this message because you are subscribed to the Google Groups "pixy_firmware_sdk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pixy_firmware_sdk+unsubscribe@googlegroups.com.
To post to this group, send email to pixy_firmware_sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pixy_firmware_sdk/75613bc4-d944-4c0c-a7bf-60607f9f46fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Charmed Labs
www.charmedlabs.com

[Michael A]

That is what I gathered from googling the errors but there is nothing online that tells me how to adjust the floating point types - at this point I'm willing to comb through all those errors.

As for using uVision 4, I am using uVision 5 with the legacy package which purportedly supports older Cortex-M processors but that does not work.

I will install MDK474 and try uVision 4 but if it doesn't work, how can I fix these errors?

I'm well versed in C/C++, I just have no domain knowledge in this context.

I've emailed IR Lock several times and tried to post on their forum, it's broken sadly, that is why I came here.

Thanks Rich!

On Sunday, March 12, 2017 at 9:22:47 AM UTC-7, Rich LeGrand wrote:

Hey Michael, 

Hmm, those are some weird errors, having to do with floating-point support-- some files have one type of fp support and some files have another type of fp support.  Combing through these errors might taked time, but It looks to me like the project configuration is somehow inconsistent.  Are you using uvision 5 or 4?  I'd use 4 because I think that's what they're using.   

Have you asked the IR lock folks?  The IR lock firmware is being maintained by them. 

 

On Sat, Mar 11, 2017 at 12:09 PM, Michael A <mtande...@gmail.com> wrote:

Hello, I'm trying to compile IR Lock's pixy firmware and running into trouble.

I've tried using Kiel but get over 500 build artifact errors.

I also tried LPCxpresso, it builds a hex but the hex can't be flashed on the Pixy. Pixymon outputs missing version number and memory errors.

Any help will be appreciated, thanks!

The firmware for source:

https://irlock.com/pages/archived-files

--
You received this message because you are subscribed to the Google Groups "pixy_firmware_sdk" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pixy_firmware_...@googlegroups.com.
To post to this group, send email to pixy_fir...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pixy_firmware_sdk/75613bc4-d944-4c0c-a7bf-60607f9f46fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Charmed Labs
www.charmedlabs.com