Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mhoneywill

Pages: 1 [2] 3 4 ... 12
16
µTasker general / Re: TFTP Boot
« on: October 21, 2011, 03:30:59 PM »

17
µTasker general / Re: Zero-configuration protocol (AUTO-IP)
« on: August 04, 2011, 10:56:48 PM »
Great News,

Is it easily available for the Luminary release?

Thanks very much for this Mark

Regards

Martin

 

18
µTasker general / Re: WiFi module RN-171
« on: July 21, 2011, 10:32:47 AM »
Having a quick look at the RN-171 module, it looks like this is a complete WiFi module and TCPIP stack, and that when setup correctly it will configure the Wifi Connection automatically.

In this sense it would be completely independent of the uTasker TCPIP stack. It looks like you would configure the module, let it make the connection then transfer data from your application directly to the module for transmission. You should think of it more like a Modem rather than a Wifi module. The modules job is to hide all the Wifi operation from the user.

Cheers

Martin

19
µTasker general / Re: DDNS Support
« on: June 30, 2011, 06:20:10 PM »
Looks pretty simple to update the DNS server see http://www.dyndns.com/developers/specs/syntax.html

Code: [Select]
http://username:password@members.dyndns.org/nic/update?hostname=yourhostname&myip=ipaddress&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG
Cheers

Martin

20
Hi Tonko,

The laskater example is actually a VNC client, what I understand you want is a VNC server, so I think its best you look at the uvnc code which has now been rolled into Contiki as mentioned in my earlier post. Once unpacked look here "contiki-2.4\core\ctk" for the server code

Cheers

Martin

21
Good points, Mark.

I did a bit of Googling around to point Tonko in areas to look at, and also to give info to others who might read the post.

The VNC approach does have a certain, novelty to it especially as it would support keyboard input. Would also provide a way of simulating Displays that the VC Simulator does not currently support.

I agree that a Web interface also has advantages. It would be good to allow for the code to gracefully handle there being no physical display avaliable. I'm looking at the display code in the next few weeks and will see how easy this is to do and report back.

Cheers

Martin

22
Interesting concept this might be of use http://virtuallab.tu-freiberg.de/p2p/p2p/vnc/ug/rfbcounter.html although the source seems to be long gone.

Another way to do this would be to use the graphics lib to create a memory map of the virtual screen, which it does anyway. so for a 256 x 64 monochrome screen this would be (256 x 64)/8 = 2048 bytes large. This could then be embedded as a BMP or possibly more efficient PNG or GIF in a web page which would take up two Ethernet packets uncompressed. You would just generate the BMP of the screen on the fly as required. This way a VNC client would not be needed.

Further investigation into the VNC protocol, seems to imply it is pixel based so very similar to the above see http://en.wikipedia.org/wiki/RFB_protocol and the protocol description here http://www.realvnc.com/docs/rfbproto.pdf

This also looks like an interesting link http://www.sics.se/~adam/uvnc/ an embedded VNC server for 8 bit devices developed by Adam Dunkels of UIP fame. This has now been incorporated into  Contiki here http://www.sics.se/contiki/download.html

Here is details of Seggers emwin VNC server http://www.segger.com/cms/vnc-support.html

Cheers

Martin

23
µTasker general / Re: New USB MSD Boot Loader
« on: June 12, 2011, 10:14:43 PM »

Hi Martin,

Are you changing from the LM3 parts due to supply issues? I ask as I am looking at dumping the TI  parts and changing to another processor.

Cheers,

Peter.

Hi Peter,

Sorry for the delay in replying, There are a few reasons I'm looking at other chips.

1. Sometimes I need more that the 3 Uarts supplied on the Luminary Chips

2. I too am worried about supply, but I'm also not sure how available the Kinetis K60 parts are?

