Re: [GSoC 2021] Beagle BSP USB OTG Support

2021-05-16 Thread Ahamed Husni
Hi,

I tried the CDC Ethernet in FreeBSD. My Laptop detects an ethernet
 interface with an IPv6.
I tried to ping the IPv6, but it didn't work
. The serial and ethernet works. I'll
check the mass
storage.

--Husni


On Thu, May 13, 2021 at 9:40 AM Ahamed Husni 
wrote:

> Hi,
>
> I couldn't set up the JTAG using Launchpad as it requires some adapters.
> While discussing
> 
> in the Element14 forum, it seems it would require a lot of
> work to set up JTAG using the Launchpad.
> I can get the standard JTAG hardwares required  by ordering online before
> the coding period begins.
>
> Until that I did the hardware mod 
> required for Libdebugger on the BBB
> 
> .
> I don't know how to use the libdebugger. If anyone could point me in the
> right direction, that would be great.
>
> I tried booting the FreeBSD on BBB. The serial over usb is working.
> Ethernet and mass storage might require some configuration in FreeBSD.
>
> Best regards,
> Husni Faiz.
>
> On Mon, May 10, 2021 at 12:04 PM Christian MAUDERER <
> christian.maude...@embedded-brains.de> wrote:
>
>> Hello Ahamed,
>>
>> I'm using a J-Link to debug Beagle. I think that it doesn't have a EMU
>> pin either. Only difference: It has an additional TRST. I would suggest
>> to just try it.
>>
>> I think on OpenOCD there are a few options regarding RST. You can have
>> SRST only, TRST only, both connected together and both as separate pins.
>>
>> Best regards
>>
>> Christian
>>
>> Am 10.05.21 um 06:09 schrieb Ahamed Husni:
>> > Hi all,
>> >
>> > I need to debug the Beaglebone Black using JTAG. I got a TI LaunchPad
>> > CC1310. Launchpad has a XDS110 debugger with a (ARM - not sure) 10 pin
>> > JTAG out which can be used to debug external targets. The Beaglebone
>> has
>> > a cTI 20 pin JTAG interface. Pin layouts for the ARM10 and cTI20 is
>> > given here.
>> >
>> >
>> http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html#connector-information
>> > <
>> http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html#connector-information
>> >
>> >
>> > Can we map the pins, point to point without adapters to debug the BBB
>> > using Launchpads's XDS110?
>> >
>> > Following is what I came up with just refering the above given pin
>> layouts.
>> >
>> > *ARM10 to cTI20*
>> >
>> > 1==5 (VTRef/VCC)
>> > 2==1 (SWDIO/TMS)
>> > 3==8(GND)
>> > 4==9  (SWCLK/TCLK) SWDCLK(9) and TCK(11) are separate in cTI
>> > 5==10  (GND)
>> > 6==7(SWO/TDO)
>> > 7 KEYED
>> > 8==3 (NC/TDI)
>> > 9==12   (GNDDetect)
>> > 10==15  (nRESET)
>> >
>> > Will this work? (EMU pins are not used here)
>> >
>> > Also I found a discussion in TI' forum which says,
>> >
>> > "Controlling the EMU0 and EMU1 signals, which are mandatory to place
>> the
>> > AM335x in debug mode."
>> >
>> >
>> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly
>> > <
>> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly
>> >
>> >
>> > Also the hardware Mod for libdebugger in RTEMS connects the SWO/TDO(7)
>> > to the EMU0(13).
>> >
>> >
>> https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-using-libdebugger
>> > <
>> https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-using-libdebugger
>> >
>> >
>> > My Project Proposal:
>> >
>> https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing
>> > <
>> https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing
>> >
>> >
>> > Best regards,
>> > Husni Faiz.
>> >
>>
>> --
>> 
>> embedded brains GmbH
>> Herr Christian MAUDERER
>> Dornierstr. 4
>> 82178 Puchheim
>> Germany
>> email: christian.maude...@embedded-brains.de
>> phone: +49-89-18 94 741 - 18
>> fax:   +49-89-18 94 741 - 08
>>
>> Registergericht: Amtsgericht München
>> Registernummer: HRB 157899
>> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
>> Unsere Datenschutzerklärung finden Sie hier:
>> https://embedded-brains.de/datenschutzerklaerung/
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [GSoC 2021] Beagle BSP USB OTG Support

2021-05-12 Thread Ahamed Husni
Hi,

I couldn't set up the JTAG using Launchpad as it requires some adapters.
While discussing

in the Element14 forum, it seems it would require a lot of
work to set up JTAG using the Launchpad.
I can get the standard JTAG hardwares required  by ordering online before
the coding period begins.

Until that I did the hardware mod 
required for Libdebugger on the BBB

.
I don't know how to use the libdebugger. If anyone could point me in the
right direction, that would be great.

I tried booting the FreeBSD on BBB. The serial over usb is working.
Ethernet and mass storage might require some configuration in FreeBSD.

Best regards,
Husni Faiz.

On Mon, May 10, 2021 at 12:04 PM Christian MAUDERER <
christian.maude...@embedded-brains.de> wrote:

> Hello Ahamed,
>
> I'm using a J-Link to debug Beagle. I think that it doesn't have a EMU
> pin either. Only difference: It has an additional TRST. I would suggest
> to just try it.
>
> I think on OpenOCD there are a few options regarding RST. You can have
> SRST only, TRST only, both connected together and both as separate pins.
>
> Best regards
>
> Christian
>
> Am 10.05.21 um 06:09 schrieb Ahamed Husni:
> > Hi all,
> >
> > I need to debug the Beaglebone Black using JTAG. I got a TI LaunchPad
> > CC1310. Launchpad has a XDS110 debugger with a (ARM - not sure) 10 pin
> > JTAG out which can be used to debug external targets. The Beaglebone has
> > a cTI 20 pin JTAG interface. Pin layouts for the ARM10 and cTI20 is
> > given here.
> >
> >
> http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html#connector-information
> > <
> http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html#connector-information
> >
> >
> > Can we map the pins, point to point without adapters to debug the BBB
> > using Launchpads's XDS110?
> >
> > Following is what I came up with just refering the above given pin
> layouts.
> >
> > *ARM10 to cTI20*
> >
> > 1==5 (VTRef/VCC)
> > 2==1 (SWDIO/TMS)
> > 3==8(GND)
> > 4==9  (SWCLK/TCLK) SWDCLK(9) and TCK(11) are separate in cTI
> > 5==10  (GND)
> > 6==7(SWO/TDO)
> > 7 KEYED
> > 8==3 (NC/TDI)
> > 9==12   (GNDDetect)
> > 10==15  (nRESET)
> >
> > Will this work? (EMU pins are not used here)
> >
> > Also I found a discussion in TI' forum which says,
> >
> > "Controlling the EMU0 and EMU1 signals, which are mandatory to place the
> > AM335x in debug mode."
> >
> >
> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly
> > <
> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly
> >
> >
> > Also the hardware Mod for libdebugger in RTEMS connects the SWO/TDO(7)
> > to the EMU0(13).
> >
> >
> https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-using-libdebugger
> > <
> https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-using-libdebugger
> >
> >
> > My Project Proposal:
> >
> https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing
> > <
> https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing
> >
> >
> > Best regards,
> > Husni Faiz.
> >
>
> --
> 
> embedded brains GmbH
> Herr Christian MAUDERER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: christian.maude...@embedded-brains.de
> phone: +49-89-18 94 741 - 18
> fax:   +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[GSoC 2021] Beagle BSP USB OTG Support

2021-05-10 Thread Ahamed Husni
Hi all,

I need to debug the Beaglebone Black using JTAG. I got a TI LaunchPad
CC1310. Launchpad has a XDS110 debugger with a (ARM - not sure) 10 pin JTAG
out which can be used to debug external targets. The Beaglebone has a cTI
20 pin JTAG interface. Pin layouts for the ARM10 and cTI20 is given here.

http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html#connector-information

Can we map the pins, point to point without adapters to debug the BBB using
Launchpads's XDS110?

Following is what I came up with just refering the above given pin layouts.

*ARM10 to cTI20*

1==5 (VTRef/VCC)
2==1 (SWDIO/TMS)
3==8(GND)
4==9  (SWCLK/TCLK) SWDCLK(9) and TCK(11) are separate in cTI
5==10  (GND)
6==7(SWO/TDO)
7 KEYED
8==3 (NC/TDI)
9==12   (GNDDetect)
10==15  (nRESET)

Will this work? (EMU pins are not used here)

Also I found a discussion in TI' forum which says,

"Controlling the EMU0 and EMU1 signals, which are mandatory to place the
AM335x in debug mode."

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly

Also the hardware Mod for libdebugger in RTEMS connects the SWO/TDO(7) to
the EMU0(13).

https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-using-libdebugger

My Project Proposal:
https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing

Best regards,
Husni Faiz.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [GSoC 2021] Beagle BSP USB OTG Support

2021-05-10 Thread Christian MAUDERER

Hello Ahamed,

I'm using a J-Link to debug Beagle. I think that it doesn't have a EMU 
pin either. Only difference: It has an additional TRST. I would suggest 
to just try it.


I think on OpenOCD there are a few options regarding RST. You can have 
SRST only, TRST only, both connected together and both as separate pins.


Best regards

Christian

Am 10.05.21 um 06:09 schrieb Ahamed Husni:

Hi all,

I need to debug the Beaglebone Black using JTAG. I got a TI LaunchPad 
CC1310. Launchpad has a XDS110 debugger with a (ARM - not sure) 10 pin 
JTAG out which can be used to debug external targets. The Beaglebone has 
a cTI 20 pin JTAG interface. Pin layouts for the ARM10 and cTI20 is 
given here.


http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html#connector-information 



Can we map the pins, point to point without adapters to debug the BBB 
using Launchpads's XDS110?


Following is what I came up with just refering the above given pin layouts.

*ARM10 to cTI20*

1==5     (VTRef/VCC)
2==1     (SWDIO/TMS)
3==8    (GND)
4==9      (SWCLK/TCLK) SWDCLK(9) and TCK(11) are separate in cTI
5==10  (GND)
6==7    (SWO/TDO)
7 KEYED
8==3     (NC/TDI)
9==12   (GNDDetect)
10==15  (nRESET)

Will this work? (EMU pins are not used here)

Also I found a discussion in TI' forum which says,

"Controlling the EMU0 and EMU1 signals, which are mandatory to place the 
AM335x in debug mode."


https://e2e.ti.com/support/processors-group/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly 



Also the hardware Mod for libdebugger in RTEMS connects the SWO/TDO(7) 
to the EMU0(13).


https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-using-libdebugger 



My Project Proposal:
https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing 



Best regards,
Husni Faiz.



--

embedded brains GmbH
Herr Christian MAUDERER
Dornierstr. 4
82178 Puchheim
Germany
email: christian.maude...@embedded-brains.de
phone: +49-89-18 94 741 - 18
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel