--- In ts-7000@yahoogroups.com, "drex459" <dexterjagula@...> wrote:
>
> I'm pretty new to working in UNIX, and have to do some development on the
TS-8390-4700 board. Before I get started I have to use an image provided by TS.
I need some help backing-up an existing micro SD card, and "dropping" an imagine
onto the same micro-SD card.
>
> Here is a summary of what I have to do:
> 1. Back-up the existing micro-SD card (that came with the  TS-8390-4700
board).
> 2. "Drop" a downloaded image onto the micro-SD card.
> 3. If necessary, how to revert the micro-SD card to the backed-up image.
>
> Here's where I am, and what I still have to do:
> 1. Using the "sudo fdisk -l" command, I was able to see that the micro-SD card
had a few partitions on it (/dev/sdb1, /dev/sdb2, /dev/sdb3, /dev/sdb4). I then
used the command "sudo dd if=/dev/sdb of=sd.iso", which returned the following
result:
> 3862528+0 records in
> 3862528+0 records out
> 1977614336 bytes (2.0 GB) copied, 505.756 s, 3.9 MB/s
> which looks like it got backed-up successfully to the .iso file. Is this the
best way to back-up/image the micro-SD card, so that I can revert ALL files and
partitions to the way it was?
>
> 2. The image I require is:
"ftp://ftp.embeddedarm.com/ts-socket-macrocontrollers/ts-4800-linux/binaries/ts-\
images/2gbsd-latest.dd.gz" Once downloaded, how can I extract this image and
"drop" it on the micro-SD card? Can I use the 'dd' utility to do this? Or some
other utility? Do I have to format the micro-SD card first?
>
> 3. If I want to revert the micro-SD card back to the way it was before I
"dropped" the image onto it, how do I do that using the .iso type (or any file
type) using the 'dd' utility?
>
> These questions may seem basic, but any help would be greatly appreciated!
Thanks in advance!
>

So far I think you've got it.  'dd' is the right utility for doing straight
binary copy from one file/device to another.  Since your card is showing up on
/dev/sdb, after step 1 above you now have the original card image backed up in
the sd.iso file.  This includes the MBR on the card and can be used to restore
the card image by using dd again in exactly the same way: "dd if=sd.iso
of=/dev/sdb bs=32k"   Setting the block size to 32k is a performance enhancer
when writing to the card.

For (2), writing a downloaded image to the card, you must first gunzip the
downloaded file.  Also note that you need to match the SD card size to the
image.  Don't try to put an 8Gb image on a 2 gig card and vice versa.  Then it's
just "dd if=<downloaded unzipped image> of=/dev/sdb bs=32k"  to load it on the
card.  Note that it takes a loooooong time to write to an SD card this way, so
be patient.  Since you are writing a complete filesystem image to the card
including the MBR there is no formatting necessary.  Just plug in a card and go.

For (3) see step one above, just write your original sd.iso image back onto the
card with dd.

Things to remember:

dd is a very low level operation, no formatting or partitioning of a card is
necessary to use it.

Use the block size (bs=32k) parameter to improve performance when writing to sd
cards.  Leave this off when saving image from the card to disk.

Match downloaded binary image size to card size.  Note that the downloaded
binary image is usually about 10% smaller than the size of the card in order to
allow for the size of the card to shrink slightly over time due to sectors
wearing out.

Be sure to unzip downloaded images prior to writing to SD card.

-Jeff

I no longer receive e-mail copies from the list of my e-mails to the
list (I do see the e-mails appear on the web interface to the group).
If someone receives this _e-mail_ from the group, please reply directly
to me so that I know that others are able to see my posts.  Thank you.

Don

Thanks, Harry.  Everyone, my posts seem to be getting there so my test
is complete.  My apologies for the spam.

Don
On 4/3/2012 9:38 AM, harry olar wrote:
> There you go.
>
> ------------------------------------------------------------------------
> *From:* Don Tucker <dtucker@...>
> *To:* ts-7000@yahoogroups.com
> *Sent:* Tuesday, April 3, 2012 10:24 AM
> *Subject:* [ts-7000] test
>
> I no longer receive e-mail copies from the list of my e-mails to the
> list (I do see the e-mails appear on the web interface to the group).
> If someone receives this _e-mail_ from the group, please reply
> directly to me so that I know that others are able to see my posts.
> Thank you.
>
> Don
>
>
>

You're good Don. Sounds like some sort of issue with a spam filter.
Larry

On 4/3/2012 10:24 AM, Don Tucker wrote:
> I no longer receive e-mail copies from the list of my e-mails to the
> list (I do see the e-mails appear on the web interface to the group).
> If someone receives this _e-mail_ from the group, please reply
> directly to me so that I know that others are able to see my posts.
> Thank you.
>
> Don
>

With the -r option, ts7800ctl outputs sample values in raw bits.
With the -S option, ts7800ctl outputs sample values in ASCII strings.
In either case, ts7800ctl.c reads the sample values in bits.


--- In ts-7000@yahoogroups.com, Vidhya Verma <vidhyaverma88@...> wrote:
>
> Hi,
>
>          I have a one doubt here , that ts7800ctl.c code is for outputting
> sample values which I got it , but now I need digital output in bits.
>
>
> ________________________________
>  From: Mark Featherston <mark@...>
>

Thanks for the help Jeff!

I'm not quite out of the woods just yet.

I first used gunzip to unzip the file (2gbsd-latest.dd.gz), as you suggested,
which left me with '2gbsd-latest.dd'.
Then I used: "sudo dd if=2gbsd-latest.dd of=/dev/sdb bs=32k" (and also without
the "bs=32k").

