Jump to content
43oh

ronszon1426459902

Members
  • Content Count

    7
  • Joined

  • Last visited

About ronszon1426459902

  • Rank
    Noob Class
  1. I link with arm-none-eabi-ld, but the problem was that LIBGCC=${shell ${CC} ${CFLAGS} -print-libgcc-file-name} where CFLAGS= -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=softfp results in ~/sat/lib/gcc/arm-none-eabi/4.7.2/libgcc.a which is wrong. Putting -mfloat-abi=hard gives " ~/sat/lib/gcc/arm-none-eabi/4.7.2/thumb/cortex-m4/float-abi-hard/fpuv4-sp-d16/libgcc.a so that the correct library is linked. So it is precisely the same problem you had, however for some reason the "softfp" lib is not installed...
  2. Hi, Ufff, after a bit of debugging (and learning about gcc, that is never lost time ) I noticed that when I build with "-mfloat-abi=softfp" I get the default libgcc.a as doragasu earlier explained (memset gets compiled to blx instruction -> that gives a hard fault). Strangely, it seems that it was the summon-arm-toolchain that did not compile 'softfp' version. Is that possible? I don't have previous experience with arm toolchains... Any idea how I could force 'sat' to compile for 'softfp'? Either way, using 'hard' as '-mfloat-abi' does work!
  3. Uff, not much time for debug, but managed to get it a step futher. Apparently summon-arm-toolchain did not create softfp library (anybody knows why??? any way to make sure it does?) so I got into the pitfall as in http://forum.stellarisiti.com/topic/333-anyone-building-cmsis-under-linux where the memset operation gives a hard-fault. After compilation with 'hard' floating point setting it went a step further and SMPL_Init completes. I have to now try to link to my network, hopefully that works! Regards
  4. Hi, I fell in the same memset/blx hole as you I believe... I am trying to build the simpliciti stack for stellaris launchpad using gcc, but calls to memset use blx instruction what then causes hard failure of the program. However, I use only TI files for the moment. Also, I made sure (I think) I put -mthumb and -mcpu=cortex-m4 in the Makefile, so it should work according to your post. Any clue what alse could have gone wrong? I am no compilation expert, could you say in which way I could check which libraries were compiled in? Thanks!
  5. Yes.... I think I'll try to see if my code runs in CCS, these things happen I have modified the startup_gcc.c to have BSP_Gpio1Isr in correct places (I think), but that did not help...
  6. Hi, Thanks for your answer. I will share the results of my porting trial with pleasure Here it comes: https://github.com/kubaraczkowski/stellaris-launchpad_simpliciti (or simply git://github.com/kubaraczkowski/stellaris-launchpad_simpliciti.git). I adapted the pinout to match the CC2500 boosterpack(http://430things.blogspot.be/2012/02/cc2500-module-breakoutbooster-pack.html), but I don't have it myself, so I only hope I did not make a mistake here. I adapted: - bsp_button_defs.h (button 1 only for the moment) - bsp_drivers.c ( to enable appriopriate ports) - mrfi_board.c
  7. Hi, I am trying to run a simple SimpliciTI code on the Launchpad (mostly hub_dev example from stellarisware, modified to strip all graphic/touchscreen code), but I cannot figure why it does hangs on SMPL_Init... I modified the mrfi_board_defs.h and some more code around to point to other ports (bsp led driver works ok) but cannot go further. Anybody managed to successfully port the bsp code from stellarisware to the launchpad? Thanks!
×
×
  • Create New...