greeeg
-
Content Count
561 -
Joined
-
Last visited
-
Days Won
53
Everything posted by greeeg
-
PIC also have a huge range of Micros. PIC10F,12F,16F,18F,24F,dsPIC,PIC32 Am I mistaken in thinking that microchip haven't moved into the ARM space yet? This is probably how they're doing it through acquiring Atmel. I personally started electronics with PICs and don't actually mind them, I then moved to Atmel and then MSP430 when the $4.30 launchpads came out. It will be interesting how this merger pans out. Will there be no new Atmel ICs? Will they become Microchip ICs? Microchip did this when the aquired SMSC, now all newly manufactured SMSC IC's are microchip branded. Would be kind
-
The first boards I assembled used wire links across the MOSFETS because I did not have any in stock. I designed the PCB to use SC70. (SOT323) does anyone know why there are SC and SOT part numbers? Turns out I tried using some SC59 (SOT 23) P channel's This did not work, at all. Turn out I wired the Source and the Drain the wrong way around. Because I hardly ever use P channels, and basically everything about them is inverted from N-channels. The way I have wired it in my original circuit, the current will always flow though the body diode!! So I've re-designed the PCB and sent it f
-
You can download it directly from the author here: http://elm-chan.org/fsw/ff/00index_e.html It will be compatible with energia, since energia just uses GCC to compile your sketches. However this method is not packaged as a library, so you will need to make changes to the lower level hardware driver to get it to connect with your SD card. Also note this library takes up around 8kb of FLASH in it's minimal R/W configuration with directories. Enabling some extra features increases this size. You should be fine on the CC3200. The link I posted has more detail, but you will need to imp -
How to protect your free code from companies predating on it ?
greeeg replied to CorB's topic in Suggestions
Maybe I'm misunderstanding the problem. But regardless of how you license the code if a company has patents on intellectual property they have legal grounds. There isn't really much us hobbyists can do. A single hobbyist against a big company with lawyers doesn't feel like a fair fight. Using git and online repo's probably helps. because it shows the development of the code over time. Thus showing original ideas / original code. Unless the "intellectual property issues and licence infringements" were related to UI design elements. then I guess you'd need to change them... Edit: I d -
http://www.ti.com/tool/ble-stack Not sure about the exact licence, but it's open source/royalty free. But it is also integrated with TI-RTOS. So it's quite a large beast to compile. Once the stack is setup in a project the API to make use of it is very straightforward. Then there is the fact that the stack itself will be running on the Network processor, and your code will run on the more powerful Application processor. In most of the examples I've worked with they deal with 2 sepeate CCS projects, one for the stack and one for the application.
-
You can add a .section attribute to your function declarations. Then add a .section relocation flag when you link. It's more common to indirectly address functions. You can have a function table at a fixed address. With each index of the table mapped to a specific function. You then populate this table with pointers to each function. It does take up more FLASH. Are you wanting to reuse some routines from within your main app? Typically this is avoided because it adds complications.
-
Did some more work today. Wanted to check out the size of the buttons, so I printed half a profile to get a feel for button placement, I feel like I had designed these a bit too small. Took a closer look at the battery protection circuitry. unsoldered one and sanded it down to get good images of the copper. then worked the images in photoshop. These have been added to the schematic/pcb so I don't have to have the board soldered inline. Schematic has been done. PCB is routed too, and here it is in it's natural environment. (Kicad 3d export is still kind of dodgy
-
@sven222 Any slight timing variations in the duty cycle will cause the brightness to be brighter or darker. If the rest of your program has even just a few conditional branches (if/else) then there will likely be some timing variations for the execution time of the main loop. The code you have here will maintain a constant +width on your LED. (assuming you don't use interrupts...) if this code is interrupted, then you could also get +width variations between cycles. If you can afford the hardware resources, utilizing a timer so you have a constant periodic event is the best way to go.
-
This is right, it's been discussed before, when the shipping first changed, it's 19USD for Shipping to Australia
-
From my experience with the sensor tag it is for the CC26xx's only. The size limit comes from the compiler, and the ARM compiler used for the CC26xx's is completely different to the TI MSP430 compiler. For the MSP, GCC is always free and un-restricted. (but does create slightly larger binaries by nature.) There was no key for the sensor-tag, just installing the simplelink compiler comes with no size restrictions. [it's still slightly limited, in that it doesnt support the more expensive (and faster) debuggers, but works perfectly well with the onboard debugger of the launchpad itself.]
-
Some more parts arrived this week. Batteries These are 650mAh round lipo cells. Bought from my local hobbyking, Super cheap, super high energy density. Because these are RC lipos, they lack any under voltage/overcurrent protection. Searching digikey for lipo protection didn't turn up anything particular cost effective, so I've got some generic protection PCBs these were about $0.30 each. I will either transplant the components onto my own PCB, or use them between the battery any my device as is. Finally the GPS units. These are similar, if not the same, as the units used
-
Glad to hear it's all working for you. It's been awhile since I did any work on MSP430 bootloaders. But recently I've done some AVR ones. One reason I can think for running it in RAM is for speed. Typically when a write is initiated other Flash reads are stalled. So running in RAM may yeild performance benefits, especially if the CPU can be receiving new data over UART while page writes are in progress. I also know that the MSP430 BSL makes use of a loadable bootloader that the Host PC loads into RAM, then runs it from the BSL interface. It can easily be updated by TI, and performs bet
-
@L.R.A The stack pointer will point to RAM unlikely you need to alter that in anyway. I suppose you've looked at the layout of the vectors on the TM4C. it appears that vector address 0 is actually the initial SP, hence jumping to that will case your program to jump into RAM. Try setting the PC to the address in vector 1? Thanks for the tip about the website, I haven't updated it for along time.... It's hosted on a server alongside some teamspeak servers me and some friends use for games. guess somehow the http server was closed. It's back up now for what it's worth. (hasn't been up
-
@@spirilis nice setup, you could add some WS2812's to the Launchpad, illuminate the back with red when it's hot and blue when it cools down!
-
How did you compile your app code? I'm not 100% on the ISR implementation for the TM4C. I suspect that the value at 0x4000 actually directs the PC into the main routine as if the app code was loaded at 0x0000. You will need to atleast add some linker flags in order to push your .text block down to 0x4000, the linker needs to know where the program will be loaded in order to patch any absolute addresses. Typically bootloaders can be designed to sit at the bottom of the FLASH, that way the app doesn't require special compiling options.
-
I was thinking the same thing. The trouble with going to the gray market, and why I generally don't buy ICs, outside of hobby stuff, from ebay/ali. The trouble is you can't tell, unless you use an authorized distributor. Interesting to see if the wifi Sensorpack makes use of one of these modules. Because that's bound to be around a similar price point. $30, like the bluetooth one.
-
Looks like they recommend using a DSO. I wonder if I can use my '89 vintage Tektronix 2430 digital oscilloscope. (1024 sample means it's kind of lacking in the storage department though.)
-
What a great start to the new year, Congratulations.
-
This project now has a github page. (barely) Got TI's example firmware to a surprisingly functional state. The GPS implementation is very basic, serial data comes in via Interrupt. data is stored in a buffer, if buffer is full buffer switches to second buffer, notifies main loop. main loop upon getting notification write buffer into file on SD card. I'm using TI's MSC example. which already has USB event functions that are used to start/stop this File writing when USB is connected/disconnected. https://github.com/Greeeg/gpsLogger Still alot to do, would like a basic text_f
-
Z height should be OK, only have 50mm of travel. But that can be offset, by manual moving the spindle in it's holder. It's just one of these elcheapo Chinese CNC mills. (with a spindle upgrade) I honestly, didn't consider it. Atleast here in Australia, cheap phones generally lack GPS. You need to get into the $50+ range to get that feature. Of course there are specials sometimes. I think the biggest thing would be altering their workflow. A phone (especially cheap ones) might take a minute or two just to boot. Then they'd have to open the app. and I'm sure it's possible, but I've
-
@Fred, this is What I was thinking. This cutout could extend downwards but then the part would need to be mounted on the curved side. and you would be cutting out a very unsupported thin wall. I doubt this is achievable on my small mill. The cutout could extend upwards, so the part can be mounted flat against the mill's table. I think this is what you're suggesting like so Which is a good compromise. I need to source the toggle switch and pushbutton, and see if those can be incorporated in similar ways. Good point about the project name, I actually didn't realize that at
-
I just looked at TI's MSP lineup again. 522 MSP430 devices 2 MSP432 devices But keep in mind the MSP430 core is TI's IP, but the is a license cost associated with using the ARM CPU. I'm not sure how that's billed, if it's per chip design/revision. It is interesting that they haven't locked it down to production ready device yet, but I suspect it will be similar to the Simplelink series. 2x Wifi 9x CC26x (3 devices with 3 package sizes each) Both of these are multicore (App + network processor) SoC's but lack many of the options available for the MSP430 series. I suspect that by
-
@@zeke Microsoft Visio, it's part of Micorosoft Office (But you can buy it individually). I've actually never used it before, but I got given a license from my university. Figured I'd try it out. It's more user friendly than the online based diagram tools I've used in the past. http://visio.microsoft.com/
-
I intend to finish this project in a usable state. So I've got to pick an enclosure right off the bat. There are a few options, all with their pros and cons. Option 1 OKW minitec series. (https://www.okw.com.au/en/Plastic-enclosures/Minitec.htm) 3d Mockups Pros Slimline Simple 2 part design Nice looking Cons Expensive (>$10) Curved design makes cutouts difficult. Verdict, Probably Too difficult to machine the cutouts myself, would add significant cost. Option 1a Minitec Teardrop series Pros: Has a flat surface, should be easy to mill cutouts Slimline C
-
I know I haven't finished off my desk clock project just yet, But I've been requested to design a new GPS logging device for my sisters Beagle Club, The basic idea is that a sent is placed with a guy that forms a path, the GPS logger is taken along also. They then attach the device to a beagle (using some kind of vest, I think). And let them follow the scent. Post event they extract the GPS data from the logger and overlay both tracks in google earth. They have one unit that has been working well for them, developed by a previous club member. It consists of off the shelf c