But I keep getting the message: dd: writing to `/dev/sdb': No space left on
device

It is a 2GB micro-SD card, and this image from TS suggests it is meant for that
size card, so I'm not sure why it's not working. Thoughts?

Thanks!


--- In ts-7000@yahoogroups.com, "jeffs7283" <jeffs@...> wrote:
>
>
>
> --- In ts-7000@yahoogroups.com, "drex459" <dexterjagula@> wrote:
> >
> > I'm pretty new to working in UNIX, and have to do some development on the
TS-8390-4700 board. Before I get started I have to use an image provided by TS.
I need some help backing-up an existing micro SD card, and "dropping" an imagine
onto the same micro-SD card.
> >
> > Here is a summary of what I have to do:
> > 1. Back-up the existing micro-SD card (that came with the  TS-8390-4700
board).
> > 2. "Drop" a downloaded image onto the micro-SD card.
> > 3. If necessary, how to revert the micro-SD card to the backed-up image.
> >
> > Here's where I am, and what I still have to do:
> > 1. Using the "sudo fdisk -l" command, I was able to see that the micro-SD
card had a few partitions on it (/dev/sdb1, /dev/sdb2, /dev/sdb3, /dev/sdb4). I
then used the command "sudo dd if=/dev/sdb of=sd.iso", which returned the
following result:
> > 3862528+0 records in
> > 3862528+0 records out
> > 1977614336 bytes (2.0 GB) copied, 505.756 s, 3.9 MB/s
> > which looks like it got backed-up successfully to the .iso file. Is this the
best way to back-up/image the micro-SD card, so that I can revert ALL files and
partitions to the way it was?
> >
> > 2. The image I require is:
"ftp://ftp.embeddedarm.com/ts-socket-macrocontrollers/ts-4800-linux/binaries/ts-\
images/2gbsd-latest.dd.gz" Once downloaded, how can I extract this image and
"drop" it on the micro-SD card? Can I use the 'dd' utility to do this? Or some
other utility? Do I have to format the micro-SD card first?
> >
> > 3. If I want to revert the micro-SD card back to the way it was before I
"dropped" the image onto it, how do I do that using the .iso type (or any file
type) using the 'dd' utility?
> >
> > These questions may seem basic, but any help would be greatly appreciated!
Thanks in advance!
> >
>
> So far I think you've got it.  'dd' is the right utility for doing straight
binary copy from one file/device to another.  Since your card is showing up on
/dev/sdb, after step 1 above you now have the original card image backed up in
the sd.iso file.  This includes the MBR on the card and can be used to restore
the card image by using dd again in exactly the same way: "dd if=sd.iso
of=/dev/sdb bs=32k"   Setting the block size to 32k is a performance enhancer
when writing to the card.
>
> For (2), writing a downloaded image to the card, you must first gunzip the
downloaded file.  Also note that you need to match the SD card size to the
image.  Don't try to put an 8Gb image on a 2 gig card and vice versa.  Then it's
just "dd if=<downloaded unzipped image> of=/dev/sdb bs=32k"  to load it on the
card.  Note that it takes a loooooong time to write to an SD card this way, so
be patient.  Since you are writing a complete filesystem image to the card
including the MBR there is no formatting necessary.  Just plug in a card and go.
>
> For (3) see step one above, just write your original sd.iso image back onto
the card with dd.
>
> Things to remember:
>
> dd is a very low level operation, no formatting or partitioning of a card is
necessary to use it.
>
> Use the block size (bs=32k) parameter to improve performance when writing to
sd cards.  Leave this off when saving image from the card to disk.
>
> Match downloaded binary image size to card size.  Note that the downloaded
binary image is usually about 10% smaller than the size of the card in order to
allow for the size of the card to shrink slightly over time due to sectors
wearing out.
>
> Be sure to unzip downloaded images prior to writing to SD card.
>
> -Jeff
>

It appears your SD card has probably lost too many sectors.  Go get a brand new
2G SD card and try again.  Also there is a utility that you might be interested
in: http://oss.digirati.com.br/f3/   This is a utility to test SD cards and in
particular tests them to see if they are counterfeits.  Unfortunately
counterfeiting is rampant in these things, and the "no space left on device"
error can be symptomatic of a counterfeit device.  Always purchase SD or microSD
cards from reputable sources, and be sure to run the F3 utility on any new or
unknown cards to be sure they really are what they say they are.

--- In ts-7000@yahoogroups.com, "drex459" <dexterjagula@...> wrote:
>
> Thanks for the help Jeff!
>
> I'm not quite out of the woods just yet.
>
> I first used gunzip to unzip the file (2gbsd-latest.dd.gz), as you suggested,
which left me with '2gbsd-latest.dd'.
> Then I used: "sudo dd if=2gbsd-latest.dd of=/dev/sdb bs=32k" (and also without
the "bs=32k").
>
> But I keep getting the message: dd: writing to `/dev/sdb': No space left on
device
>
> It is a 2GB micro-SD card, and this image from TS suggests it is meant for
that size card, so I'm not sure why it's not working. Thoughts?
>
> Thanks!
>
>
> --- In ts-7000@yahoogroups.com, "jeffs7283" <jeffs@> wrote:
> >
> >
> >
> > --- In ts-7000@yahoogroups.com, "drex459" <dexterjagula@> wrote:
> > >
> > > I'm pretty new to working in UNIX, and have to do some development on the
TS-8390-4700 board. Before I get started I have to use an image provided by TS.
I need some help backing-up an existing micro SD card, and "dropping" an imagine
onto the same micro-SD card.
> > >
> > > Here is a summary of what I have to do:
> > > 1. Back-up the existing micro-SD card (that came with the  TS-8390-4700
board).
> > > 2. "Drop" a downloaded image onto the micro-SD card.
> > > 3. If necessary, how to revert the micro-SD card to the backed-up image.
> > >
> > > Here's where I am, and what I still have to do:
> > > 1. Using the "sudo fdisk -l" command, I was able to see that the micro-SD
card had a few partitions on it (/dev/sdb1, /dev/sdb2, /dev/sdb3, /dev/sdb4). I
then used the command "sudo dd if=/dev/sdb of=sd.iso", which returned the
following result:
> > > 3862528+0 records in
> > > 3862528+0 records out
> > > 1977614336 bytes (2.0 GB) copied, 505.756 s, 3.9 MB/s
> > > which looks like it got backed-up successfully to the .iso file. Is this
the best way to back-up/image the micro-SD card, so that I can revert ALL files
and partitions to the way it was?
> > >
> > > 2. The image I require is:
"ftp://ftp.embeddedarm.com/ts-socket-macrocontrollers/ts-4800-linux/binaries/ts-\
images/2gbsd-latest.dd.gz" Once downloaded, how can I extract this image and
"drop" it on the micro-SD card? Can I use the 'dd' utility to do this? Or some
other utility? Do I have to format the micro-SD card first?
> > >
> > > 3. If I want to revert the micro-SD card back to the way it was before I
"dropped" the image onto it, how do I do that using the .iso type (or any file
type) using the 'dd' utility?
> > >
> > > These questions may seem basic, but any help would be greatly appreciated!
Thanks in advance!
> > >
> >
> > So far I think you've got it.  'dd' is the right utility for doing straight
binary copy from one file/device to another.  Since your card is showing up on
/dev/sdb, after step 1 above you now have the original card image backed up in
the sd.iso file.  This includes the MBR on the card and can be used to restore
the card image by using dd again in exactly the same way: "dd if=sd.iso
of=/dev/sdb bs=32k"   Setting the block size to 32k is a performance enhancer
when writing to the card.
> >
> > For (2), writing a downloaded image to the card, you must first gunzip the
downloaded file.  Also note that you need to match the SD card size to the
image.  Don't try to put an 8Gb image on a 2 gig card and vice versa.  Then it's
just "dd if=<downloaded unzipped image> of=/dev/sdb bs=32k"  to load it on the
card.  Note that it takes a loooooong time to write to an SD card this way, so
be patient.  Since you are writing a complete filesystem image to the card
including the MBR there is no formatting necessary.  Just plug in a card and go.
> >
> > For (3) see step one above, just write your original sd.iso image back onto
the card with dd.
> >
> > Things to remember:
> >
> > dd is a very low level operation, no formatting or partitioning of a card is
necessary to use it.
> >
> > Use the block size (bs=32k) parameter to improve performance when writing to
sd cards.  Leave this off when saving image from the card to disk.
> >
> > Match downloaded binary image size to card size.  Note that the downloaded
binary image is usually about 10% smaller than the size of the card in order to
allow for the size of the card to shrink slightly over time due to sectors
wearing out.
> >
> > Be sure to unzip downloaded images prior to writing to SD card.
> >
> > -Jeff
> >
>

