Jump to content
43oh

ervplecter

Members
 View Profile  See their activity

  • Content Count

    17

  • Joined

  • Last visited

  1. ervplecter
    some more information about this : Energia 009 shows the ports properly and lists (like arduino) ALL serial ports including the BT port / modem, using the /dev naming (aka tty and cu). for some reasons, it doesn't work the same since 010 or 011. I can't believe the serial port / peripherals could be filtered and that only "official" launchpad boards would be recognized, it doesn't make sense to me.
  2. ervplecter
    I'm digging this topic out (apologies). Having issues with OSX now we're deploying our boards within the team with collaborators equipped with macbook computers. Our CC3200 (mod) design doesn't use a FTDI chip but a silicon labs CP2102. We've installed the driver from silabs, it's signed. Other apps see the port without problem, they appear in /dev with tty. and cu. Obviously it's working just fine under windows. We've tested this on OSx yosemite : arduino (1.6) sees the com port, max msp as well, but the serial port menu is greyed in energia 0015. The only moment we can see something in
  3. ervplecter
    I keep narrowing down this issue with the profiles, it's really weird. If I use DHCP only, it works from scratch, most of the time to always. I sometimes have to reset the chip seven times to get it to work then it's going well afterwards, like if the 7 profiles were NOT there and had to be created by successive connections (that's after the chip has been formatted with uniflash). I'm at my wit ends with this thing. I've tried creating the files the CC3200 expects, using uniflash 3.2 and the configuration groups, it didn't change anything. With a static IP, it will first boot, connect and
  4. ervplecter
    I believe my issue posted here http://forum.43oh.com/topic/8426-cc3200-mod-bricked-with-static-ip/ is directly linked to this too. As soon as there's a static IP configuration that doesn't lead to a successful connection (in my case at least one UDP packet sent), the module will stall during wifi.init. I've traced it down to the profile deletion in the init function. I tried to remove profile storage (in all wifi.begin methods) along with the profile deletion in wifi.init, no dice. If I stick to DHCP, it seems to work indeed, no profiles were used in energia 0013 from what I see
  5. ervplecter
    no help ? please, somebody test this, even on a red bear lab mini wifi, so I can compare. I've tried 1.0.1.2 and 1.0.10 service packs, same behavior. I believe it has to see with the saved profiles.
  6. ervplecter
    Greetings, I'm almost at the end of my project with my CC3200 sensor board, and I want to thank again people who helped me here, for the SFLS lib and my printf issues. From the begining with energia, I had (minor) issues of bricking my board with no real understanding of WHAT was causing it. I finally took (had) the time to narrow it down to a very specific scheme, so I'd like to pick your brains about it. background : - started with a launchpad (of the first revisions), tried different service pack, never got issues. That's only when I started with my own board and the CC3200 mod
  7. ervplecter
    worked perferly thanks a lot
  8. ervplecter
    That's what I though, thank you. I actually came with the idea to make a secondary sketch that would have the file contents itself in the code. Upload and run, it checks for the file existences, upload the contents using SLFS. From there, the regular sketch is re uloaded (still in energia) and uses the file / ressource referenced by its name. That would allows users to stay in energia for updates but it's great to have several solutions for that thanks !
  9. ervplecter
    I want to thank you again for that lib, it's awesome and worked very well. I have an additional question regarding the file system : is there a way to specify a contents (var, char array, string, text) to be stored in a specific file of the file system so that it's part of the code project BUT isn't "compiled" with the mcuimg file, therefore not eating any code space when transferred to RAM for execution. More like a ressource finally. That would be neat if I could declare that ressource in my energia project, then having the bootloader writing the firmware (mcuimg) and the additional fi
  10. ervplecter
    I've just added this. #undef putchar int putchar(int c) { Serial.write©; return©; } It doens't matter where it's located in the main .ino. Same when inserted in another C file. if I comment the line //#define putchar(x) putc(x, stdout) in stdio.h, it does compile but still doesn't work (doesn't produce any char). I've tested compiling the above in a blank project without commenting stdio.h, same errors. Again, the stdio.h structure seems quite different compared to the MSP430 version where you're just asked to actually *provide* your own putchar (what I was do
  11. ervplecter
    Well, actually it doesn't compile error links to stdio.h. I've noticed that the structure for code structure for printf, puchar and putc in stdio.h is quite different between the msp version and the one used with the CC3200. v1_1.ino:34:5: error: expected unqualified-id before '--' token v1_1.ino:34:5: error: expected ')' before '--' token v1_1.ino:203:1: error: expected declaration before '}' token don't know what to do next. Anybody has done it with energia on an arm platform ?
  12. ervplecter
    thanks a lot, I'll give it a try !! I do have a terminal connected via serial (USB) on my module, I use it as a console, with a small command interpreter.
  13. ervplecter
    greetings, my wireless sensor project using the CC3200(mod) is coming up great and progressing fast. As I'm porting some code from my previous platform (pic + CC3000), I'm having trouble with the usual suspect printf. on the one hand, I've used simplified variants of printf in some arduino programs but I would definitely have the use of the full versatility of the stock printf as I'm far from the code size limit. In my previous platform / compiler, I just needed to provide the low level function that maps the output of printf to the UART, like putc or putchar. I've also read a
  14. ervplecter
    that's awesome news, just what I needed ! thanks a lot !
  15. ervplecter
    merci, thanks everyone
×
×
  • Create New...