Hi Nauman,

1/ This blog posts describes how use one Discovery to debug another, 
which is just like using a Discovery to debug a SM1000:

   http://www.rowetel.com/blog/?p=3168

2/ There is a link to the SM1000 schematic on the SM1000 page 
http://rowetel.com/sm1000.html, the STLINK connector is clearly labelled.

Cheers,

David

On 29/07/15 17:30, Nouman Khalid/A-XEN R&D/NRTC wrote:
> Hello ,
>            Thanks David for your reply. You talked a 3 wire connection of 
> stm32 Discovery board with SM1000 to listen hts1a.raw. Can you specify the 
> exact points for connection between stm32 and sm1000.
>
> Thanks in advance
>
> Nauman
> ________________________________________
> From: [email protected] 
> [[email protected]]
> Sent: Wednesday, July 29, 2015 5:18 AM
> To: [email protected]
> Subject: Freetel-codec2 Digest, Vol 63, Issue 14
>
> Send Freetel-codec2 mailing list submissions to
>          [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>          https://lists.sourceforge.net/lists/listinfo/freetel-codec2
> or, via email, send a message with subject or body 'help' to
>          [email protected]
>
> You can reach the person managing the list at
>          [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Freetel-codec2 digest..."
>
>
> Today's Topics:
>
>     1. Re: options wanted-codec2 stmf4 code optimization question
>        (David Rowe)
>     2. Problem in playing hts1a.raw (Nouman Khalid/A-XEN R&D/NRTC)
>     3. Re: Problem in playing hts1a.raw (Shane Burrell)
>     4. Re: Problem in playing hts1a.raw (Steve)
>     5. Re: Problem in playing hts1a.raw (Steve)
>     6. Re: Problem in playing hts1a.raw (David Rowe)
>     7. Re: options wanted-codec2 stmf4 code optimization question
>        (glen english)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 28 Jul 2015 15:48:01 +0930
> From: David Rowe <[email protected]>
> Subject: Re: [Freetel-codec2] options wanted-codec2 stmf4 code
>          optimization question
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> You're right Steve, I even blogged on it:
>
>     http://www.rowetel.com/blog/?p=3427
>
> This bit is a slightly damped 2nd order system for me (rings a bell):
>
> "This work took me about an hour of creative thinking (the fun bit) and
> several days of implementation pain, off by one errors, fighting to
> understand filter memories (again), and tracking down differences
> between the Octave and C versions."
>
> That ratio of 1% inspiration/99% perspiration .....
>
> - David
>
> On 28/07/15 12:44, Steve wrote:
>> I think that David said he kept the kissfft only because it was faster.
>> The kissfft however, uses twice as much memory, not being an in-place
>> algorithm.
>>
>> This can be easily changed in the code though, if a slower in-place is
>> used that still performs the task "fast enough" and you are running out
>> of memory.
>>
>> He did do a lot of memory optimizations last year, as I recall.
>>
>> On Mon, Jul 27, 2015 at 7:33 PM, Shane Burrell <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>      My last project working with codec2, the code is coupled to kissfft.
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>>
>> _______________________________________________
>> Freetel-codec2 mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 28 Jul 2015 12:27:40 +0000
> From: Nouman Khalid/A-XEN R&D/NRTC <[email protected]>
> Subject: [Freetel-codec2] Problem in playing hts1a.raw
> To: "[email protected]"
>          <[email protected]>
> Message-ID:
>          <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi all,
>        I have downloaded the code from svn and followed the instructions in 
> stm32/README. All steps went well without any error. After making stlink, I 
> copied hts1a.raw in stlink folder.
> While running  sudo ./st-util -f /home/lab/codec2/stm32/stm32f4_codec2.elf I 
> have got the following error.
>
> -f arg; /home/lab/codec2/stm32/stm32f4_codec2.elf
> 2015-07-28T17:02:15 WARN src/stlink-usb.c: Couldn't find any ST-Link/V2 
> devices
>
> Any suggestions ?
>
>
> My sm1000 is in debug mode (Pressed PTT then powered up then PTT released).
> dmesg shows me following
> [98392.925109] usb 1-1.3: Product: STM32  BOOTLOADER
> [98392.925110] usb 1-1.3: Manufacturer: STMicroelectronics
> [98392.925111] usb 1-1.3: SerialNumber: 335838523233
> Means device is connected.
>
>
> Thanks in advance
>
> Nauman
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 28 Jul 2015 09:00:54 -0400
> From: Shane Burrell <[email protected]>
> Subject: Re: [Freetel-codec2] Problem in playing hts1a.raw
> To: [email protected]
> Message-ID:
>          <CACy74GRqhQtBVpkYEFLnRzm96r6t_v4A=o3b+vz8sirjvda...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Are you using a ST- LINK Programmer?  Looks like that device is a STM board
> and its connecting to the STM bootloader.
>
> On Tue, Jul 28, 2015 at 8:27 AM, Nouman Khalid/A-XEN R&D/NRTC <
> [email protected]> wrote:
>
>> Hi all,
>>        I have downloaded the code from svn and followed the instructions in
>> stm32/README. All steps went well without any error. After making stlink, I
>> copied hts1a.raw in stlink folder.
>> While running  sudo ./st-util -f /home/lab/codec2/stm32/stm32f4_codec2.elf
>> I have got the following error.
>>
>> -f arg; /home/lab/codec2/stm32/stm32f4_codec2.elf
>> 2015-07-28T17:02:15 WARN src/stlink-usb.c: Couldn't find any ST-Link/V2
>> devices
>>
>> Any suggestions ?
>>
>>
>> My sm1000 is in debug mode (Pressed PTT then powered up then PTT released).
>> dmesg shows me following
>> [98392.925109] usb 1-1.3: Product: STM32  BOOTLOADER
>> [98392.925110] usb 1-1.3: Manufacturer: STMicroelectronics
>> [98392.925111] usb 1-1.3: SerialNumber: 335838523233
>> Means device is connected.
>>
>>
>> Thanks in advance
>>
>> Nauman
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Freetel-codec2 mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 4
> Date: Tue, 28 Jul 2015 08:24:13 -0500
> From: Steve <[email protected]>
> Subject: Re: [Freetel-codec2] Problem in playing hts1a.raw
> To: [email protected]
> Message-ID:
>          <CAMeUeEBrRyUhDbsFrSkvf5+nkEG2Pf5EOO4nipL=wgoo52-...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Do you have the STLINK_DEVICE environment variable defined properly to the
> USB port detected after the 'dmesg'.
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 5
> Date: Tue, 28 Jul 2015 08:54:35 -0500
> From: Steve <[email protected]>
> Subject: Re: [Freetel-codec2] Problem in playing hts1a.raw
> To: [email protected]
> Message-ID:
>          <CAMeUeEDf00y0PoYbsAbfGLRpKTpWsUgR=xn+8d7yv5lbdnz...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Use the 'lsusb' to get the bus and device address probably.
>
> STLINK_DEVICE=001:004; export STLINK_DEVICE
>
> For BUS 1 Device 4, or whatever associates with the USB port desired.
>
> I looked at the code and if the variable is not defined it just goes
> along merrily until it blows up somewhere down the line.
>
> Just an idea...
>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 29 Jul 2015 06:49:26 +0930
> From: David Rowe <[email protected]>
> Subject: Re: [Freetel-codec2] Problem in playing hts1a.raw
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> To use st-util, gdb, and the stdio semi-hosting library, you need a
> Discovery board and 3 wire STLINK connection to the SM1000.
>
> Or you can use a Discovery board stand alone to run many of the unit
> tests in codec2-dev/stm32.
>
> Alternatively you can simply flash the SM1000 over USB using the boot
> loader, as described on the SM1000 page.  However in this case you can't
> use the semi-hosting facility, e.g. fread/fwrite required bymany of the
> programs in codec2-dev/stm32.
>
> Cheers,
>
> David
>
> On 28/07/15 21:57, Nouman Khalid/A-XEN R&D/NRTC wrote:
>> Hi all,
>>         I have downloaded the code from svn and followed the instructions in 
>> stm32/README. All steps went well without any error. After making stlink, I 
>> copied hts1a.raw in stlink folder.
>> While running  sudo ./st-util -f /home/lab/codec2/stm32/stm32f4_codec2.elf I 
>> have got the following error.
>>
>> -f arg; /home/lab/codec2/stm32/stm32f4_codec2.elf
>> 2015-07-28T17:02:15 WARN src/stlink-usb.c: Couldn't find any ST-Link/V2 
>> devices
>>
>> Any suggestions ?
>>
>>
>> My sm1000 is in debug mode (Pressed PTT then powered up then PTT released).
>> dmesg shows me following
>> [98392.925109] usb 1-1.3: Product: STM32  BOOTLOADER
>> [98392.925110] usb 1-1.3: Manufacturer: STMicroelectronics
>> [98392.925111] usb 1-1.3: SerialNumber: 335838523233
>> Means device is connected.
>>
>>
>> Thanks in advance
>>
>> Nauman
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Freetel-codec2 mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 29 Jul 2015 09:31:55 +1000
> From: glen english <[email protected]>
> Subject: Re: [Freetel-codec2] options wanted-codec2 stmf4 code
>          optimization question
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> ------------------------------------------------------------------------------
>
>
> ------------------------------
>
> _______________________________________________
> Freetel-codec2 mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>
>
> End of Freetel-codec2 Digest, Vol 63, Issue 14
> **********************************************
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Freetel-codec2 mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>

------------------------------------------------------------------------------
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to