Hey Everyone,

So far, every issue that I have asked for help with via this message board has
been answered for me by you wonderful people. Here's hoping you guys are willing
and able to help me out with this one too!

I am now using a custom 2.6.34 kernel, however, Udev is not using my rules and
adding them to the /dev/ directory. Does anyone know of anything that I may have
overlooked in compiling my kernel that could result in Udev not working
properly? I have verified my rules and they are fine (they also work perfectly
on the 2.6.29 kernel).

Any help or insight would be greatly appreciated! Thanks

I am able to crosscompile and run my software on the board without any problems.

However when I try to use floating point in my software I am having runtime
issues.

Would those of you using floating point mind posting all of your compiler and
linking flags.

Thanks in advance

On Mon, Apr 2, 2012 at 8:39 AM, komal<komalrauf@...>  wrote:
> I have recently acquired a ts-7500 board with the development kit. The SD
> card comes with a 2.6.24 Linux Kernel. After a few days of experimenting I
> have realized that my application (controlling a servo through PWM) will
> require HRT and RT support which the Kernel is unable to provide (maximum
> timer resolution I am getting on the current Kernel is 20ms).

When I needed high resolution timing to toggle a couple of lines on the DIO
header of a TS-7250 I used a small custom kernel module that used a CPU
timer to generate interrupts and the ISR flipped the DIO bits.

--
Cheers!

Kevin.

http://www.ve3syb.ca/           |"Nerds make the shiny things that distract
Owner of Elecraft K2 #2172      | the mouth-breathers, and that's why we're
                                  | powerful!"
#include <disclaimer/favourite> |             --Chris Hardwick

At TS we just had to reject a batch of around 500 flash devices we ordered
because they weren't passing our stress tests.  I don't think they were
counterfeit but just of extremely low quality.  The industry is adopting "TLC"
tri-level cell flash at an increasing rate which is just extremely unreliable.

We have definitely found the quality of SD flash is deteriorating and we just
released some software to address some of this on the TS-7520:
http://www.embeddedarm.com/about/resource.php?item=628

As part of the above described "DoubleStore" software layer, we have created our
own stress test that is much better than the utilities currently available on
the internet as they work underneath the filesystem layer rather than through
it.  New TS-7520's ship with a "sdctl" binary that has a "--stresstest" option
that repeatedly writes/verifies sectors at a block layer.  We have a long term
test about 50 boards and 50 SD cards running right now.  The cards that have
survive the longest seem to be cards that were manufactured several years ago.
We have a 2007 512MB Sandisk that has been running for over a month now writing
continuously at 4MByte/sec with 0 glitches)

//Jesse Off