3. Some designs I'm looking at having dual Ethernet ports, to allow products to be daisy chained. This is easier to do with a MMII or RMMII interface, see the following links for possible chips to use http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=102;65;107&PLine=65 or http://www.micrel.com/_PDF/Ethernet/KS8893ML-pb.pdf or http://www.dacomwest.de/eng/e_etherics_switch_dm8603.htm

4. Mark seems to be very fond of the Kinetis chips, so it seems that a lot of uTasker development is focused in this direction at the moment.

Regards

Martin

24
ATMELTM AT91SAM7X and AVR32 / Re: USB Support for AVR32
« on: June 09, 2011, 09:48:44 PM »
Don't know much about AVR32 but you might want to investigate this link http://www.fourwalledcubicle.com/LUFA.php might help with USB support on AVR's

I seem to remember the programmer was talking about AVR32's at one point, maybe an email to him might get some more info

Cheers

Martin

25
Hi,

Out of interest what type of screen are you trying to interface via SPI? do you have a part number

Cheers

Martin

26
µTasker general / Re: New USB MSD Boot Loader
« on: May 10, 2011, 07:31:11 AM »
Very Nice, now I must get a Kinetis demo kit.

I'm looking at new processors at the moment and am either going towards the Kinetis or NXP LPC17xx. Not sure how avaliable Kinetis K60 parts are yet.

Cheers

Martin

27
If you are going to look at UIP then it might be worth looking at LWIP http://savannah.nongnu.org/projects/lwip/ . UIP is very simple and may well be too simple for your requirements.

FreeRtos has demo's for the NXP chips you are looking at and I think they have LWIP and UIP demos http://www.freertos.org/

One think I really value about uTasker is the quality and speed of Mark's support (I my opinion the best of any software product I've purchased), this has helped me out even when the documentation doesn't cover everything.

Good Luck with your investigations.

Cheers

Martin

28
LCD Graphics Library and Simulator / Re: glcd 240*128
« on: March 08, 2011, 11:56:05 PM »
I'm sorry but uTasker does not support the ATmega range of processors.
Codevision is the compiler you use, that does note really make any different you are just looking for C source code to drive your display.

You also did not say which display you were using and which chip was used in the display, this is the important thing. There are many different types of display driver chips, all need slightly different software code to set them up and drive them.

But as I said before uTasker does not support the ATMega

Regards

Martin


29
Luminary Micro TM LM3SXXXX / Re: Code hitting irq_hard_fault(void)
« on: March 03, 2011, 07:00:05 PM »
Hi Mark,

I'd been ignoring this problem as most of my code does not use the ADC, but have just come across it again.

I think I've fixed my problem by doing the following

                    RCGC0 |= CGC_SARADC0;                                // enable clocks to ADC module
                    RCGC0 |= CGC_SARADC0;                                // repeat above command to give the ADC module time to wakeup
                    ADCACTSS_0 &= ~ASEN0;                                // ensure sequencer is disabled before configuring
                    ADCEMUX_0 &= ~SS0_MASK;                              // clear sequencer mode

Arround line 4657 in the function fnConfigureInterrupt in LM3Sxxxx.c I've added the above line in RED, I think the access to the ADCACTSS_0 register was happening before the ADC module had powered up. Hence I was getting an irq_hard_fault

It seems to be working fine now, I can download from Rowley in Debug mode and start debugging into the code. This may not have been your problem but it might be worth incorporating or checking out (Still not quite sure why the release build without the JTAG just worked)

Cheers

Martin

30
utFAT / Re: SD Card questions
« on: February 23, 2011, 06:09:04 PM »
Hi Dave,

I agree about the write protect switch it should be supported in software and just #defined out if not used.

As you say, a system that will re-init the card if it detects a no reply would be nice and neat as it would automatically cover both cases of a reinsertion of the same card or a re-insertion of a different card.

I'm presuming a newly inserted card will not communicate unless an init sequence has been performed.

Also LFN support when writing would be nice.

Cheers

Martin

Pages: 1 [2] 3 4 ... 12