PSoC™ 4 Forum Discussions

Hi,

I have to write an own GUI Based Bootloader software for a PSOC BLE module. To save time, I would like to adapt the new software to the already prepared Visual Studio example project from Cypress. This software is included in "AN68272 (PSoC Creator 3.1 CP1).zip" If I debug this project and try to bootload a file, I always get an exception "System.BadImageFormatException". I use Visual Studio 2015 and tested the debug function with 3 different .cyacd files (generated by Cypress). So I think there must be an error in the published source code... Can anyone retrace this error?

Thanks in advance!

Pascal

Hi folks,

I'm trying to embed some inline assembly in my project to work around areas where I can't get the compiler and optimizer to do what I want.

I pulled the lst file for the main loop, and I can see a couple of places that I want to tweak, to save a few precious clock cycles. What has me confused is that the lst formatting looks like ARM assembly, but AN89610 (Code Optimization document for PSOC 4) says that PSOC 4 uses Thumb 2.

Is there a way to choose ARM or Thumb?

I modified the main loop portion of the lst code, and swapped it in within asm(" .... "); The result is a "Cannot represent THUMB_OFFSET relocation in this object file" error during build. There's a referenced .s file and line number, but I can't find the actual file. I'm guessing it's just temporary during the build process....? 

At this point, I'm getting almost the performance I need from my solution in C, but I have tried many variants, and only been able to find options that don't work. I do think I need the extra savings I can get from using assembly in the critical sections.

Thanks for the help,

Edit: I think I see the cause of the error: I missed that an array I'm using is represented as a label within the assembly block. I'll need to fix the assembly to correct address the array. I'm still rather confused about the ARM vs. Thumb stuff, though.

Paul

Using the kit, I do a lot of printf serial debugging via COM port and Putty.  Is there a way I can do the same with the MiniProg?  The reason being that I'm testing 2 devices, Central and Peripheral, and only have one kit and one MiniProg.  If there's any past discussion, please feel free to point me in the right direction.  I can't seem to find much specifically addressing it.  

Hi,

I have successfully written code to write the Device ID to row 0 of SFLASH.  Questions:

Is row0 the designated spot for the Device ID?  Just the first six bytes?

Is the SFLASH preserved during programming?  We would want to be able to update firmware while preserving the Device ID.

Right now I program the Device ID before BLE initialization, we will normally program it after.  What is the proper way to get the device in the state for SFLASH programming?  It does not work after our initialization (Including BLE init).

cybl10563-56lqxi

Thanks

Rich

I'm currently working on a BLE project with PSoC 4. Since today everything worked fine. But now I'm facing the error "undefined reference to main" every time I compile my project. Didn't change anything on the project or code since the last successful compilation.

Hope you can help me.