--- In ts-7000@yahoogroups.com, "jeffs7283" <jeffs@...> wrote:
>
> It appears your SD card has probably lost too many sectors.  Go get a brand
new 2G SD card and try again.  Also there is a utility that you might be
interested in: http://oss.digirati.com.br/f3/   This is a utility to test SD
cards and in particular tests them to see if they are counterfeits. 
Unfortunately counterfeiting is rampant in these things, and the "no space left
on device" error can be symptomatic of a counterfeit device.  Always purchase SD
or microSD cards from reputable sources, and be sure to run the F3 utility on
any new or unknown cards to be sure they really are what they say they are.
>
> --- In ts-7000@yahoogroups.com, "drex459" <dexterjagula@> wrote:
> >
> > Thanks for the help Jeff!
> >
> > I'm not quite out of the woods just yet.
> >
> > I first used gunzip to unzip the file (2gbsd-latest.dd.gz), as you
suggested, which left me with '2gbsd-latest.dd'.
> > Then I used: "sudo dd if=2gbsd-latest.dd of=/dev/sdb bs=32k" (and also
without the "bs=32k").
> >
> > But I keep getting the message: dd: writing to `/dev/sdb': No space left on
device
> >
> > It is a 2GB micro-SD card, and this image from TS suggests it is meant for
that size card, so I'm not sure why it's not working. Thoughts?
> >
> > Thanks!
> >
> >
> > --- In ts-7000@yahoogroups.com, "jeffs7283" <jeffs@> wrote:
> > >
> > >
> > >
> > > --- In ts-7000@yahoogroups.com, "drex459" <dexterjagula@> wrote:
> > > >
> > > > I'm pretty new to working in UNIX, and have to do some development on
the TS-8390-4700 board. Before I get started I have to use an image provided by
TS. I need some help backing-up an existing micro SD card, and "dropping" an
imagine onto the same micro-SD card.
> > > >
> > > > Here is a summary of what I have to do:
> > > > 1. Back-up the existing micro-SD card (that came with the  TS-8390-4700
board).
> > > > 2. "Drop" a downloaded image onto the micro-SD card.
> > > > 3. If necessary, how to revert the micro-SD card to the backed-up image.
> > > >
> > > > Here's where I am, and what I still have to do:
> > > > 1. Using the "sudo fdisk -l" command, I was able to see that the
micro-SD card had a few partitions on it (/dev/sdb1, /dev/sdb2, /dev/sdb3,
/dev/sdb4). I then used the command "sudo dd if=/dev/sdb of=sd.iso", which
returned the following result:
> > > > 3862528+0 records in
> > > > 3862528+0 records out
> > > > 1977614336 bytes (2.0 GB) copied, 505.756 s, 3.9 MB/s
> > > > which looks like it got backed-up successfully to the .iso file. Is this
the best way to back-up/image the micro-SD card, so that I can revert ALL files
and partitions to the way it was?
> > > >
> > > > 2. The image I require is:
"ftp://ftp.embeddedarm.com/ts-socket-macrocontrollers/ts-4800-linux/binaries/ts-\
images/2gbsd-latest.dd.gz" Once downloaded, how can I extract this image and
"drop" it on the micro-SD card? Can I use the 'dd' utility to do this? Or some
other utility? Do I have to format the micro-SD card first?
> > > >
> > > > 3. If I want to revert the micro-SD card back to the way it was before I
"dropped" the image onto it, how do I do that using the .iso type (or any file
type) using the 'dd' utility?
> > > >
> > > > These questions may seem basic, but any help would be greatly
appreciated! Thanks in advance!
> > > >
> > >
> > > So far I think you've got it.  'dd' is the right utility for doing
straight binary copy from one file/device to another.  Since your card is
showing up on /dev/sdb, after step 1 above you now have the original card image
backed up in the sd.iso file.  This includes the MBR on the card and can be used
to restore the card image by using dd again in exactly the same way: "dd
if=sd.iso of=/dev/sdb bs=32k"   Setting the block size to 32k is a performance
enhancer when writing to the card.
> > >
> > > For (2), writing a downloaded image to the card, you must first gunzip the
downloaded file.  Also note that you need to match the SD card size to the
image.  Don't try to put an 8Gb image on a 2 gig card and vice versa.  Then it's
just "dd if=<downloaded unzipped image> of=/dev/sdb bs=32k"  to load it on the
card.  Note that it takes a loooooong time to write to an SD card this way, so
be patient.  Since you are writing a complete filesystem image to the card
including the MBR there is no formatting necessary.  Just plug in a card and go.
> > >
> > > For (3) see step one above, just write your original sd.iso image back
onto the card with dd.
> > >
> > > Things to remember:
> > >
> > > dd is a very low level operation, no formatting or partitioning of a card
is necessary to use it.
> > >
> > > Use the block size (bs=32k) parameter to improve performance when writing
to sd cards.  Leave this off when saving image from the card to disk.
> > >
> > > Match downloaded binary image size to card size.  Note that the downloaded
binary image is usually about 10% smaller than the size of the card in order to
allow for the size of the card to shrink slightly over time due to sectors
wearing out.
> > >
> > > Be sure to unzip downloaded images prior to writing to SD card.
> > >
> > > -Jeff
> > >
> >
>

It worked!

I tried writing the image to the card again, and it worked this time. I didn't
do anything different. Ah well...

49544+0 records in
49544+0 records out
1623457792 bytes (1.6 GB) copied, 348.628 s, 4.7 MB/s


--- In ts-7000@yahoogroups.com, Dexter Jagula <dexterjagula@...> wrote:
>
> Thanks again Jeff!
>
> I don't think it is a bad micro SD card. Unless some sectors got lost when
> I backed it up using 'dd'. The micro SD card came with the board from TS,
> so I doubt it's a counterfeit device.
>
> Let me know if you have any other ideas. I'm going to pick-up a bigger
> micro SD card tonight anyway, and see if that makes a difference.
>
> On Wed, Apr 4, 2012 at 8:17 AM, jeffs7283 <jeffs@...> wrote:
>
> > **
> >
> >
> > It appears your SD card has probably lost too many sectors. Go get a brand
> > new 2G SD card and try again. Also there is a utility that you might be
> > interested in: http://oss.digirati.com.br/f3/ This is a utility to test
> > SD cards and in particular tests them to see if they are counterfeits.
> > Unfortunately counterfeiting is rampant in these things, and the "no space
> > left on device" error can be symptomatic of a counterfeit device. Always
> > purchase SD or microSD cards from reputable sources, and be sure to run the
> > F3 utility on any new or unknown cards to be sure they really are what they
> > say they are.
> >
> >
> > --- In ts-7000@yahoogroups.com, "drex459" <dexterjagula@> wrote:
> > >
> > > Thanks for the help Jeff!
> > >
> > > I'm not quite out of the woods just yet.
> > >
> > > I first used gunzip to unzip the file (2gbsd-latest.dd.gz), as you
> > suggested, which left me with '2gbsd-latest.dd'.
> > > Then I used: "sudo dd if=2gbsd-latest.dd of=/dev/sdb bs=32k" (and also
> > without the "bs=32k").
> > >
> > > But I keep getting the message: dd: writing to `/dev/sdb': No space left
> > on device
> > >
> > > It is a 2GB micro-SD card, and this image from TS suggests it is meant
> > for that size card, so I'm not sure why it's not working. Thoughts?
> > >
> > > Thanks!
> > >
> > >
> > > --- In ts-7000@yahoogroups.com, "jeffs7283" <jeffs@> wrote:
> > > >
> > > >
> > > >
> > > > --- In ts-7000@yahoogroups.com, "drex459" <dexterjagula@> wrote:
> > > > >
> > > > > I'm pretty new to working in UNIX, and have to do some development
> > on the TS-8390-4700 board. Before I get started I have to use an image
> > provided by TS. I need some help backing-up an existing micro SD card, and
> > "dropping" an imagine onto the same micro-SD card.
> > > > >
> > > > > Here is a summary of what I have to do:
> > > > > 1. Back-up the existing micro-SD card (that came with the
> > TS-8390-4700 board).
> > > > > 2. "Drop" a downloaded image onto the micro-SD card.
> > > > > 3. If necessary, how to revert the micro-SD card to the backed-up
> > image.
> > > > >
> > > > > Here's where I am, and what I still have to do:
> > > > > 1. Using the "sudo fdisk -l" command, I was able to see that the
> > micro-SD card had a few partitions on it (/dev/sdb1, /dev/sdb2, /dev/sdb3,
> > /dev/sdb4). I then used the command "sudo dd if=/dev/sdb of=sd.iso", which
> > returned the following result:
> > > > > 3862528+0 records in
> > > > > 3862528+0 records out
> > > > > 1977614336 bytes (2.0 GB) copied, 505.756 s, 3.9 MB/s
> > > > > which looks like it got backed-up successfully to the .iso file. Is
> > this the best way to back-up/image the micro-SD card, so that I can revert
> > ALL files and partitions to the way it was?
> > > > >
> > > > > 2. The image I require is: "
> >
ftp://ftp.embeddedarm.com/ts-socket-macrocontrollers/ts-4800-linux/binaries/ts-i\
mages/2gbsd-latest.dd.gz"
> > Once downloaded, how can I extract this image and "drop" it on the micro-SD
> > card? Can I use the 'dd' utility to do this? Or some other utility? Do I
> > have to format the micro-SD card first?
> > > > >
> > > > > 3. If I want to revert the micro-SD card back to the way it was
> > before I "dropped" the image onto it, how do I do that using the .iso type
> > (or any file type) using the 'dd' utility?
> > > > >
> > > > > These questions may seem basic, but any help would be greatly
> > appreciated! Thanks in advance!
> > > > >
> > > >
> > > > So far I think you've got it. 'dd' is the right utility for doing
> > straight binary copy from one file/device to another. Since your card is
> > showing up on /dev/sdb, after step 1 above you now have the original card
> > image backed up in the sd.iso file. This includes the MBR on the card and
> > can be used to restore the card image by using dd again in exactly the same
> > way: "dd if=sd.iso of=/dev/sdb bs=32k" Setting the block size to 32k is a
> > performance enhancer when writing to the card.
> > > >
> > > > For (2), writing a downloaded image to the card, you must first gunzip
> > the downloaded file. Also note that you need to match the SD card size to
> > the image. Don't try to put an 8Gb image on a 2 gig card and vice versa.
> > Then it's just "dd if=<downloaded unzipped image> of=/dev/sdb bs=32k" to
> > load it on the card. Note that it takes a loooooong time to write to an SD
> > card this way, so be patient. Since you are writing a complete filesystem
> > image to the card including the MBR there is no formatting necessary. Just
> > plug in a card and go.
> > > >
> > > > For (3) see step one above, just write your original sd.iso image back
> > onto the card with dd.
> > > >
> > > > Things to remember:
> > > >
> > > > dd is a very low level operation, no formatting or partitioning of a
> > card is necessary to use it.
> > > >
> > > > Use the block size (bs=32k) parameter to improve performance when
> > writing to sd cards. Leave this off when saving image from the card to disk.
> > > >
> > > > Match downloaded binary image size to card size. Note that the
> > downloaded binary image is usually about 10% smaller than the size of the
> > card in order to allow for the size of the card to shrink slightly over
> > time due to sectors wearing out.
> > > >
> > > > Be sure to unzip downloaded images prior to writing to SD card.
> > > >
> > > > -Jeff
> > > >
> > >
> >
> >
> >
>

