The issue has been resolved on the server side. I confirmed that wget works fine now. I expect the yocto build should be able to succeed now.

Best regards,

Brad

---------------------------------------------------

Brad Griffis

TI Digital Field Applications

Member Group Technical Staff (MGTS)

Schaumburg, IL

Office: 847-517-4699

From: Peter Smith [mailto:salerio@gmail.com]
Sent: Monday, April 23, 2018 12:33 PM
To: Stiffler, Jacob
Cc: Griffis, Brad; meta-ti@yoctoproject.org
Subject: [EXTERNAL] Re: [meta-ti] wget fetch issue with ti-cgt-pru_2.1.5.bb

Both,

behind our corporate proxy the error is seen and on my private Mac (with no proxy etc). I too can download the file with Chrome but wget always fails, unfortunately Yocto uses wget.

Peter

Best Regards

Peter

On 23 April 2018 at 18:11, Stiffler, Jacob <j-stiffler@ti.com> wrote:

Brad,

On my home machine. I was able to recreate this with wget, but I was able to download through other methods. I am not sure what may be happening.

I was able to download through a browser (chrome), and I was able to download with “curl” using the following command:

$ curl -L http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.2.1/ti_cgt_pru_2.2.1_linux_installer_x86.bin > ti_cgt_pru_2.2.1_linux_installer_x86.bin

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 382 100 382 0 0 2239 0 --:--:-- --:--:-- --:--:-- 2247

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0

100 318 100 318 0 0 848 0 --:--:-- --:--:-- --:--:-- 848

100 17.0M 100 17.0M 0 0 4040k 0 0:00:04 0:00:04 --:--:-- 4517k

$ file ti_cgt_pru_2.2.1_linux_installer_x86.bin

ti_cgt_pru_2.2.1_linux_installer_x86.bin: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped

- Jake

From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Griffis, Brad
Sent: Monday, April 23, 2018 12:51 PM
To: meta-ti@yoctoproject.org
Subject: [EXTERNAL] [meta-ti] wget fetch issue with ti-cgt-pru_2.1.5.bb

Recipe: meta-ti/recipes-ti/devtools/ti-cgt-pru_2.1.5.bb

Issue summary: fetch of ti_cgt_pru_2.2.1_linux_installer_x86.bin results in 403 forbidden error

In the rocko branch, I see we’re building PRU source code from source. I wanted to report a fetch issue. This was reported to me by a customer and I have independently confirmed I see the same behavior.

I can see the issue very easily just by doing a wget:

brad@brad-XPS-15-9560:~$ wget http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.2.1/ti_cgt_pru_2.2.1_linux_installer_x86.bin

--2018-04-23 11:48:42-- http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.2.1/ti_cgt_pru_2.2.1_linux_installer_x86.bin

Resolving software-dl.ti.com (software-dl.ti.com)... 23.209.190.17

Connecting to software-dl.ti.com (software-dl.ti.com)|23.209.190.17|:80... connected.

HTTP request sent, awaiting response... 302 Moved Temporarily

Location: https://www.ti.com/general/docs/licreg/anonymousproddownload.tsp?downloadPage=true&location=http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.2.1/ti_cgt_pru_2.2.1_linux_installer_x86.bin [following]

--2018-04-23 11:48:42-- https://www.ti.com/general/docs/licreg/anonymousproddownload.tsp?downloadPage=true&location=http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.2.1/ti_cgt_pru_2.2.1_linux_installer_x86.bin

Resolving www.ti.com (www.ti.com)... 23.34.71.13, 2600:1407:21:281::b48, 2600:1407:21:285::b48

Connecting to www.ti.com (www.ti.com)|23.34.71.13|:443... connected.

HTTP request sent, awaiting response... 302 Moved Temporarily

Location: http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.2.1/ti_cgt_pru_2.2.1_linux_installer_x86.bin?tracked=1 [following]

--2018-04-23 11:48:42-- http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.2.1/ti_cgt_pru_2.2.1_linux_installer_x86.bin?tracked=1

Connecting to software-dl.ti.com (software-dl.ti.com)|23.209.190.17|:80... connected.

HTTP request sent, awaiting response... 403 Forbidden

2018-04-23 11:48:42 ERROR 403: Forbidden.

The above console snippet comes from my home PC where there is no firewall/proxy to complicate things. There seems to be a fundamental issue being able to fetch this file. Interestingly, if I run the command from inside the TI firewall it works ok.