Thank you very much for your reply Kevin. I would really appreciate it if you
can elaborate on the solution you have mentioned. I am completely new to Linux
so I do not quite understand what you are saying. Will it be possible for you to
guide me in a more detailed manner and/or provide me the code that you developed
so that I may use it as a reference?! Any help you can extend my way will save
me!

Thank you :)
--- In ts-7000@yahoogroups.com, Kevin Cozens <kevin@...> wrote:
>
> On Mon, Apr 2, 2012 at 8:39 AM, komal<komalrauf@...>  wrote:
> > I have recently acquired a ts-7500 board with the development kit. The SD
> > card comes with a 2.6.24 Linux Kernel. After a few days of experimenting I
> > have realized that my application (controlling a servo through PWM) will
> > require HRT and RT support which the Kernel is unable to provide (maximum
> > timer resolution I am getting on the current Kernel is 20ms).
>
> When I needed high resolution timing to toggle a couple of lines on the DIO
> header of a TS-7250 I used a small custom kernel module that used a CPU
> timer to generate interrupts and the ISR flipped the DIO bits.
>
> --
> Cheers!
>
> Kevin.
>
> http://www.ve3syb.ca/           |"Nerds make the shiny things that distract
> Owner of Elecraft K2 #2172      | the mouth-breathers, and that's why we're
>                                  | powerful!"
> #include <disclaimer/favourite> |             --Chris Hardwick
>

thank you for your reply. I would really appreciate it if you can elaborate on
the solution you have mentioned. I am a Linux newbie so not very familiar with
the development process.
Thank you :)

--- In ts-7000@yahoogroups.com, Walter Marvin <walter.marvin@...> wrote:
>
> If you don't need the serial uarts you can steal this interrupt to support hi
res timers. Its a relitively simple kernel mod.
>
> thanks
>
> Walter
>
>
>
> ________________________________
>  From: JoĆ£o Trindade <trindade.joao@...>
> To: ts-7000@yahoogroups.com
> Sent: Monday, April 2, 2012 11:22 AM
> Subject: Re: [ts-7000] Re: high resolution timers and real time
>
>
> Ā 
> I don't think that patch will work on the ts-7500.
>
>
> On Mon, Apr 2, 2012 at 8:39 AM, komal <komalrauf@...> wrote:
>
>
> >Ā 
> >Dear Sir,
> >
> >I have recently acquired a ts-7500 board with the development kit. The SD
card comes with a 2.6.24 Linux Kernel. After a few days of experimenting I have
realized that my application (controlling a servo through PWM) will require HRT
and RT support which the Kernel is unable to provide (maximum timer resolution I
am getting on the current Kernel is 20ms).
> >
> >I am new to Linux and embedded systems development and hence I am a little
confused about how to tackle this problem. I do not understand what you mean by
applying the patches and how to apply the patch. Can i simply do it on-board my
board with the SD-Card. I have a windows PC with Eclipse for Development.
> >
> >Any help you can provide me will be highly appreciated. Thank you.
> >
> >Regards,
> >Komal RAUF
> >
> >--- In ts-7000@yahoogroups.com, Peter Gammie <peteg42@> wrote:
> >>
> >> Charles, any anyone interested in hrtimers:
> >>
> >> With Andrew's help I managed to build a 2.6.32.3 kernel that seems to work.
Attached are a config and a patch, based on this:
> >>
> >> http://lkml.org/lkml/2009/7/22/119
> >>
> >> that enable hrtimers. I've lightly tested it on a ts7260 with 64Mb of
memory. I loaded the kernel via TFTP with:
> >>
> >> load -r -b 0x00218000 -h 192.168.1.1 z
> >> exec -c "console=ttyAM0,115200
ip=192.168.1.50:192.168.1.1:192.168.1.1:255.255.255.0:ts7200a:eth0:off 
root=/dev/mtdblock1"
> >>
> >> (i.e. no special memory options or anything.)
> >>
> >> So the routine is to apply Matthieu's patches, then this one. I expect it
will apply to other kernel versions (specifically 2.6.29.6 if you want -RT)
without too much bother - but be careful that the Kconfig patch applies to the
right system type!
> >>
> >> As for the clock multiplexing, Charles's suggestion of using just a PREEMPT
(not RT) kernel results in better behaviour under light periodic load (it
doesn't flicker while running top on the console) but about the same under
heavier load (scp'ing a few megabytes via ethernet). I have the CONFIG_NO_HZ
(tickless) option set, which may or may not do anything in particular...
> >>
> >> So, more investigation is required.
> >>
> >> Thanks for all your help.
> >>
> >> cheers
> >> peter
> >>
> >>
> >>
> >>
> >> --
> >> http://peteg.org/
> >>
> >
> >
>
>
> --
> JoĆ£o TrindadeĀ  Ā  Ā  <trindade.joao@...>
> Telephone: +351 93 561 39 10
> http://cnm.tagus.inesc-id.pt/joao+trindade
>

Finally i return board to TS for claim all board and I get return yesterday. The
problem is clear now.


--- In ts-7000@yahoogroups.com, "pakorn_0608" <pakorn_0608@...> wrote:
>
> I cannot reboot my TS4200+TS8160.
> I have 3 set of its and all of them are the same.
>
> i use minicom to monitor from uart port.
> When i use reboot command all board can shutdown until show "will now
restart", after that, It's no any response from TS4200.
> I try to wait for 15 mins, nothing happen.
> It occur both when booting from Xnand or SDcard.
> I already used image from ftp-embeddedarm.
>
>
> I have to switch power off and power on again.
>
> I used TS7400 and TS4800+TS8390 before.
> It never have problem like this.
>
> What should i do for solve problem?
> Thank in advance.
>

Thank you for your response. The current version of Linux kernel on the TS-7500
does not support RT? Does this mean that before I can attempt to apply the patch
I will need to upgrade my Linux Kernel?

Thank you,
Komal RAUF

--- In ts-7000@yahoogroups.com, Joćo Trindade <trindade.joao@...> wrote:
>
> I don't think that patch will work on the ts-7500.
>
> On Mon, Apr 2, 2012 at 8:39 AM, komal <komalrauf@...> wrote:
>
> > **
> >
> >
> > Dear Sir,
> >
> > I have recently acquired a ts-7500 board with the development kit. The SD
> > card comes with a 2.6.24 Linux Kernel. After a few days of experimenting I
> > have realized that my application (controlling a servo through PWM) will
> > require HRT and RT support which the Kernel is unable to provide (maximum
> > timer resolution I am getting on the current Kernel is 20ms).
> >
> > I am new to Linux and embedded systems development and hence I am a little
> > confused about how to tackle this problem. I do not understand what you
> > mean by applying the patches and how to apply the patch. Can i simply do it
> > on-board my board with the SD-Card. I have a windows PC with Eclipse for
> > Development.
> >
> > Any help you can provide me will be highly appreciated. Thank you.
> >
> > Regards,
> > Komal RAUF
> >
> > --- In ts-7000@yahoogroups.com, Peter Gammie <peteg42@> wrote:
> > >
> > > Charles, any anyone interested in hrtimers:
> > >
> > > With Andrew's help I managed to build a 2.6.32.3 kernel that seems to
> > work. Attached are a config and a patch, based on this:
> > >
> > > http://lkml.org/lkml/2009/7/22/119
> > >
> > > that enable hrtimers. I've lightly tested it on a ts7260 with 64Mb of
> > memory. I loaded the kernel via TFTP with:
> > >
> > > load -r -b 0x00218000 -h 192.168.1.1 z
> > > exec -c "console=ttyAM0,115200 ip=192.168.1.50:192
> > .168.1.1:192.168.1.1:255.255.255.0:ts7200a:eth0:off root=/dev/mtdblock1"
> > >
> > > (i.e. no special memory options or anything.)
> > >
> > > So the routine is to apply Matthieu's patches, then this one. I expect
> > it will apply to other kernel versions (specifically 2.6.29.6 if you want
> > -RT) without too much bother - but be careful that the Kconfig patch
> > applies to the right system type!
> > >
> > > As for the clock multiplexing, Charles's suggestion of using just a
> > PREEMPT (not RT) kernel results in better behaviour under light periodic
> > load (it doesn't flicker while running top on the console) but about the
> > same under heavier load (scp'ing a few megabytes via ethernet). I have the
> > CONFIG_NO_HZ (tickless) option set, which may or may not do anything in
> > particular...
> > >
> > > So, more investigation is required.
> > >
> > > Thanks for all your help.
> > >
> > > cheers
> > > peter
> > >
> > >
> > >
> > >
> > > --
> > > http://peteg.org/
> > >
> >
> >
> >
>
>
>
> --
> Joćo Trindade      <trindade.joao@...>
> Telephone: +351 93 561 39 10
> http://cnm.tagus.inesc-id.pt/joao+trindade
>

I used to use TS4800.
It has command "createxnandroot".
It can create and restore root filesystem from sd to xnand.

Now, i use TS4200.
I have only "sd2xnand" that can copy kernel and initrd to xnand.
If i wanna restore or change root system on Xnand, How could i do on ts4200?

Thank in advance.
Pakorn

No special compiler settings are needed, but you will need to use the -lm linker
option to include the match library.


--- In ts-7000@yahoogroups.com, "dannyd5000" <dannyd4000@...> wrote:
>
> I am able to crosscompile and run my software on the board without any
problems.
>
> However when I try to use floating point in my software I am having runtime
issues.
>
> Would those of you using floating point mind posting all of your compiler and
linking flags.
>
> Thanks in advance
>

Thanks,

That's what i was thought also, but I am still having problems.  Would you mind
please posting all your linker flags you are using anyway?




--- In ts-7000@yahoogroups.com, "al" <mitch.stanek@...> wrote:
>
> No special compiler settings are needed, but you will need to use the -lm
linker option to include the match library.
>
>
> --- In ts-7000@yahoogroups.com, "dannyd5000" <dannyd4000@> wrote:
> >
> > I am able to crosscompile and run my software on the board without any
problems.
> >
> > However when I try to use floating point in my software I am having runtime
issues.
> >
> > Would those of you using floating point mind posting all of your compiler
and linking flags.
> >
> > Thanks in advance
> >
>

I now have it working but only if i use gcc and not g++ for linking

/usr/local/arm-oabi-toolchain/arm-unknown-linux-gnu/bin/arm-unknown-linux-gnu-g+\
+ -o build/target/linux2/arm9/app/app -lm -lc -lstdc++ "list of object files
here"

Using g++ links but I get a failure on the TS-7500 at run time when my
application uses atof

here is the error
/app: relocation error: ./app: symbol __truncdfsf2, version GCC_3.0 not defined
in file libgcc_s.so.1 with link time reference


Using gcc links and runs on the board with no problems

/usr/local/arm-oabi-toolchain/arm-unknown-linux-gnu/bin/arm-unknown-linux-gnu-gc\
c -o /mnt/project/pems/ptc/build/target/linux2/arm9/app/app -lm -lc -lstdc++


Any ideas as to why?


--- In ts-7000@yahoogroups.com, "al" <mitch.stanek@...> wrote:
>
> No special compiler settings are needed, but you will need to use the -lm
linker option to include the match library.
>
>
> --- In ts-7000@yahoogroups.com, "dannyd5000" <dannyd4000@> wrote:
> >
> > I am able to crosscompile and run my software on the board without any
problems.
> >
> > However when I try to use floating point in my software I am having runtime
issues.
> >
> > Would those of you using floating point mind posting all of your compiler
and linking flags.
> >
> > Thanks in advance
> >
>

After successfully installing the bitstream
(ts4700_opencore-rev3-1CAN-2UART.vme.gz) that enables me to have 1 CAN port on
the TS-4700 board with the ts-8100 daughter board, I could not get the tsctl
server to send messages out the CAN port.

According to Michael Schmidt there is a bug...

Anyone here able to get CAN to work on ts4700 and ts8100?

So, I've got a 7350 here with the RTC option (big ass IC).  The stock kernel
works fine with it but a 3.0.4 kernel I built myself was having trouble.  I
could set the RTC with hwclock just fine but it would "forget" on reboot.

Examining dmesg output showed me the following:
ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx-rtc as rtc0

This makes no sense at all given that the ep93xx driver is configured as a
module and the m48t86 is configured as built-in in the kernel.

But, if I recompile the kernel with the ep93xx to be built-in, I get a second
rtc entry in /dev (rtc1).  And if I run hwclock --rtc=/dev/rtc1, it works just
fine.

So, why would ep93xx be used if it's not even loaded?

What's with the hacks in the driver code, the two blocks of hardcoded values,
selected by the module param hardcode=1 or hardcode=2 ??  On my TS4800 with the
800x480 touch panel the original images from the SD card worked fine, touch
panel cal was dead on, but when I went to modify my startup scripts somewhat so
I could boot directly into the Debian Lenny image on the card now the screen is
significantly out of calibration.  If I remove the "hardcode=1" module param
from the startup script the ts no longer works, apparently because it is getting
all 0's for the cal values.  Any ideas what's going on here?

-Jeff

--- In ts-7000@yahoogroups.com, Jim Ham <jimham@...> wrote:
>
> Hmmm, I thought that QT was a toolkit that ran on top of X. I've never
> developed in QT, so may be wrong. You might try "ps -A |grep -i xorg" or
> "ps -A |grep -i X11" and see what happens.
>
> Regards,
>
> Jim
>
> emrebirol wrote:
> > Hey Jim,
> >
> > Kernel is 2.6.35.3-433-g0fae922
> >
> > My app is written with Qt and it depends on Tslib to work with the touch
screen. I don't use X11.
> >
> > --- In ts-7000@yahoogroups.com, Jim Ham<jimham@>  wrote:
> >>
> >> Which kernel are you running? I believe that up-to-date xorg doesn't use
> >> tslib any more. The calibration values now go in xorg.conf. The down
> >> side of this is that I don't know of any calibration utility. I just
> >> played with the calibration values until it worked right.
> >>
> >> I put my xorg.conf below. Some of the entries in the touchscreen section
> >> may not be necessary - I didn't spend the time to figure out which are
> >> actually used. GrabDevice was important.
> >>
> >>
> >> The good news is that the touchscreen works perfectly once the config
> >> file is right. BlankTime, StandbyTime, SuspendTime and Offset disable
> >> screen blanking.
> >>
> >> You may have to compile some modules. I am running a custom kernel made
> >> from the 2.6.29-ts4700-00 sources available from Technologic. I'm also
> >> using the TS-4700, although I don't believe that makes any difference.
> >>
> >> here's the result of "X -version"
> >>
> >> X.Org X Server 1.7.5
> >> Release Date: 2010-02-16
> >> X Protocol Version 11, Revision 0
> >> Build Operating System: Linux 2.6.32-5-amd64 x86_64
> >> Current Operating System: Linux DynaViewIIIb 2.6.29-ts4700-00 #3 PREEMPT
> >> Tue Jun 21 09:14:48 PDT 2011 armv5tejl
> >> Kernel command line: root=/dev/ram0 init=/linuxrc mem=256M splash
> >> console=ttyS0,119200n8 video=800x480M@48
> >> Build Date: 23 June 2011  01:58:05AM
> >>
> >> Current version of pixman: 0.17.6
> >>           Before reporting problems, check http://wiki.x.org
> >>           to make sure that you have the latest version.
> >> #
> >>
> >>
> >> and here's the contents of "/etc/X11/xorg.conf"
> >>
> >> section "ServerLayout"
> >>           Identifier     "Default Layout"
> >>           Screen         "Default Screen"
> >>           InputDevice    "Generic Keyboard"
> >>           InputDevice    "Configured Mouse
> >> #       InputDevice     "TouchScreen" "CorePointer"
> >>           InputDevice     "TouchScreen" "SendCoreEvents"
> >>          Option          "BlankTime" "0"
> >>          Option          "StandbyTime" "0"
> >>          Option          "SuspendTime" "0"
> >>          Option          "OffTime" "0"
> >> EndSection
> >>
> >> Section "Files"
> >>      ModulePath "/usr/lib/xorg/modules"
> >>      ModulePath "/usr/lib/xorg/modules/linux"
> >> EndSection
> >>
> >> Section "Module"
> >>       Load           "dbe"
> >>       Load           "extmod"
> >>       Load           "fbdevhw"
> >> EndSection
> >>
> >>
> >> Section "InputDevice"
> >>          Identifier      "Generic Keyboard"
> >>          Driver          "kbd"
> >>          Option          "CoreKeyboard"
> >>          Option          "XkbRules"      "base"
> >>          Option          "XkbModel"      "pc104"
> >>          Option          "XkbLayout"     "us"
> >> EndSection
> >>
> >>
> >> Section "InputDevice"
> >>          Identifier      "Configured Mouse"
> >>          Driver          "mouse"
> >>          #Option         "CorePointer"
> >>          Option          "Device"                "/dev/input/mice"
> >>          Option          "Protocol"              "ImPS/2"
> >>          Option          "SendCoreEvents"        "true"
> >>           Option         "Emulate3Buttons"       "false"
> >> EndSection
> >>
> >>
> >> Section "InputDevice"
> >>      Identifier "TouchScreen"
> >>      Driver "evdev"
> >>      Option "Device" "/dev/input/event0"
> >>      Option "GrabDevice" "true"
> >>      Option "DeviceName" "TouchScreen"
> >>      Option "SendCoreEvents"      "true"
> >>      Option "CorePointer"
> >>      Option "Calibration" "160 3950 160 3950"
> >>      Option "ReportingMode" "Raw"
> >>      Option "Emulate3Buttons" "false"
> >>      Option "Emulate3Timeout" "50"
> >>      Option "EmulateWheel"   "false"
> >>      Option "IgnoreRelativeAxes" "true"
> >>      Option "SendCoreEvents" "true"
> >>      Option "SendDragEvents" "off"
> >>      Option "touched_action" "down"
> >>      Option "touched_button" "1"
> >>      Option "maybetapped_action" "down"
> >>      Option "maybetapped_button" "1"
> >>      Option "longtouched_action" "down"
> >>      Option "longtouched_button" "1"
> >>      Option "oneandahalftap_action" "down"
> >>      Option "oneandahalftap_button" "1"
> >>      Option "MoveLimit" "170"
> >> #   Option "DebugLevel" "5"
> >> EndSection
> >>
> >> Section "Device"
> >>           Identifier "FB"
> >>           Driver "fbdev"
> >> EndSection
> >>
> >>
> >> Section "Monitor"
> >>           Identifier "LCD Panel"
> >>           Option     "DPMS"
> >>           Modeline   "800x480" 33.26 800 800 849 850 480 480 529 530
> >> +hsync +vsync
> >> EndSection
> >>
> >> Section "Screen"
> >>           Identifier "Default Screen"
> >>           Device "FB"
> >>           Monitor "LCD Panel"
> >>           DefaultDepth    24
> >>           SubSection "Display"
> >>             Depth 24
> >>             Modes "800x480"
> >>           EndSubSection
> >> EndSection
> >>
> >> Section "DRI"
> >>          Mode    0666
> >> EndSection
> >>
> >>
> >>
> >>
> >> emrebirol wrote:
> >>> Hi,
> >>>
> >>> I try to install tslib to TS-8390. I have downloaded and compiled
libts-bin without any problem on the system but whenever I run ts_calibrate I
get the following output:
> >>>
> >>> xres = 800, yres = 480
> >>> Took 3 samples...
> >>> Top left : X =    0 Y = 715938024
> >>> Took 3 samples...
> >>> Top right : X =    0 Y = 715938024
> >>> Took 3 samples...
> >>> Bot right : X =    0 Y = 715938024
> >>> Took 3 samples...
> >>> Bot left : X =    0 Y = 715938024
> >>> Took 3 samples...
> >>> Center : X =    0 Y = 715938024
> >>> ts_calibrate: determinant is too small -- 0.000000
> >>> Calibration failed.
> >>>
> >>> Obviously it cannot read X nad Y properly. Any idea what could be the root
cause?
> >>>
> >>>
> >>>
> >>> ------------------------------------
> >>>
> >>> Yahoo! Groups Links
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> -----
> >>> No virus found in this message.
> >>> Checked by AVG - www.avg.com
> >>> Version: 10.0.1391 / Virus Database: 1520/3822 - Release Date: 08/08/11
> >>>
> >>>
> >>
> >> --
> >> Porcine Associates LLC
> >> 244 O'Connor St.
> >> Menlo Park, CA 94025
> >> USA
> >> +1(650)326-2669 fax +1(650)326-1071
> >>
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 10.0.1392 / Virus Database: 1520/3828 - Release Date: 08/11/11
> >
> >
>
> --
> Porcine Associates LLC
> 244 O'Connor St.
> Menlo Park, CA 94025
> USA
> +1(650)326-2669 fax +1(650)326-1071
>